Yes. ZipLead sends a webhook (a small HTTP POST with a JSON body) to one URL you save in Settings, and Zapier's Catch Hook trigger receives it. There is no ZipLead app in Zapier's directory, so you use the generic Webhooks by Zapier trigger, which Zapier puts on their paid plans. On the ZipLead side, The Webhook URL field is on Command ($179/mo), the plan that includes API access. Operator and the free plan do not have it.
In Zapier, click Create Zap. For the trigger, choose the app Webhooks by Zapier and the event Catch Hook, then Continue. Zapier shows a URL starting with hooks.zapier.com/hooks/catch/. Copy it.
In ZipLead, open the dashboard and click Settings in the left sidebar. Scroll to the section titled Webhook URL. Paste the URL into the field and click Save. It has to start with https://, which Zapier's does.
Once a URL is saved, a Send test payload button appears under the field. Click it. ZipLead posts an event called test.ping. Back in Zapier, click Test trigger and the request shows up with event, timestamp and data.
Every event goes to the same URL, so add a Filter by Zapier step right after the trigger: only continue if event (Text) exactly matches the one you want, for example prospect.gold.
A Google Sheets row, a Slack message, a HubSpot company, whatever you run. The test payload's fields differ from the real events, so map from the reference below. prospects arrives as a list; use Looping by Zapier if you want one action per prospect.
Publish the Zap. Then run a search in ZipLead. When it finishes, scrape.completed hits the URL and you can watch it in Zap History. Enrich a few prospects to see prospect.enriched and, if any score 85 or higher, prospect.gold.
Same URL for all of them. The X-ZipLead-Event header and the event field in the body both carry the name, so filter on either.
| Event | When it fires | What data holds |
|---|---|---|
test.ping | You click Send test payload in Settings. | message, userId |
scrape.completed | A search finishes. | jobId, location, radius, industries, totalProspects |
prospect.enriched | You enrich prospects in a search. | jobId, enrichedCount, prospects (id, name, score, tier) |
prospect.gold | A prospect you just enriched scores 85 or higher, the Hot tier. Sent alongside prospect.enriched. | jobId, count, prospects (id, name, score, tier) |
pipeline.moved | You move one or more prospects to a new pipeline stage. | prospectIds, newStatus, prospects (id, name) |
alerts.raised | The weekly monitoring run finds changes, and only if the Webhook switch under Alert delivery is on. | count, alerts (prospectId, prospectName, type, severity, message) |
POST https://your-endpoint
Content-Type: application/json
User-Agent: ZipLead-Webhook/1.0
X-ZipLead-Event: prospect.gold
{
"event": "prospect.gold",
"timestamp": "2026-09-09T18:20:11.000Z",
"data": {
"jobId": 4127,
"count": 2,
"prospects": [
{ "id": 88213, "name": "Coastline Drain Co.", "score": 91, "tier": "PRIME" },
{ "id": 88240, "name": "Peak Electric", "score": 86, "tier": "PRIME" }
]
}
}There is a single Webhook URL field. Every event goes to it. If you want Zapier and Make both, catch it once and fan out from there.
The field rejects anything that does not start with https://.
ZipLead sends each event once and waits up to 10 seconds for a 2xx. If your endpoint is down or slow, that event is gone. It does not queue and it does not try again.
There is no signing secret or HMAC header. If you need to know a request really came from ZipLead, put a secret in the URL itself (Zapier and Make URLs already are unguessable) and check it on your side.
The prospect events carry id, name, score and tier. They do not carry phone, website, address or email. For the full record, download the CSV or call GET /api/v1/prospects with the job_id from the event.
tier arrives as PRIME, SOLID, WATCH or SKIP. The app shows those as Hot, Warm, Cold and Skip. Same thing, older names.
Yes. Webhooks and the REST API are the two things Command adds on top of Operator, along with 200 searches and 500 enrichment credits a month instead of 100 and 100. On Operator you can still export a CSV and import it wherever you want.
No. Webhooks by Zapier is one of Zapier's premium apps, and Zapier makes it available on their paid plans. That is Zapier's rule, not ours, so check their pricing page for the current tier.
No. The webhook is one direction, ZipLead to you. There is no endpoint that starts a search or enriches a prospect from outside. The API is read-only: GET /api/v1/prospects and GET /api/v1/jobs with your API key.
The event is gone. ZipLead sends each one once and does not retry. Zapier keeps catching as long as the Zap is on, so the practical rule is to leave it on.
5 free searches a month, no card, so you can see the data before you pay for the webhook. Prefer Make? That page is here.
Run a free search