How to Connect Google Maps Scraper to n8n and Make.com

Learn how to build end-to-end B2B lead generation workflows without code. Trigger Google Maps scrapes from Airtable, catch instant webhook payloads, and push fresh business leads directly into Notion, HubSpot, or Google Sheets.

Why Connect Google Maps Scraping to No-Code Tools?

You do not need to be a software engineer to build powerful lead generation systems. With visual automation platforms like Make.com and n8n, growth marketers, sales operations leads, and agency founders can connect the Bolt Scraper API directly to their existing toolstack.

On-Demand Triggers

Add a new target industry or city into Airtable or Notion to instantly trigger a scrape in Bolt Scraper.

Zero-Touch Webhooks

Receive an instant callback the moment search extraction finishes, complete with extracted emails and social links.

Auto-Enroll in Outreach

Filter prospects by rating or review count and push new business contacts straight into cold email campaigns.

The 2-Scenario No-Code Architecture

A robust no-code scraping automation is built with two interconnected workflows:

Scenario A: The Job Trigger

Monitors a form or database table. Sends an HTTP POST request to https://boltscraper.com/api/v1/maps/jobs with the desired keywords and passes the Webhook URL from Scenario B.

Bolt Scraper Cloud Engine

Crawls Google Maps in the cloud, visits linked websites to discover emails and social channels, and automatically deduplicates all results by place_id.

Scenario B: The Webhook Receiver & Lead Syncer

Catches the gmap_job.completed payload, iterates through the business records, and creates rows in Airtable, Google Sheets, or CRM contacts.

How to Set Up in Make.com

Step 1: Create Scenario B (Custom Webhook Receiver)

  1. In Make.com, create a new scenario and select the Custom Webhook module as the trigger.
  2. Click Add, name it Bolt Scraper Completed Webhook, and copy the generated Webhook URL (e.g. https://hook.eu1.make.com/abc123xyz).

Step 2: Create Scenario A (HTTP Request Module)

  1. Add an HTTP - Make a request module.
  2. Set URL to: https://boltscraper.com/api/v1/maps/jobs
  3. Set Method to: POST
  4. Under Headers, add:
    • Name: Authorization  |  Value: Bearer bs_YOUR_API_KEY
    • Name: Content-Type  |  Value: application/json
  5. Set Body type to Raw (application/json) with content:
Make.com HTTP Request Payload
{
  "keywords": ["Solar contractors in Phoenix, AZ", "Solar contractors in Tucson, AZ"],
  "scrape_websites": true,
  "ultra_mode": true,
  "webhook_url": "https://hook.eu1.make.com/your-scenario-b-webhook"
}

Tip: Bolt Scraper automatically bypasses Google Maps' 120-lead limit even in standard mode. Setting "ultra_mode": true enables deep extraction to retrieve up to 3x more leads in dense metropolitan markets.

Step 3: Parse Leads and Sync to Airtable or Google Sheets

When Bolt Scraper finishes, it sends the gmap_job.completed payload containing an array of leads and a signed download_csv_url.

In Make.com, add an Iterator module mapping over leads[], followed by an Airtable - Create a Record module. Map the following fields directly:

  • title → Company Name
  • phone → Phone Number
  • website → Website URL
  • email → Discovered Contact Email
  • address → Physical Address
  • rating → Google Review Rating
  • place_id → Google Place ID (use for primary record matching)

How to Set Up in n8n (Self-Hosted or Cloud)

For privacy-conscious teams using open-source automation, n8n offers an unbeatable workflow canvas.

n8n Workflow Structure
// 1. Webhook Node: Catch Bolt Scraper callback
[Webhook: POST /bolt-scraper-callback]
       ↓
// 2. IF Node: Validate event
[IF: $json.headers["x-bolt-event"] === "gmap_job.completed"]
       ↓
// 3. HTTP Request Node: Stream full dataset or process inline leads
[Item Lists / Split Out: $json.body.leads]
       ↓
// 4. Destination Node: Upsert into Postgres / Airtable / HubSpot
[Postgres / Airtable: Upsert where place_id matches]
No Complex Deduplication Routers Needed

In many scraping workflows, you must build multi-step deduplication routers in n8n or Make.com to drop duplicate businesses. With Bolt Scraper, deduplication across your keywords happens automatically in the cloud via place_id, simplifying your no-code scenarios and conserving Make operations.

Under the hood, both Make.com and n8n can leverage either the Real-time Search API (POST /api/v1/maps/search for synchronous lookups in single-run scenarios) or the asynchronous Batch Jobs API (POST /api/v1/maps/jobs with signed webhooks for high-volume pipelines). For complete technical details, explore our comprehensive Google Maps Scraper API guide and the official Bolt Scraper API documentation. To trigger these scenarios automatically on a cron recurrence, see our guide on how to schedule Google Maps scraping with webhooks. If you are structuring campaigns across dozens of territories, check out our best practices for multi-city lead generation at scale, or explore our Google Places API alternative / comparison.

Google Maps API Series

Part of the Google Maps Scraping Playbook

Explore the other core guides in this topic cluster to build robust, automated prospecting pipelines:

Automate Your Lead Sourcing with No-Code

Connect Make.com or n8n to Bolt Scraper in minutes. Bypass the 120-lead limit natively and stream clean B2B lead lists straight into your CRM on autopilot.

No Credit Card Required 1,000 Free Cloud Leads/Mo Auto-Deduplication by Place ID

Instant cloud setup • No-code webhooks • Test live Google Maps API for free & view docs

Frequently Asked Questions

No. The initial HTTP POST request triggers the job asynchronously and returns immediately with a job_id. Your Make scenario finishes right away (saving execution credits), and Scenario B triggers only when Bolt Scraper fires the webhook callback upon completion.

Yes. For large datasets (500+ records), use Make's CSV parser module to ingest the signed download_csv_url in batches, or use n8n's batching node to create up to 10 records per request in Airtable.

Yes. Bolt Scraper automatically removes duplicate business records in the cloud using Google's permanent place_id across all keywords in your job. You never have to build complex deduplication filters in your scenarios.