Send New UK Leads Straight to Your CRM: Webhooks, Zapier and Slack
Leadistry fires an outbound webhook and a Slack message the moment a new UK lead is delivered or a prospect replies. Here is how to wire those events into your CRM, Zapier, Make or a team channel, on any plan.
To send new UK leads to a CRM webhook, connect Leadistry's outbound webhook to a URL your CRM (or Zapier, Make or a custom endpoint) can receive. Leadistry then fires a JSON payload the moment a lead is delivered, and again when a prospect replies, so records land in your pipeline automatically with no manual export. Webhooks and Slack are on every plan, including the free trial.
Most teams lose leads in the gap between "the data exists" and "someone acted on it". A lead sat in a dashboard is not a lead in your pipeline. Integrations close that gap by pushing each delivered company record, fully enriched, into the tools your team already lives in, the second it exists.
What are Leadistry integrations?
Leadistry ships two integration channels that both fire automatically on the same two events: a new delivered lead, and a new classified reply.
- Outbound webhooks. A webhook is an automated HTTP POST that Leadistry sends to a URL you control. When an event happens, we push a JSON payload to that URL. Because it is a plain webhook, it works with Zapier, Make, n8n, or any endpoint your developers stand up, which in practice means it works with any CRM.
- Slack. Connect a Slack workspace and pick a channel. New leads and replies post as messages, so the right people see them without opening a dashboard.
Both are available on all plans (Free Trial, Growth, Pro and Scale). You do not need to be sending to use them. Even on the free trial you can pipe your 25 free leads straight into your CRM to test the plumbing end to end.
Every lead that fires through a webhook or Slack is already enriched. That means the payload carries the website URL, a verified business email (extracted and MX-checked, shown with a verified tick in the app), the director name, a transparent 0-100 lead score, and any add-ons you bought for the lead (director LinkedIn, company LinkedIn, Facebook, Instagram). No phone number, because UK PECR forbids unsolicited marketing calls and we do not pretend otherwise. So the record that lands in your CRM is a working record, not a name you have to go and research.
How to send new leads to your CRM (step by step)
Here is the fastest reliable path from a Leadistry search to a CRM record.
- Decide the destination. If your CRM accepts inbound webhooks natively, use that URL. If not, use Zapier or Make as the middle layer and point Leadistry at the Zap or Scenario's catch-hook URL.
- Add the webhook in Leadistry. In Integrations, paste the destination URL and choose the "new delivered lead" event.
- Map the fields. In your Zap, Make scenario or CRM inbound step, map the payload fields (company name, website, verified email, director, LinkedIn, lead score) to your CRM's fields. Do this once.
- Add a de-dupe guard. Match on company number or verified email so re-runs never create duplicate records. Companies House company numbers are unique and stable, which makes them the ideal key.
- Fire a test lead and confirm. Deliver one lead, watch it arrive in the CRM, then let it run.
Once that is live, every company you pull, whether from a SIC code and postcode search or from the poor-website filter, flows into your pipeline the moment it is delivered and enriched. You can start a free trial and have this wired up in an afternoon.
Tell us who you sell to. We find them, with a real email. 25 free leads, no card.
Recipe: ping a Slack channel when a prospect replies
Replies are time-sensitive. A prospect who answers at 9:14am is worth ten who answer next week, but only if someone sees it. This recipe puts every reply in front of your team instantly.
- Connect Slack and choose a channel like #replies or #sales-inbox.
- Enable the "new reply" event.
- When a prospect responds to an outreach sequence, Leadistry's reply inbox classifies the response, then posts it to Slack with the company, the director and the message.
Your rep sees the reply, opens the lead brief, and responds while intent is still hot. No one is refreshing a dashboard hoping for movement. (Reply events need a sequence running. The free trial sends to its first 25 prospects, so replies fire there too, and sending past that is included on every paid plan from £29/mo. New-lead webhooks and Slack messages work on every plan, sending or not.)
Recipe: route leads by score before they hit the CRM
Because the payload includes the transparent 0-100 lead score, you can branch in Zapier or Make before anything reaches your CRM.
- Score 80 and above: create the CRM record and assign it to a rep straight away.
- Score 50 to 79: create the record but tag it "nurture".
- Below 50: hold it, or send it to a separate list for review.
This keeps your CRM clean and stops reps wasting time on the weakest records. You are triaging at the point of ingestion, not after a human has already touched every row.
Recipe: pair webhooks with Signals for same-day outreach
Leadistry's Signals feature (on all plans) lets you create watches: a SIC prefix plus a city plus an optional poor-website filter, with triggers for new incorporation, accounts due soon, or confirmation statement due soon. A daily matcher scans the ~5M-company UK register and posts matches to an arrivals board.
Wire a webhook to those delivered leads and you have a same-day pipeline: a company is incorporated in Leeds, the matcher catches it, it is enriched, and the record is in your CRM (and a Slack channel) before a competitor has even seen it. This is how teams get to recently incorporated companies first.
A quick note on compliance
Automating delivery does not change your obligations. Leadistry operates on a UK GDPR legitimate-interest basis with a documented ICO LIA, honours data-removal requests within 24 hours, and enforces director and company suppression lists. The do-not-contact list is applied at import and again at send time. If you are formalising your own basis, our UK B2B data and GDPR guide walks through the LIA. Pushing a record to your CRM by webhook sits comfortably inside that framework, because you are moving data you already lawfully hold, not calling anyone.
Frequently asked questions
Do I need a paid plan to use webhooks?
No. Outbound webhooks and Slack are on every plan, including the free trial. You can test the full delivery flow with your 25 free trial leads before paying anything. Reply events work on the trial as well, because the trial sends to its first 25 prospects from your own mailbox. Sending beyond those 25 is included on every paid plan.
Which CRMs does Leadistry integrate with?
Any CRM that accepts an inbound webhook, directly or through Zapier or Make. Because Leadistry fires a standard JSON webhook, there is no fixed integration list: HubSpot, Pipedrive, Close, or a custom system all work through the same mechanism.
What data is in the webhook payload?
The full enriched record: company name and number, website URL, a verified MX-checked business email, director name, the 0-100 lead score, and any social add-ons on the lead. No phone number, in line with UK PECR.
When exactly does the webhook fire?
On two events. First, the moment a lead is delivered and enriched. Second, when a prospect replies to an outreach campaign and the reply inbox classifies it. You can enable either or both, on any plan. See pricing for what each plan includes, and grab the Chrome extension to identify any UK company and its director while you browse.