All articles

Data Quality & CRMOctober 6, 2026· 5 min read

How to Send Google Maps Leads to Your CRM Automatically

Downloading a CSV and importing it by hand works once. Here's how to send new Google Maps leads to your CRM on a schedule using the MapsDaddy API, webhooks and files.

By MapsDaddy Team

Downloading a CSV and importing it by hand works fine once. When you do it every week, it gets old fast. This guide shows how to send Google Maps leads to your CRM automatically: start a search with the MapsDaddy API, get a signed webhook when the list is ready, skip the businesses you already have, and create only new records. Once it's set up, new local businesses reach your team without anyone opening a spreadsheet.

Three Ways to Send Google Maps Leads to Your CRM

MapsDaddy doesn't have built-in CRM connectors. Instead, it gives you three ways to move data, and you connect them to the CRM you already use.

MethodHow it worksBest for
CSV or Excel fileDownload the list from Lists & Exports and use your CRM's import toolOccasional lists, no code
API pollingYour script starts a search, then checks the order until it's doneScheduled jobs and scripts
WebhooksMapsDaddy sends a signed request to your URL when the list is readyHands-off pipelines

To receive webhooks, you can write a small endpoint yourself, or use a tool people already rely on for this, like Zapier, Make or n8n. These aren't official MapsDaddy integrations. They're simply tools that can receive a webhook, call an API and then create records in your CRM.

What You Need

  • A MapsDaddy API key from the API Key page. Owners and admins can create one.
  • A CRM that can create records through its own API, or an automation tool that connects to it.
  • A public HTTPS URL to receive webhooks.
  • A field in your CRM to store each business's Google Maps URL.

You don't need a Google account or a Places API key. The API uses the same credits and prices as your dashboard, with no API fee.

How the Pipeline Works

  1. Start the search. Send POST /google-maps-scraper with your categories, locations, a results_file_name and your callback_url. Each category in each location is one search, at a flat 10 credits per search at the time of writing.
  2. Save the signing secret. The response includes an order_id and a callback_signing_secret. The secret is only returned once, so store it.
  3. Catch the webhook. When the order.delivered event arrives, check the X-MapsDaddy-Signature header with your secret before you trust it.
  4. Read the rows. Once an order is completed, its order_id is also the list ID. Read it 50 rows at a time with GET /lists/{list_id}/rows, or grab the whole file with GET /lists/{list_id}/download?format=csv.
  5. Skip what you have. Check each Google Maps URL against your CRM and drop the ones that already exist.
  6. Create the records. Send only new businesses to your CRM, then assign them or post a summary to your team chat.

Our post on automating exports with the API and webhooks has the full request and a signature check you can copy.

Use the Google Maps URL as Your Key

This is the step that matters most. Every listing in your list has its own Google Maps URL. Save it in a custom field on each CRM record, and check it before you create anything. If the URL already exists, skip the row or update the record. That way, running the same city again next month only adds the businesses you don't have yet.

Business names aren't reliable for this, because chains and similar names are common. Website is a decent second check, as long as you skip rows where it's blank. Our checklist for how to clean Google Maps data before a CRM import covers phone formats, address splitting and the full column mapping.

Add Contacts Before the Push

If your sales team needs emails or owner names, enrich the list before it reaches the CRM. Send POST /lists/{list_id}/enrichments with a service such as biz_email_finder or contact_enrichment. Set dry_run to true first: it returns how many rows would run and the most it could cost, and charges nothing.

Enrichment runs don't send webhooks, so check their progress with GET /lists/{list_id}/enrichments. When the run is complete, the new columns show up in the rows and the download. You only pay for what's found, and rows already enriched by the same service aren't run again. The latest credit costs are on the pricing page.

Tip: Send an Idempotency-Key header with enrichment requests. If your automation retries after a timeout, it gets the same run back instead of starting a second one.

A Practical Example

A fictional insurance agency, Harbor Line Insurance, wants new auto repair shops in front of its team every Monday. A scheduled job sends one request with the category "Auto repair shop" and four locations around Tampa. That's 4 searches, so 40 credits. The callback_url points at an n8n workflow they set up themselves.

When order.delivered arrives, the workflow checks the signature, reads the rows and compares each Google Maps URL with the CRM. Suppose 37 shops are new, like Bayshore Auto Care with a phone number of (813) 555-0162. The workflow creates those 37 company records, tags them with the search category and posts "37 new auto repair shops this week" in the sales channel.

Keep It Reliable

  • Respond fast. Return a 2xx status as soon as you've saved the webhook, then do the slow work afterwards.
  • Handle repeats. Your endpoint may see the same event more than once, so check the order ID before you process it again.
  • Watch your balance. A 402 response means you're out of credits. Top up on Buy Credits, and credits never expire.
  • Log failures. Keep the order ID with every error so you can find the list in Lists & Exports later.

Getting Started

Create a key on the API Key page, run one small search with a test callback_url, and log what arrives. Once that works, point it at your real workflow. See what you can build on the Google Maps API page.

Start Finding & Scraping Local
Business Leads
Today

Get started for free

No Credit Card Required

Send Google Maps Leads to Your CRM Automatically