Skip to content

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 Native · Solo and above

    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 Native · Solo and above

    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 Native · Solo and above

    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 Native · Solo and above

    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 Native · Solo and above

    Post qualified leads into one Slack channel with the score, why they match, the evidence, and a suggested opening line.

  • HubSpot Native · Solo and above

    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 Native · Solo and above

    Send signed HTTPS events to your own endpoint with Standard Webhooks headers and automatic retries.

  • Zapier Webhook recipe · Solo and above

    Point an Embers webhook at a Zapier Catch Raw Hook and fan the event out to anything Zapier supports.

  • Make Webhook recipe · Solo and above

    Feed a Make custom webhook module from Embers and route leads through a Make scenario.

  • Clay Webhook recipe · Solo and above

    Push each qualified lead into a Clay table as a new row for further enrichment.

  • n8n Webhook recipe · Solo and above

    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) MCP · Paid plans, any member

    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 Export · Solo and above

    Download the leads you have selected, with scores, signals, and contact fields, as a CSV file.

Connecting a destination is administrator only. Any member can export a CSV or push selected leads by hand with Send to.

Workflows

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
Questions

Before you
connect anything.

Plans, permissions, and what each destination actually does.

All setup guides

Slack, 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.

Your next pass

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