How to Send Paid-Ads Leads to Slack or Your CRM Automatically (2026)
The fastest way to route paid-ads leads is one of three standard methods: native CRM integrations (about 15 minutes, usually free), Zapier or Make middleware (about 30 minutes, most flexible), or direct webhooks (hours of dev time, full control and no middleware fees). Every minute between a lead form submit and a sales touch costs conversion — and by default, Meta lead ads sit in a CSV nobody downloads. This guide sets up all three routes for Meta and Google, designs the Slack alert properly, and closes the loop back to the ad account.
Built by our community of 2,000 marketers
Free skills and prompts for paid ads and SEO
Templates for Claude, ChatGPT and Perplexity.
Clients we work withClients we
work with
The three ways to route paid-ads leads, compared
All three methods end in the same place — a lead lands, a channel pings, a CRM row exists. They differ in setup effort, monthly cost, latency and how much you own. Pick by the row that matches your team, then jump to that method's section.
| Method | Setup time | Cost | Best for |
|---|---|---|---|
| Native CRM integrations | ~15 min | Usually free with your CRM | HubSpot or Salesforce shops that want zero new tools |
| Zapier / Make middleware | ~30 min | Free tier to roughly $30/mo at typical volumes | Slack alerts plus any CRM combination, no code |
| Direct webhooks / API | Hours (dev time) | Free to run | Dev teams needing custom routing and no per-task fees |
Start native if your CRM is HubSpot or Salesforce — ads to CRM natively, CRM to Slack natively, and you may be done in one sitting. Reach for Zapier or Make when the pieces don't natively connect or you want routing logic without engineering. Build direct webhooks when lead volume makes middleware pricing silly or the routing rules outgrow a no-code filter. The sections below walk through each, then cover the two things every method shares: what belongs in the Slack alert, and how to send conversion quality back to the ad platforms.
Get a free instant audit
Get a free, instant read on your paid ads or SEO — and fix it right away.
Paid ads audit
- Catch wasted spend & broad-match leaks
- Find account structure gaps
- Rank your quickest wins
- Spot PMax & brand-search overlap
- Check conversion-tracking health
- Benchmark CPC vs your industry
- Catch wasted spend & broad-match leaks
- Find account structure gaps
- Rank your quickest wins
- Spot PMax & brand-search overlap
- Check conversion-tracking health
- Benchmark CPC vs your industry
Free · no credit card · instant
SEO audit
- Find keyword & ranking gaps
- Catch technical SEO issues
- Rank your fastest wins
- Surface thin & duplicate pages
- Check indexing & crawl coverage
- Compare backlinks vs competitors
- Find keyword & ranking gaps
- Catch technical SEO issues
- Rank your fastest wins
- Surface thin & duplicate pages
- Check indexing & crawl coverage
- Compare backlinks vs competitors
Free · no credit card · instant
Method 1 — native integrations (start here)
If your CRM is one of the majors, the shortest path involves no third-party tools at all: the ad platforms connect to the CRM natively, and the CRM posts to Slack natively.
Meta lead ads → CRM
HubSpot, Salesforce and most major CRMs ship first-party Meta lead ads integrations. In Meta Business Suite: All tools → Instant Forms → CRM setup, connect the CRM, and map the form fields to CRM properties. Leads sync in near-real time from that point on — no CSV downloads, no polling. Field mapping is the step worth doing carefully: unmapped custom questions silently drop, and those answers are usually the routing signal sales needs.
Google Ads lead form assets → CRM
Google Ads supports webhook delivery per lead form asset: Assets → Lead form → lead delivery option → webhook. HubSpot and Salesforce both provide the webhook URL and key in their Google Ads integration settings — paste them into the form asset and test with Google's send-test-data button. Each form carries its own webhook config, so audit every active form when you change endpoints.
CRM → Slack
Both HubSpot and Salesforce post new-lead alerts to a Slack channel through their native Slack apps — workflow-triggered in HubSpot, flow- or alert-based in Salesforce. For many teams this completes the whole pipe with zero middleware: ads → CRM natively, CRM → Slack natively. The limitation to know up front: alert formatting and routing logic are only as flexible as the CRM's workflow builder, which is where the next method earns its keep.
Method 2 — Zapier or Make (most flexible)
Middleware is the default when the native pieces don't line up — a niche CRM, a Teams channel, routing rules, enrichment steps. The standard recipe takes about half an hour.
Set the trigger
"New Lead in Facebook Lead Ads" (or "Google Ads — new lead form entry"). On Zapier, the Facebook Lead Ads trigger is instant on paid plans — for speed-to-lead SLAs, that matters more than any other setting in the build.
Action 1: post the Slack message
Send a channel message containing the lead's name, email and phone, the campaign, ad set and creative, and the form answers. Mention the owner. The alert design section below covers what separates a useful alert from noise.
Action 2: create or update the CRM contact
HubSpot, Pipedrive, Attio and Close all have create-or-update actions. Use the update-if-exists variant keyed on email so a returning lead enriches the existing record instead of duplicating it.
Add a filter for routing (optional)
Route by form-field answers — budget above a threshold to #sales-priority, everything else to #leads. This one filter is most of what teams actually want from "lead scoring" and it costs nothing to add.
Test with a real form submit
Submit the actual form from a phone, not the platform's test tool alone — field names and formatting differ in production, and the five-minute test catches the mapping bugs that otherwise surface as a week of silent drops.
Choosing between them: Zapier is faster to build and has the larger app catalog; Make runs the same flow cheaper at volume and handles branching more gracefully. Free tiers cover low lead volumes on both — verify current task limits before committing an SLA to them. The one caveat that bites teams: polling triggers on cheap plans can add minutes of delay. If minutes matter, pay for instant triggers or use Method 3.
Ryze AI — Autonomous Marketing
The pipe routes leads. Something should improve the ads.
- ✓Ryze AI manages campaigns on your conversion-quality signal
- ✓Google, Meta and more from $89/month flat
- ✓3-day trial for $1, cancel anytime
2,000+
Marketers
$500M+
Ad spend
23
Countries
Method 3 — direct webhooks (no middleware fees, full control)
With a developer available, the whole pipeline is one small service: both ad platforms speak webhooks, and Slack accepts them. You trade middleware fees for owning the plumbing.
Meta: the leadgen webhook
Create a Meta app, subscribe an endpoint to the leadgen webhook on your Page, and on each event fetch the full lead by ID from the Graph API (the webhook payload carries the ID, not the answers). From there, fan out: post to Slack, write to the CRM's API. The operational work is token management — Page access tokens need rotation handling, and a silently expired token is the classic failure mode of DIY lead pipes.
Google: point the form at your endpoint
Google Ads lead form assets deliver directly to any webhook URL with a key you set — no app review, no intermediary. Validate the key on every request, return 200 quickly, and process asynchronously; slow endpoints get retried and produce duplicates downstream if you have no dedupe.
Slack: incoming webhooks are enough
An incoming webhook URL per channel covers internal alerting — no app review needed for your own workspace. Format with Block Kit for the one-tap contact links described below. A single serverless function handles all of the above; the honest trade is that retries, dedupe, token rotation and monitoring are now your pager's problem, which is exactly what the $30/month to Zapier was buying.
What to put in the Slack alert (the part everyone under-designs)
Most lead alerts are a name and an email in a channel nobody watches. The difference between that and a working speed-to-lead system is four design decisions, none of them technical.
- One-tap contact, not a string — render the lead's name with mailto and tel links so the rep on a phone taps once to call. An email address pasted as plain text adds a copy-paste step to every single lead, forever.
- Campaign, ad set and creative in the message — sales sees the context they're walking into, and marketing gets creative-level quality feedback for free by reading which alerts turn into thread activity.
- Form answers verbatim — budget and timeline answers are the routing signal; truncating or omitting them turns a qualified lead alert back into a name and an email.
- An owner mention and a claim convention — mention the on-duty rep and agree that a ✅ reaction means claimed. An alert without an owner is a notification, not a workflow, and unclaimed leads are the silent failure mode of every lead channel.
One addition worth stealing from support teams: a daily unclaimed-leads sweep — anything without the claim reaction after an agreed window gets re-mentioned to a fallback owner. It costs one scheduled message and closes the gap every SLA quietly dies in.
Closing the loop back to the ad account
Routing leads out is half the plumbing. Sending conversion quality back in is the half that improves the ads — and most teams never build it.
Why outbound-only routing leaves money on the table
With only form fills as the conversion signal, the ad platforms optimize toward people who fill forms — including the ones who type gibberish. The platforms can optimize toward down-funnel quality, but only if you send it: they need to know which leads a human eventually marked qualified, opportunity or closed.
The mechanism: offline conversions
When the CRM stage changes to qualified or closed-won, push that event back — Meta's Conversions API for lead events, Google's enhanced conversions for leads — matched on the lead's email or the click identifiers captured at submit. Both HubSpot and Salesforce can send these natively, Zapier and Make both have actions for them, and a direct-webhook build adds one more outbound call on stage change. Our guide to tracking offline conversions in Meta Ads covers the Meta side in detail.
What changes once the signal flows
The campaigns start optimizing toward leads that close instead of leads that submit, which over time shifts budget toward the audiences and creatives producing revenue rather than volume. This closed loop is also where automated ad management earns its keep: Ryze AI — our product, bias stated — is an autonomous AI marketer that manages the campaigns on top of exactly this signal ($89/month, 3-day trial for $1); the lead-routing plumbing itself, any of the three methods above handles without us.
Troubleshooting: when leads arrive late or not at all
Lead pipes fail quietly — nothing errors, the channel just goes still. The causes rank in a predictable order.
- Late leads: a polling trigger on a cheap plan — the most common cause by far. Polling intervals on free middleware tiers can add minutes; move to an instant trigger or a native integration.
- No leads: an expired token or permission — Meta integrations depend on Page access that expires or gets revoked when the connecting user changes roles. Reconnect the integration and prefer system users over personal logins where offered.
- Some leads missing: unmapped or renamed form fields — editing a lead form after connecting it silently breaks field mapping in most tools. Re-test the pipe after any form edit, every time.
- Duplicates: retries without dedupe — slow endpoints get retried by both platforms. Dedupe on the platform's lead ID, not on email, or legitimate repeat leads disappear too.
- Everything works but nobody acts: no owner convention — the pipe is fine; the workflow is missing. Fix it with the owner mention and claim reaction, not with more integrations.
The single habit that prevents most of these: submit one real test lead from a phone every week — a two-minute ritual that converts silent failures into Monday-morning fixes. Put it in the same calendar slot as checking the ad account.
Alex M.
VP Growth
Multi-Brand Ecommerce Group
We had five channels and five people each defending their own budget. Handing allocation to Ryze AI cut blended CAC 27% in a quarter — not because the bidding got smarter, but because money finally moved to whichever channel was winning that week.”
27%
Blended CAC reduction
5
Channels automated
12 weeks
To full autonomy
1,000+ marketers use Ryze
Automating hundreds of agencies
Which method should you build?
Route by two facts: what CRM you run, and whether anyone on the team ships code. Find your profile.
HubSpot or Salesforce shop
Recommended: fully native — ads to CRM via the first-party integrations, CRM to Slack via the native Slack app.
Fifteen minutes per platform, no new subscriptions, and the offline-conversion loop is also available natively later. Move to middleware only when routing rules outgrow the CRM's workflow builder.
Niche CRM, no developers
Recommended: Zapier (fastest to build) or Make (cheaper at volume) — trigger, Slack message, CRM upsert, optional routing filter.
Pay for instant triggers if response time is an SLA; polling delay on free tiers is the classic silent tax on speed-to-lead.
Dev team on hand, real lead volume
Recommended: direct webhooks — Meta's leadgen subscription plus Google's per-form webhook into one serverless function.
No per-task fees and full routing control; the trade is owning retries, dedupe and token rotation. Worth it once middleware pricing scales past pocket change.
High-stakes speed-to-lead (sales calls in minutes)
Recommended: native or webhook delivery — anything instant — plus the owner-mention and claim convention, plus the weekly test lead.
At this tier the alert design and the human convention matter more than the transport; a perfect pipe into an unwatched channel converts nothing.
Quick decision framework
- If your CRM is HubSpot or Salesforce → native end to end, done in a sitting
- If the pieces don't natively connect → Zapier or Make, instant triggers if speed matters
- If volume makes middleware pricing silly → direct webhooks, one serverless function
- If leads arrive but nobody acts → fix the alert design and claim convention, not the pipe
- If the ads should improve from lead quality → add the offline-conversion loop, whatever the method
Two adjacent guides pair well with this one: Meta Ads for B2B lead generation covers the campaign side of the leads you're routing, and conversion tracking setup for Meta Ads covers the tracking foundation the offline loop builds on.
The one-afternoon setup playbook
The full pipe — both platforms, Slack, CRM, and the quality loop scheduled — fits in an afternoon for methods 1 and 2. In order:
Connect Meta lead ads to the CRM
Meta Business Suite → All tools → Instant Forms → CRM setup. Connect, then map every field — including custom questions, which are the routing signal. Native integration if your CRM has one; otherwise the middleware trigger.
Wire Google lead form assets
For each active lead form asset: Assets → Lead form → lead delivery → webhook, paste the URL and key from your CRM or endpoint, and fire the test-data button. Repeat per form — the config does not inherit.
Build the Slack alert
Channel message with one-tap contact links, campaign/ad set/creative, form answers verbatim, and the owner mention. Agree the claim-reaction convention with sales in the same conversation — it is a five-minute meeting.
Add the routing filter
One filter on the qualifying form field: high-budget or near-term answers to the priority channel with the senior rep mentioned, everything else to the standard channel.
Submit a real test lead from a phone
The production form, not the test tool. Verify the Slack message renders, the links tap through, the CRM row is complete, and the right person got mentioned. Then recur it weekly.
Schedule the offline-conversion loop
Wire CRM stage changes (qualified, closed-won) back to Meta's Conversions API and Google's enhanced conversions for leads. This is the step that makes the ad platforms optimize toward leads that close — skip it and the pipe routes volume forever.
Frequently asked questions
How do I send Facebook lead ads to Slack instantly?
Two good routes: Zapier's instant Facebook Lead Ads trigger feeding a Slack channel-message action is the fastest no-code build, and if you already sync leads to HubSpot or Salesforce, their native Slack apps post new-lead alerts at no extra cost. Avoid polling triggers on free middleware plans when response time matters — they can add minutes.
Can Google Ads lead forms post to a webhook without middleware?
Yes. Each lead form asset supports direct webhook delivery — Assets → Lead form → lead delivery option → webhook — with a URL and key you set. Point it at your own endpoint or at the webhook URL your CRM's Google Ads integration provides. The configuration is per form, so set it on every active lead form asset.
What is the cheapest way to route paid-ads leads to a CRM?
Native integrations, if your CRM has them — HubSpot, Salesforce and most majors connect to Meta lead ads and Google lead forms free with the subscription you already pay for. Next cheapest is a direct webhook build (free to run, costs dev time), then middleware, whose free tiers cover low volumes before paid plans start around tens of dollars monthly.
Why are my Meta leads arriving late?
Usually a polling trigger on a free middleware plan — polling intervals add minutes by design — or a CRM sync running on a schedule rather than in real time. Move to an instant trigger (Zapier's Facebook Lead Ads trigger is instant on paid plans), a native integration, or a direct leadgen webhook subscription, all of which deliver in near-real time.
Why did my lead notifications stop working entirely?
Check three things in order: an expired or revoked Meta access token (reconnect the integration — this is the most common cause), a form edit that silently broke field mapping (re-test after any form change), and a changed webhook URL or key on Google lead form assets. A weekly real test lead from a phone catches all three before they cost a pipeline.
What should a lead alert in Slack contain?
Four things: the lead's name with one-tap mailto and tel links, the campaign, ad set and creative for context, the form answers verbatim — budget and timeline drive routing — and an owner mention with an agreed claim convention such as a checkmark reaction. An alert without an owner is a notification, not a workflow.
Should I use Zapier or Make for lead routing?
Zapier is faster to build, has the larger app catalog, and its Facebook Lead Ads trigger is instant on paid plans — the deciding feature for speed-to-lead teams. Make runs the same flow cheaper at volume and handles branching logic more gracefully. Both free tiers cover low lead volumes; verify current task limits before relying on either for an SLA.
How do I route high-value leads to a different channel?
Add a qualifying question to the lead form — budget range or purchase timeline — then filter on the answer: in Zapier or Make, one filter step routes above-threshold leads to a priority channel with the senior rep mentioned; in native CRM workflows, a property-based branch does the same. This single filter delivers most of what teams want from lead scoring.
What are offline conversions and why do they matter for lead ads?
Offline conversions are down-funnel outcomes — qualified, opportunity, closed-won — pushed from the CRM back to the ad platforms via Meta's Conversions API or Google's enhanced conversions for leads. Without them, campaigns optimize toward form fills including junk; with them, budget shifts toward the audiences and creatives that produce leads that actually close.
Can I do all of this without writing any code?
Yes. Native CRM integrations cover ads-to-CRM and CRM-to-Slack for HubSpot and Salesforce shops, and Zapier or Make covers every other combination — triggers, Slack messages, CRM upserts, routing filters and offline-conversion actions are all no-code. Direct webhooks exist for teams that want zero middleware fees and full control, not because code is required.
Does this work for Microsoft Teams instead of Slack?
Yes — the same three shapes apply. Teams accepts incoming webhooks per channel, Zapier and Make both have Teams message actions, and the CRM-native route works through the HubSpot and Salesforce Teams apps. The alert design rules are identical: one-tap contact, campaign context, verbatim form answers, and a named owner.
What does Ryze AI do in this workflow?
The ad side, not the plumbing. Ryze AI — our product — is an autonomous AI marketer that manages Google, Meta and other campaigns on top of the conversion-quality signal the offline loop sends back, deciding and executing changes 24/7 for $89/month flat with a 3-day trial for $1. The lead routing itself, any of the three methods in this guide handles without us.
Related guides
Track Offline Conversions in Meta Ads with AI
The Meta side of the closing-the-loop section, in detail
AI Meta Ads for B2B Lead Generation
The campaign side of the leads this guide routes
Meta Ads Conversion Tracking Setup for Beginners
The tracking foundation the offline loop builds on
AI-Automated Client Reporting for Agencies
Turning the same lead data into client-facing reporting
Ryze AI — Autonomous Marketing
Close the loop, then let it run
- ✓Autonomous ad management on top of offline conversions
- ✓Decides, executes and re-measures around the clock
- ✓3-day trial for $1, cancel anytime
2,000+
Marketers
$500M+
Ad spend
23
Countries
