Apify Building Permit Leads to n8n HTTP Workflow

Get fresh building permit leads from Apify into n8n—automatically

This n8n HTTP workflow calls the Apify Building Permits Leads actor to fetch recent building permit records from selected cities, enriches each item with a _source label, and sends the leads to a step you replace with your own destination (CRM, Slack, or Google Sheets).

What this workflow does

• Runs on a schedule (or manually): it triggers daily at 07:00, or you can start it with a manual test trigger.
• Calls Apify via HTTP: the workflow sends a POST request to the Apify API to run the actor transparent_meteorite/building-permits-leads and synchronously returns the actor’s dataset items as JSON.
• Tags each record with its source: it adds a _source field to every returned permit record so you can track where the data came from.
• Hands off to your destination: it passes the enriched items to a placeholder step that you configure to store, notify, or further process the leads.

Use cases

• Real estate & contractor lead generation: automatically collect building permit leads from specific cities and route them into your pipeline.
• Sales ops automation: enrich permit data with _source and forward it to a system of record like Google Sheets or a CRM.
• Daily monitoring: run the workflow every morning to keep your outreach lists current without manual data pulling.

Technical details

• HTTP request node: POSTs to the Apify API to run transparent_meteorite/building-permits-leads.
• Apify API authentication: uses an n8n HTTP Header Auth credential with Authorization: Bearer <YOUR_APIFY_API_TOKEN>.
• Workflow nodes: set, no op, sticky note, http request, manual trigger, schedule trigger.
• Configurable actor inputs: cities, recordTypes, sinceDays, maxItems, and monitorMode.

Get a reliable Apify-to-n8n HTTP workflow foundation for building-permit lead automation—then connect it to your chosen destination.