Send ranked leads
where your team works.
Embers never acts on LinkedIn. It hands each ranked lead, with the reason it surfaced, to the tools that send, store, and notify.
13 destinations · native · webhook recipes · AI assistants · CSV
Browse by what it is for
Sending tools
They run the sequence. Embers hands them the lead and the reason.
- HeyReach
Push each agent's qualified leads into its own HeyReach campaign or lead list, with the signal, the ICP reason, and the score as custom fields.
- Instantly
Push a qualified lead into an Instantly campaign or lead list, with the signal as the opener. A missing email is looked up first on paid plans.
- Smartlead
Push a qualified lead into a Smartlead campaign, with the signal as the embers_signal custom field. A missing email is looked up first on paid plans.
- Emelia
Push a qualified lead into an Emelia campaign or contact list, where one sequence mixes LinkedIn and email steps, with the signal as a custom variable.
Alerts and CRM
Where your team sees a lead first, and where it is kept.
- Slack
Post qualified leads into one Slack channel with the score, why they match, the evidence, and a suggested opening line.
- HubSpot
Create or update a HubSpot contact, with one note on the signal that qualified the lead when the contact is created.
Webhooks and automation
Signed events for your own stack, or a recipe in the tool you use.
- Signed webhooks
Send signed HTTPS events to your own endpoint with Standard Webhooks headers and automatic retries.
- Zapier
Point an Embers webhook at a Zapier Catch Raw Hook and fan the event out to anything Zapier supports.
- Make
Feed a Make custom webhook module from Embers and route leads through a Make scenario.
- Clay
Push each qualified lead into a Clay table as a new row for further enrichment.
- n8n
A community recipe: an n8n Webhook node that verifies the signature and runs your own workflow.
AI assistants
Work the queue by chat.
- AI assistants (MCP)
Paste one MCP server address into an AI assistant, approve Embers once, and work the lead queue by chat.
Export
Take a selection with you.
- CSV export
Download the leads you have selected, with scores, signals, and contact fields, as a CSV file.
No integration matches "". Signed webhooks reach anything with an HTTPS endpoint. Set up a webhook
Connecting a destination is administrator only. Any member can export a CSV or push selected leads by hand with Send to.
One agent, one destination, no glue code.
Each agent's leads can go somewhere different. These are the routes teams set up first.
-
People reacting to your posts, in a Slack channel
Each engager who fits your ICP arrives with the score, why they match, and the evidence.
Post Engagement Set it up -
Keyword authors into their own HeyReach campaign
Each agent's leads go to the campaign you choose. HeyReach does the sending; Embers never does.
Keyword Tracker Set it up -
Engagers on the profiles you watch, as HubSpot contacts
Embers creates or updates the contact and attaches one note describing the signal.
Watchlist Set it up -
Replies to your comments, into any system
Signed events your own stack, or Zapier, Make, Clay, or n8n, receives and retries.
Comment Engagement Set it up
Set up delivery once, properly.
- Guide Route warm LinkedIn leads to HubSpot with signed webhooks Move Priority Queue leads into Slack, native HubSpot, and signed webhooks, all on Solo and above.
- Help center Delivery rules Narrow what each destination receives: a minimum score, ICP only, sources, and excluded titles or industries.
- Help center Verify webhook signatures Check the Standard Webhooks headers on every event before you trust it.
Before you
connect anything.
Plans, permissions, and what each destination actually does.
All setup guidesSlack, HubSpot, HeyReach, Instantly, Smartlead, Emelia, signed webhooks, and CSV export need a Solo, Growth, Enterprise, or Agency plan. An account administrator connects each destination; any member can export a CSV or push selected leads by hand with Send to.
No. Zapier, Make, Clay, and n8n receive a signed Embers webhook: point it at their catch hook or webhook module and every lead arrives as an event. Each setup guide walks through the steps.
Never. Embers does not send connection requests, messages, comments, or reactions on LinkedIn. It pushes ranked leads to HeyReach, Instantly, Smartlead, or Emelia, and those tools do the sending under your rules.
Yes, on a paid plan. Paste one MCP server address into an assistant that supports remote MCP with OAuth, approve Embers once, and ask for today's queue. It can read and update leads and draft openers. It cannot act on LinkedIn.
Signed webhooks reach anything with an HTTPS endpoint: lead, status, and report-ready events, signed, logged, retried seven times over six days, and replayable.
Tomorrow’s queue is
already forming.
Every day Embers reads the public activity around your market, ranks the people who fit, and hands you a short list with the reason each one surfaced. You decide who to contact.
Your first 2,000 engagers free · No card to start · No LinkedIn login · Cancel anytime