Choose where Embers sends your leads

Embers can hand a qualified lead to a person, a CRM, an outreach tool, your own code, or a spreadsheet. This page compares every destination so you can pick the one that fits the next step. For quick answers, such as a destination that says Paused or leads that were skipped, see the integrations FAQ.

Find the Integrations page

Open Integrations in the sidebar (/integrations). The tools sit on three shelves, grouped by the job they do, and each shelf counts what is in use:

• Send leads to your workspace (“1 of 3 connected”): HubSpot, Notion, and Slack.
• Start outreach (“1 of 4 connected”): HeyReach, Instantly, Smartlead, and Emelia.
• Build your own (“2 of 5 set up”): one card of rows for Webhooks, Zapier, Make, Clay, and MCP.

On the first two shelves each tool has a card with a status line, such as “#warm-leads in Acme”, “2 configurations”, or “Not connected”, that turns amber when the tool needs you, as in “Paused after an error”. A working connection also shows a Connected chip. Every card has a How to connect link to its guide and one button named for the next step, such as Connect, Finish setup, Fix, Turn on, or Configure, which opens the tool’s own page, for example /integrations/slack, where you connect it and set its rules.

On Build your own, the Webhooks row opens the Webhooks page (/integrations/webhooks) and the MCP row opens the MCP page (/integrations/mcp). Zapier, Make, and Clay have no page of their own: a row reads “Not set up” with Set up, which opens a side sheet with three steps and adds the endpoint for you. Once an endpoint’s URL is on the tool’s domain, the row names it, as in “Sending to Zapier”, with Manage, which opens the Webhooks page. Webhook payload in the top bar opens the payload reference under Settings, then Developer.

Below Solo, every card and row reads “Solo and above”. A member who is not an administrator sees “Administrators only” on every tool except MCP.

The destinations

What each one is for

Slack is for a person who reads the lead and decides. The card carries the score, the ICP verdict, the evidence, and a suggested opening line. One workspace, one channel.

HubSpot is the system of record. Embers creates or updates the contact; it never creates companies or deals. One portal per account.

Notion is a working surface you shape yourself. Embers adds one page per lead to a database you choose and keeps it current, so you can filter, sort, and assign in Notion. You map Embers fields to your own columns, and Embers never changes the database’s properties. Connect it with Notion’s own consent screen; no key to paste. One database at a time.

HeyReach, Instantly, Smartlead, and Emelia run the sequence. Each connection holds configurations, so every agent can feed its own campaign, and the signal arrives as a variable for your opening line. Embers never sends anything on LinkedIn and never emails a lead; the tool does. They differ in what a lead needs:

• HeyReach needs a public LinkedIn profile URL. A campaign needs a sender.
• Instantly and Smartlead need an email. On a paid plan Embers looks a missing one up first; a lead with none found is skipped.
• Emelia needs a public profile URL or an email, and never triggers a lookup.

Signed webhooks carry every field of the lead and its engagement, with signature headers, retries, and a 30-day delivery log. Up to 10 endpoints per account. They are the route to a CRM other than HubSpot, or to Zapier, Make, Clay, or n8n, which consume the same webhook rather than a separate connection.

CSV export is a point-in-time file. It is not a live feed and pushes nothing anywhere.

AI assistants work the other way round. Connecting one over MCP lets it read your queue and act on it while you talk to it, so it is a way to use Embers rather than a place leads are sent.

Choose a combination

1. Start with the person who acts on the lead

   If a human decides what happens next, send leads to Slack. It is the shortest path from a signal to a reply.

2. Add the system of record

   If your pipeline lives in HubSpot, connect it too. If your team works leads in Notion, send them to a database there. Slack, HubSpot, and Notion run side by side from the same events.

3. Add the tool that sends

   If a sequence is the next step, connect HeyReach for LinkedIn, Instantly or Smartlead for email, or Emelia for both. Instantly and Smartlead can both be connected on one workspace. Point one configuration at a list or a paused campaign and watch a few leads land before you point it at a running campaign.

4. Reach for a webhook when you need everything

   Choose a signed webhook when you want fields the others do not carry, a CRM other than HubSpot, or an automation tool in the middle.

5. Use CSV for one-off work

   A campaign list, a hand-off, or an audit. Anything recurring belongs on a live destination.

Which leads get delivered

A lead qualifies when its score is above zero, it matched your ICP or you approved it by hand, and its company is not on your blocklist. Blocklisted companies never leave Embers.

Slack, HubSpot, Notion, and each HeyReach, Instantly, Smartlead, or Emelia configuration then apply their own delivery rules: a minimum score, ICP only, sources, and excluded titles and industries. Signed webhooks are deliberately unfiltered.

Email and phone travel only when Embers already holds them, on a paid plan. Contact details are not part of the free trial.

Everything above is automatic. Send to is the manual half: pick leads on the Leads page or in the Priority Queue and push up to 100 at once to a connected destination. Any member of a paid workspace can use it once an administrator has connected the destination.

Related