Google Maps Lead List n8n Workflow with Evascrape & Budget Cap

Turn Google Maps searches into a budget-capped lead list—automatically in n8n

This Google Maps Lead List n8n Workflow with Evascrape & Budget Cap uses the Evascrape API to request, run, and retrieve a Google Maps scraping job, then outputs one item per business lead (e.g., dentists in a chosen location) while enforcing a maximum budget and handling common job/API failure states.

What this workflow does

• Starts manually and accepts Google Maps search terms, location, total record count, a max cost cap (USD), and polling limits.
• Requests a free quote from Evascrape for the requested number of records.
• Stops early if the quote fails or if the quoted cost exceeds your configured maximum.
• Starts the paid scraping job only when the quote is successful and within budget.
• Polls job status at your chosen interval until the job finishes or the workflow hits the maximum number of checks.
• Stops with notes if the job is still running after polling limits, or stops with details when the job completes without a successful result.
• If successful, fetches job results from Evascrape and splits the response into one workflow item per lead record.

Use cases

• Build a targeted Google Maps lead list for outbound sales (e.g., “dentists” in Austin) with predictable spend.
• Automation engineers can plug the output items into CRM or outreach steps—after this workflow produces one item per business.
• SaaS operators can refresh local business datasets on demand while preventing overspending via the budget cap.

Technical details

• Integration: Evascrape API (HTTP Request with Authorization: Bearer <your_evascrape_key>)
• n8n nodes: if, set, wait, split out, sticky note, http request
• Setup: create an Evascrape account, generate an API key, ensure your balance covers paid jobs, then update workflow search settings (terms, location, records, max cost, optional email verification).