Most lead tools integrate with Zapier in one direction: push a lead out, wave goodbye. Leadistry Flows completes the loop. A flow can hand a lead to your external system, pause that lead's journey, and resume it automatically when the work outside finishes, with whatever data came back attached to the lead for the steps that follow.
The two blocks
Send to a webhook POSTs the lead, everything known about it plus everything earlier steps added, to any URL: a Zapier catch hook, Make, n8n, or your own endpoint. The payload also carries a callback_url.
Wait for a webhook parks the lead until something POSTs to that callback URL. When your Zap (or script, or colleague's tool) calls back, the lead wakes up and carries on from exactly where it stopped. Simple fields in the posted JSON, strings, numbers, booleans, are merged onto the lead, so later steps can branch on them or print them in emails.
If nothing calls back inside the window you set (30 days by default), the lead parks in Needs attention rather than continuing blindly.
Setting it up in five minutes
1. In your flow, add Send to a webhook and paste your Zapier catch-hook URL. 2. Directly after it, add Wait for a webhook. 3. In your Zap, do whatever the outside work is, then finish with a Webhooks by Zapier → POST step, posting to the callback_url field from step 1's payload. Any JSON body works; include the fields you want back. 4. Turn the flow on. Each lead flows out, waits, and resumes when your Zap answers.
The flow's inbound token authenticates the callback, it is minted automatically when you activate a flow that waits on a webhook, so there is nothing to configure on our side.
Three things this unlocks
External enrichment or scoring. Send each lead to your own qualifier, a spreadsheet lookup, a credit check, an internal API, and post back a score or qualified flag. Follow the wait step with a field branch: high scores get the premium sequence, the rest get the light touch.
Human approval outside Leadistry. Post the lead into a Slack approval Zap. When someone clicks approve, the Zap calls back and the emails start. Silence means nothing ever sends, a compliance-friendly gate for regulated teams.
CRM-first workflows. Create the deal in your CRM the moment a lead enrols, let your CRM automation do its thing, and only continue the email sequence once the CRM confirms the contact is not already a customer. The one-directional version covers pushing without waiting.
Data coming back
Whatever your Zap posts lands on the lead. Post deal and owner fields and later steps can branch with "if deal equals won", or a template can write the owner's name via a merge tag. Reserved and system fields are protected automatically, and oversized or exotic payloads are trimmed to the simple fields automations actually use.
Leads can enter from outside, too
The bridge works in both directions from the very start of a flow: every flow can mint a private inbound webhook URL, and anything POSTing a lead to it, a form tool, a Zap watching your calendar bookings, your own signup backend, enrols that lead at step one. Combined with the round-trip, Leadistry sits comfortably in the middle of an existing stack instead of demanding to be the whole of it.
Build the first one from a single sentence on the Flows canvas, and see the full automation guide for what the rest of the journey can do. Start free.
Leadistry maintains a live database of 5 million UK companies, enriched from the Companies House register with verified websites, business emails and social profiles. We write about the craft of finding and reaching the right businesses, first.
See how Leadistry works →