Fetch Building Permit Leads with Apify in n8n Workflow Automation

Automatically fetch building permit leads from Apify and deliver them to your tools via n8n

This n8n workflow runs daily (or on demand) to call the Apify transparent_meteorite/building-permits-leads actor, pulls recent building permit records for selected cities, tags each lead with a _source field, and sends the results to your chosen destination—such as Google Sheets, Slack, or a CRM.

What this workflow does

• Schedules or manual start: Executes every day at 07:00 via a schedule trigger, or you can start it manually with a manual trigger.
• Calls the Apify API: Uses an HTTP Request node to send a POST to the Apify API and runs the actor synchronously to fetch the resulting dataset items as JSON.
• Filters and limits leads: Retrieves up to a configured number of permit records based on the actor inputs—such as cities, record types, and the “since days” filter.
• Adds lead provenance: Appends a _source field to each returned item so you can trace where the building permit data came from.
• Routes to your destination: Passes the tagged permit leads to a placeholder step where you connect your preferred destination (for example, a spreadsheet, Slack, or a CRM).

Use cases

• Property/real estate teams who want a steady stream of building permit leads in a Google Sheet.
• Sales or BD workflows that push new permits into Slack for quick review.
• CRMs that require automated ingestion of recent permit activity for lead scoring and outreach.

Technical details

• Apify integration: Uses an Apify API token with Authorization: Bearer <YOUR_APIFY_API_TOKEN>.
• n8n nodes used: set, no op, sticky note, HTTP Request, Manual Trigger, Schedule Trigger.
• Actor: transparent_meteorite/building-permits-leads (run via Apify API, dataset results returned as JSON).