Zapier Lead Automation: Push Every New Lead and Reply Into Your Own Tools
Leadistry pushes two events out to Zapier, Make, Slack or your own webhook: a finished lead arriving and a reply coming in. Here is the five-minute setup, what each event carries, and three automations to build.
Zapier lead automation with Leadistry comes down to two events. When a finished lead is delivered, Leadistry pushes it out. When somebody replies to one of your emails, Leadistry pushes that out too. Point both at Zapier and every new lead and every reply can land in your CRM, a spreadsheet or a team channel within seconds, without anybody copying and pasting.
An earlier version of this post described a round trip: send a lead out, wait, and pull the result back in. That went when the old product was replaced by Leadistry V2. Integrations now run one way, outwards, and this post describes what exists today.
The two events
- lead.delivered. A finished lead just arrived. Drop it in your CRM, a sheet, or the channel your team looks at.
- reply.received. Somebody wrote back. Create a deal, alert whoever handles enquiries, start a task before it goes cold.
Each one is sent the moment it happens, never in a batch you wait for. Leads go one event per lead, so your Zap handles a single company at a time rather than unpicking a list.
Setting it up in five minutes
- In Zapier, start a new Zap with Webhooks by Zapier as the trigger, choose the catch hook, and copy the URL it gives you.
- In Leadistry, open Apps under Set up, then For developers. Choose "Zapier, Make or your own", paste the URL and press Add it. The connection listens for both events.
- Press Send a test lead. Zapier catches it, so you have real field names to map from.
- Build the rest of the Zap: create the CRM record, add the spreadsheet row, post the message. Turn it on.
Make works the same way with its own webhook address. Slack is simpler still: paste a Slack incoming webhook address instead and the channel gets a one-line summary, with no Zap in between. Any connection can be paused, resumed or removed from the same screen.
Tell us who you sell to. We find them, with a real email. 25 free leads, no card.
What arrives
A lead.delivered event carries the company name, the company number, the SIC code, the website, the email address and whether it passed our check, the director's name when we have it, the town and postcode, the dated reason to get in touch, and the time it was delivered. There is never a phone number, because Leadistry does not supply them.
A reply.received event carries the company, the address that replied, the subject line, a short snippet of the reply, and a simple label for the kind of reply (interested, not interested, out of office and so on). The label comes from plain word rules, so treat it as a first sort.
If you are sending to your own endpoint rather than Zapier, every delivery is signed. It carries an X-Leadistry-Timestamp header and an X-Leadistry-Signature header, and your signing secret sits beside the address under Apps, For developers, so your developer can check that a request really came from us.
Three automations worth building
Every new lead into your CRM. Trigger on the lead event and create or update the company in your CRM. Use the company number as the unique key, so the same company is never created twice however many tools touch it. The CRM, webhook and Slack guide covers the CRM side in more detail.
Every reply into a deal and an alert. Trigger on the reply event, add a Zapier filter so out-of-office replies go no further, then create the deal and message whoever handles enquiries. Inside Leadistry the reply has already stopped everything to that company, and opening it on the Desk drafts an answer for you to send, so the Zap is only there to make sure the rest of your business knows.
A running log in a spreadsheet. One row per lead, one row per reply. It is the simplest Zap there is, and after a month you have your own record of what arrived and who wrote back.
What it does not do
Worth being plain about, because the old version of this post promised more:
- Nothing comes back in. A Zap cannot pause a lead, resume one, or write a score onto it. What your Zap does with the data stays in your own tools.
- Approval stays in Leadistry. You approve, change or skip each email on the Feed, and Autopilot is off unless you switch it on there. A Zap cannot approve a send.
- Stopping on a reply does not depend on your Zap. A reply stops everything to that company whether or not anything is connected.
If what you wanted from the round trip was to work your leads from another tool, the closer fit today is connecting your own Claude, which can read the Feed and write pitches but approves nothing without you. And if you would rather not automate at all, the Leads screen downloads exactly the rows you are looking at as a CSV, and Exports (Set up, then Exports) keeps a monthly and a weekly statement of every lead you get, both on any paid plan. If what you want is a spreadsheet that fills itself, your leads link in Google Sheets does it without a Zap.
Where to start
Everything here is covered on the Apps page. Describe who you sell to in a two-minute chat, let your agent bring the first leads into the Feed, then connect Zapier and press the test button. Start free with 25 leads and no card.