Route Warm LinkedIn Leads to HubSpot With Signed Webhooks

A warm LinkedIn lead is only useful if someone can act on it in the same hour it appears. If the person sits in a product tab until Friday, the comment they left is already cold.

Embers is built around a ranked Priority Queue from supported public LinkedIn signals, then a short routing path: Slack lead cards, a native HubSpot destination, and signed HTTPS webhooks that Zapier, Make, or Clay consume as recipes. All three are Solo and above, and all three are set up by an account administrator. This guide is the conversion path, not a feature wishlist. I run Embers, and every plan limit below matches what is live today.

If you are still choosing a signal tool, start with the LinkedIn buying signal tools matrix. If the question is Traxy versus this stack, use Embers vs Traxy.

Why warm LinkedIn leads stall before they reach the CRM

Most teams already have a CRM and a chat tool. The gap is the handoff.

Public engagement is a buying signal, not a closed-won. Someone reacted to a post, replied to a comment you left, engaged on a watched profile, or used a keyword your buyers use. That moment is useful only if the right person sees the evidence, the ICP reason, and a way to follow up without copying fields into five tabs.

The stall usually looks like this:

• The lead is qualified in one product.
• Slack never sees it, so the seller keeps checking a dashboard.
• HubSpot stays empty until someone pastes a name.
• Automation tools wait on a CSV.

Embers does not automate LinkedIn. It does not ask for your password, cookies, or a Chrome extension. Outreach stays a draft you send yourself. The job this guide covers is routing the qualified person into the stack you already run.

What Embers routes today

Four public sources feed the queue: engagement on your posts, replies and reactions to comments you leave, engagement on selected competitor posts, and keyword mentions. Watched public profiles (competitors, influencers, investors, or teammates) sit on a per-account cap: 5 on Solo, 10 on Team. There is no separate competitor count.

From that queue you can route in three live ways:

Every destination screen is administrator only. Free can read the lead list and the dashboard; it cannot route anything out of Embers.

Zapier, Make, and Clay are not native Embers SDKs. They consume the signed webhook as recipes. That distinction matters if you are comparing a HubSpot button with a catch-hook.

The Slack delivery and lead webhooks pages are the product references. This post is the order to turn them on.

Review the Priority Queue

Start in Embers, not in HubSpot.

Each qualified lead keeps the post or comment that surfaced them, an ICP reason, and a suggested next action. Suggested messages stay drafts. You review who to contact, then send the LinkedIn message yourself. That is the same manual workflow described in the engagement-to-DM playbook.

A lead enters the default Leads view and can trigger a new-lead webhook only when they match your ICP or you approve them. People who do not match remain available in the broader engager view. They do not fire a new lead event. Webhook delivery waits for profile enrichment to finish so role and company details are more complete.

Do not skip this review. Routing a raw engager list into HubSpot just recreates a cold pile with a CRM logo on it.

Send lead cards to Slack

Connect Slack from Settings → Integrations. Install the workspace, pick a channel, and send a test. After that, new lead cards post when someone qualifies.

Every alert includes why they are a fit plus the evidence, so a seller can reply without opening Embers. Contact fields stay on the payload when the lead is already enriched.

Slack is the fastest check that routing works. If the card looks right in a channel your team already reads, HubSpot and webhooks are copying a known-good event, not inventing a second source of truth.

Connect native HubSpot on Solo+

Native HubSpot is a separate destination from webhooks. It is available on Solo and above. Free does not include it.

Connect it from Settings → Integrations on a paid plan. Use this when HubSpot is the system of record and you want a first-party destination instead of a catch-hook. Teams that only need Zapier, Make, Clay, or an internal endpoint can skip this step and stay on signed webhooks.

Solo is $49 per month billed monthly. Team is $99. Signal War Room is $999. Full limits sit on the pricing page.

If you are still on Free, upgrade before you try to map fields through a recipe. Every destination, native or webhook-driven, starts at Solo.

Add signed webhook endpoints

Signed webhooks are Solo and above. An account administrator can configure up to 10 HTTPS endpoints.

Supported events:

• lead.created when a qualified lead enters the queue
• lead.status_changed when a lead’s pipeline status changes
• report.generated when a report is ready

Every request is signed. Stable event IDs and delivery metadata let the receiving system verify the request and deduplicate it. Failed deliveries retry automatically for seven days. You get 30 days of delivery history, and an admin can replay failed events. Webhooks are one-way. They are not a two-way CRM sync.

Implementation is the same three steps as the webhooks page: add an HTTPS URL you control, verify the signature before you process the payload, and treat event IDs as idempotent keys so retries do not create duplicate HubSpot records.

Consume Zapier, Make, or Clay as recipes

Point a signed endpoint at a Zapier catch hook, a Make custom webhook, a Clay source, or an internal service. Those tools are recipes sitting on top of the same signed event. They are not native Embers SDKs, and they do not add destinations Embers does not have.

That is how you get a HubSpot workflow driven by the raw webhook body instead of the native destination, or a Clay enrichment table that starts from a signed lead.created event. It is not a hidden Meta Ads or n8n connector.

What lead.contact includes

Webhook payloads carry stored lead.contact (email and phone) when a lead is already enriched, and omit the object entirely when it is not. Slack cards, the native HubSpot contact, and the native HeyReach push follow the same rule.

Enrichment is the gate here, not the plan: every destination is already Solo and above. An unenriched lead arrives with a score, the evidence, and no contact fields, and Embers never invents an address to fill the gap.

Contact information is included when available on Solo, Team, and Signal War Room. Enrichment is not a promise that every lead has a phone number.

What Embers has natively, and what it does not

Slack, HubSpot, and HeyReach are native destinations, each with its own delivery rules for minimum score, ICP only, sources, and excluded titles and industries. Meta Ads and n8n are not native destinations, and there is no public REST API. If those are the job, Traxy is the closer fit. Traxy also advertises unlimited tracked profiles on Pro. Embers watches 5 public profiles on Solo and 10 on Team.

Embers itself never sends connection requests, messages, comments, or reactions on LinkedIn. HeyReach does. Embers pushes leads and reads results, which is why the HeyReach destination changes where a lead goes without changing what Embers is. If a vendor needs your LinkedIn password, cookies, or an extension to “route” leads, that is a different product category. See the LinkedIn automation restrictions record before you add that class of tool to the same stack.

Pricing for this workflow

• Solo: $49 per month billed monthly ($39 billed annually). 1 connected LinkedIn account, 5 watched public profiles, 10 keywords. Native HubSpot. Stored lead.contact when enriched. Signed webhooks.
• Team: $99 per month billed monthly ($79 billed annually). 2 connected LinkedIn accounts included, with more at $59 per month when that add-on is offered, 10 watched public profiles, 25 keywords per account. Same routing, plus team invitations, white-label reports, and priority support.
• Signal War Room: $999 per month. Scoped with the Embers team.

Slack, native HubSpot, and signed webhooks all start at Solo, and all three are configured by an account administrator. Solo and Team include a card-required 7-day trial. The free Signal Audit is a sample of qualified public signals, not the full product, and it does not require a payment method.

Frequently asked questions

Does Embers have a native HubSpot integration?

Yes, on Solo and above. Connect it from Settings → Integrations. Free does not include the native HubSpot destination.

Which Embers plans include signed webhooks?

Solo and above. An account administrator can send signed new-lead, lead-status, and report-ready events to up to 10 HTTPS endpoints. Slack and native HubSpot are on the same plans.

Are Zapier, Make, and Clay native Embers SDKs?

No. Zapier, Make, and Clay consume the signed webhook as recipes. They are not native Embers SDKs.

Does a webhook payload include an email and phone number?

Only when the lead has already been enriched. Webhooks are Solo and above, and their payloads carry stored lead.contact (email and phone) when Embers has it. Nothing is invented.

Does Embers send LinkedIn messages or need my LinkedIn password?

No. Embers does not require your LinkedIn password, cookies, or a Chrome extension. Every LinkedIn action stays manual. Suggested messages remain drafts you review and send yourself.

Does Embers ship native Meta Ads or n8n destinations?

No. Embers routes through Slack, native HubSpot, and native HeyReach on Solo+, plus signed-webhook recipes for Zapier, Make, or Clay, and exposes an MCP server for AI assistants. Meta Ads and n8n are not Embers-native destinations, and there is no public REST API.

If the queue is already producing people you would message this week, route Slack first, then HubSpot or a signed webhook. Do not wait for a destination Embers does not have.