Why a one-time CSV export stops working
The first scrape is easy: pick a category and a location, download a CSV, import it into whatever you're using to call or email. The problem shows up a month later, when that list is stale — new businesses have opened, some have closed, and nobody remembers to go back and re-run the search.
Manual re-scraping has three points of failure: someone has to remember to do it, someone has to re-upload the export without duplicating what's already in the CRM, and the filter criteria has to be re-applied by hand instead of baked into the query. None of those are hard individually. Together, they're why "we'll just re-run it monthly" quietly stops happening after the second month.
The two pieces: webhooks and scheduled runs
Automating this is really two separate mechanisms, and they solve different halves of the problem:
Webhook delivery (Growth plan, $49/mo)
The moment a scrape you triggered finishes, its results POST to a URL you control instead of sitting in the dashboard waiting to be downloaded. This is what lets Zapier, Make, or n8n pick up the data and route it anywhere those tools connect — no manual export step at all.
Scheduled, recurring scrapes (Scale plan, $129/mo)
The same query and filters re-run on their own on an interval, so the job itself no longer needs a human to start it. Paired with a webhook, this is the part that closes the loop — new listings show up in your CRM without anyone opening the dashboard.
On Growth without scheduled scrapes, you still automate the delivery side — you (or a Zapier schedule action calling the API) just have to be the one starting the job.
Building the no-code pipeline
Lock in the query and filters once
Decide the category, cities/states, and filter thresholds — minimum rating, minimum review count, has-website, has-phone — before you automate anything. Filters run during the scrape itself, so every future run returns the same shape of qualified lead instead of a raw dump you have to clean by hand each time.
Get an API key and webhook URL
From the Integrations tab in your dashboard (Growth plan or higher). The key authenticates REST calls; the webhook URL is where a finished job's results get POSTed automatically — JSON, one object per lead.
Create a webhook trigger in Zapier, Make, or n8n
Add a "Webhook received" (or "Catch Hook") trigger step and paste in the URL from step 2. Run one test scrape to send a sample payload — every automation platform uses that sample to let you map individual fields in the next step.
Map fields to a destination action
Connect the trigger to an action: "Create Row" in Google Sheets or Airtable, "Create/Update Contact" in your CRM, or "Send Channel Message" in Slack. Map business name, phone number, website URL, rating, and address to the destination's fields.
Turn on recurring scrapes to keep it running
On the Scale plan, the same query and filters can re-run on a schedule without anyone starting the job by hand — new listings and rating changes flow through the same webhook automatically. On Growth, trigger runs yourself or from a Zapier schedule action calling the API.
Where the leads can go
CRM
Zapier and Make both have native connectors for the major CRMs. Each completed scrape creates or updates a contact/deal, so reps open their pipeline to leads that are already there instead of a CSV waiting to be imported.
Google Sheets or Airtable
A running, always-current list instead of a one-off export. Useful for teams that want a shared view without giving everyone dashboard access, or that already run reporting off a sheet.
Slack
Post a message per qualified lead (or a daily digest) to a sales channel. Reps see new leads as they land instead of checking a dashboard or inbox for a fresh CSV.
Your own backend
Skip the middleman tools entirely and call the REST API directly — POST /scrape to start a job, GET /jobs/{id} to poll status, GET /jobs/{id}/download?fmt= to pull CSV, XLSX, or JSON. See the full API guide below for endpoint details and code examples.
Whichever destination you pick, the data arriving is the same up to 18 fields available across a scrape — business name, category, phone number, website URL, address, rating, review count, hours of operation, price level, and more — so the mapping step is a one-time setup, not something you redo per run.
FAQ
Do I need to know how to code?+
No. Zapier, Make, and n8n all connect to a webhook with a visual builder — you're mapping fields, not writing requests. You do need a Growth plan or higher, since webhook delivery and API access aren't included on the free or Starter tiers.
Can I skip Zapier and call the API directly?+
Yes, if you already have a backend. The same webhook payload that Zapier receives is available from the REST API's job endpoints — see the API guide below for the raw POST /scrape, GET /jobs/{id}, and download-by-format calls.
How often can a scrape re-run on its own?+
Recurring, scheduled scrapes are a Scale-plan feature ($129/mo, 20,000 credits). On Growth, a webhook fires automatically the moment a scrape you start finishes — the scrape itself still has to be triggered, whether by you, your own cron job calling the API, or a Zapier schedule trigger.
Will duplicate leads pile up if a scrape re-runs weekly?+
Each run returns the businesses matching your query and filters at that moment, not just new listings since last time — dedupe against what's already in your CRM happens on the receiving end. Most CRM and Sheets integrations in Zapier/Make have a built-in "skip if exists" match on phone number or website domain for exactly this.
Stop re-running scrapes by hand
Start on Growth for webhook delivery, or Scale for fully recurring runs. 50 free credits to test the query and filters first — no credit card.