Send New UK Leads Straight to Your CRM: Webhooks, Zapier and Slack

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 CRM automatically with no manual export. Webhooks and Slack are on every plan, including the free trial. If you would rather your tool fetched the leads itself, your leads link does that on any paid plan.

Most teams lose leads in the gap between "the data exists" and "someone acted on it". A lead nobody on your team has seen is not a lead in your pipeline. Integrations close that gap by pushing each delivered company, already checked, into the tools your team already lives in, the second it exists.

What are Leadistry integrations?

Everything below lives under Apps in the app, in the part called For developers. Two of the channels fire automatically on the same two events: a new delivered lead (the event is named lead.delivered), and a new reply (reply.received). The third waits to be asked. All three send outwards only. Nothing travels back from your CRM into Leadistry.

• 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. Every delivery is signed, so your endpoint can verify it came from us.
• Slack. Create an incoming webhook in Slack for the channel you want and paste its address into Leadistry. New leads and replies post as short messages, so the right people see them without opening anything else.
• Your leads link. One button makes a private address that serves your leads: as a CSV for Google Sheets, and as JSON for Zapier, Make or your own code. Nothing is pushed; your tool reads the link when it wants. New leads into Google Sheets automatically walks through it.

Webhooks and Slack are available on all plans (Free Trial, Growth, Pro and Scale), and the leads link comes with any paid plan. 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 is already checked. The payload carries the company name, its Companies House number, its SIC code, the website, the business email 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. No phone numbers, ever. The written first email stays on the Feed, where you approve, change or skip it. 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 lead to a CRM record.

1. 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.
2. Add the webhook in Leadistry. Open Apps under Set up, then For developers. Choose "Zapier, Make or your own", paste the destination URL and press Add it. Both events go to every connection, and each payload names its event, so you can filter at the other end.
3. Map the fields. In your Zap, Make scenario or CRM inbound step, map the payload fields (company name, company number, SIC code, website, email, director) to your CRM's fields. Do this once.
4. Add a de-dupe guard. Match on company number or email so re-runs never create duplicate records. Companies House company numbers are unique and stable, which makes them the ideal key.
5. Fire a test lead and confirm. Press "Send a test lead" on the connection, watch it arrive at the other end, then let it run.

Once that is live, every lead your agent delivers, whether it matched on a SIC code and a postcode or on the poor-website grade, lands in your CRM the moment it is delivered. You can start a free trial and have this wired up in an afternoon.

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 as soon as Leadistry sees it.

• In Slack, create an incoming webhook for a channel like #replies or #sales-inbox.
• Paste its address under Apps, then For developers, with "A Slack webhook" selected.
• When a prospect answers an email your agent sent, Leadistry stops every follow-up to that company and posts a short alert to Slack naming the company.

Your rep sees the alert, opens the reply in their own inbox or on the Desk, where an answer is already drafted, and responds while it is fresh. No one is refreshing an inbox hoping for movement. (Reply events need emails going out. The free trial includes 25 free emails from your own mailbox, 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 replies by how they were sorted

The reply webhook carries the prospect's email address, the company, the subject, a short snippet and a simple label for the kind of reply: interested, not interested, out of office, wrong person, or other. The label comes from plain word rules, so treat it as a first sort rather than a verdict. It still lets you branch in Zapier or Make before anything reaches your CRM.

• Interested: create or update the CRM record and assign it to a rep straight away.
• Wrong person: tag the record so someone finds the right contact.
• Out of office: no action, or a note on the record.
• Not interested: mark the record closed so nobody writes again.

The same trick works on new leads. Each lead payload carries its SIC code, so you can send different trades to different owners or lists. This keeps your CRM clean. You are triaging at the point of ingestion, not after a human has already touched every row.

Recipe: pair webhooks with signals for next-morning outreach

Your agent is a standing watch: the trades, the area, and the reasons to get in touch, such as a new incorporation, accounts or a confirmation statement coming due, or a website graded poor. It looks all day and puts new matching companies on your Feed, each with its website, its email and the first email written.

Add a webhook and the same leads reach the rest of your tools: a company registered in Leeds gets a website and an email address, the agent catches it within minutes, 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 contacting anyone new.

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 path with your 25 free trial leads before paying anything. Reply events work on the trial as well, because the trial includes 25 free emails 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. There is no built-in HubSpot, Pipedrive or Salesforce connection for customers yet, so those go the same way as any other system: through Zapier, Make or your own endpoint. It is one-way: Leadistry pushes out, and nothing in your CRM changes anything in Leadistry.

What data is in the webhook payload?

For a new lead: the event name, company name and number, SIC code, website, the business email and whether it passed our check, the director's name when we have it, the town and postcode, the dated reason, and the delivery time. For a reply: the prospect's email address, the company, the subject, a short snippet and a simple label for the kind of reply. No phone numbers, ever.

When exactly does the webhook fire?

On two events. First, the moment a lead is delivered. Second, when a prospect replies to an email your agent sent. Both go to every connection, on any plan, and each payload names its event. See pricing for what each plan includes, and grab the Chrome extension to identify any UK company and its director while you browse.