# Choose where Embers sends your leads URL: https://useembers.com/help/integrations/overview/ Category: Integrations Plan: Solo and above Updated: 2026-10-27 Last verified: 2026-10-27 > Compare every Embers destination and what it needs: Slack, HubSpot, Salesforce, Pipedrive, Attio, Notion, Google Sheets, outreach tools, webhooks, and CSV. 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](/help/troubleshooting/faq/#integrations-and-exports). > **Warning: Solo and above, administrators connect them** > > Every destination requires Solo or above, including during the [free trial](/help/account-and-billing/free-trial/). Only a workspace admin can connect or change Slack, HubSpot, Salesforce, Pipedrive, Attio, Notion, Google Sheets, HeyReach, Instantly, Smartlead, Emelia, and webhooks. [AI assistants](/help/integrations/mcp/) are the exception: any member connects their own. ## 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 7 connected"): Attio, Google Sheets, HubSpot, Notion, Pipedrive, Salesforce, 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 one status line, such as "Connected · #warm-leads in Acme", "Connected · 2 configurations", or "Not connected", whose dot turns amber when the tool needs you, as in "Paused after an error". 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**. The button, or anywhere else on the card, 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](/help/integrations/webhooks/) (`/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 →**, at the right of the **Build your own** heading, opens the payload reference under Settings, then API and webhooks. The top bar holds no buttons on this page. 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 | Destination | What it does | Where you connect it | | --- | --- | --- | | [Slack](/help/integrations/slack/) | Posts one card per lead into one channel | `/integrations/slack` | | [HubSpot](/help/integrations/hubspot/) | Creates or updates one contact, with one note | `/integrations/hubspot` | | [Salesforce](/help/integrations/salesforce/) | Creates a Lead, or updates the Lead or Contact you have, with a completed Task | `/integrations/salesforce` | | [Pipedrive](/help/integrations/pipedrive/) | Creates or updates one Person, with a Lead in the Leads Inbox and one note | `/integrations/pipedrive` | | [Attio](/help/integrations/attio/) | Creates or updates one person, optionally on a list, with one note | `/integrations/attio` | | [Notion](/help/integrations/notion/) | Adds or updates one page per lead in one database | `/integrations/notion` | | [Google Sheets](/help/integrations/google-sheets/) | Adds or updates one row per lead in one spreadsheet tab | `/integrations/google-sheets` | | [HeyReach](/help/integrations/heyreach/) | Pushes leads into a LinkedIn campaign or list | `/integrations/heyreach` | | [Instantly](/help/integrations/instantly/) | Pushes leads into an email campaign or list | `/integrations/instantly` | | [Smartlead](/help/integrations/smartlead/) | Pushes leads into an email campaign | `/integrations/smartlead` | | [Emelia](/help/integrations/emelia/) | Pushes leads into a sequence of LinkedIn and email steps | `/integrations/emelia` | | [Webhooks](/help/integrations/webhooks/) | Sends the full JSON event to your HTTPS endpoint | `/integrations/webhooks` | | [Zapier](/help/integrations/zapier/), [Make](/help/integrations/make/), [Clay](/help/integrations/clay/) | Recipes on the signed webhook | **Set up** on the tool's row in `/integrations` | | [n8n](/help/integrations/n8n/) | A community recipe on the signed webhook, not listed in the app | `/integrations/webhooks` | | [CSV export](/help/integrations/csv-export/) | Downloads the leads you selected | The Leads page (`/leads`) | ## 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. **Salesforce** is the same job for a Salesforce org. Embers creates a Lead, so your assignment rules route it, or updates the Lead or Contact the org already has for that person, and logs a completed Task on why the lead qualified. It never creates Contacts, Accounts, or Opportunities. Connect it with Salesforce's own login screen, ideally as a Salesforce admin. One org per account. **Pipedrive** is the same role for a Pipedrive pipeline. Embers creates or updates a Person, links it to an organization, and adds a Lead to your Leads Inbox for a person it creates, with one note on why they qualified. It never creates deals. You map Embers fields to your own Person custom fields, because a Pipedrive Person has no LinkedIn field and usually no job title, and Embers never creates fields. One company per account. **Attio** is the same role for an Attio workspace, with less setup: Attio people already have a LinkedIn attribute and a job title, so there is nothing to map. Embers creates or updates a person, links the company by name when no work email links one, can add the person to a list you pick, and leaves one note on why they qualified. It never creates deals. Connect it as an Attio workspace admin, or paste a workspace API key. One workspace 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. **Google Sheets** is the same idea for a spreadsheet. Embers can create one with its columns ready, or you map its fields to the columns of a sheet you already use, and each lead keeps one row that Embers updates. Embers can open only the spreadsheets it creates or that you choose, nothing else in your Google Drive. Connect it with your Google account; no key to paste. **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. A workspace can connect several accounts of one of these tools, each with its own key and configurations: one on Solo, up to 5 on Growth, and up to 10 on Enterprise and Agency. Slack, HubSpot, Salesforce, Pipedrive, Attio, Notion, and Google Sheets stay one connection per workspace. 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](/help/integrations/webhook-payload-reference/), with signature headers, retries, and a 30-day delivery log. Up to 10 endpoints per workspace. They are the route to a CRM other than HubSpot, Salesforce, Pipedrive, or Attio, 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](/help/integrations/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 ### 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. ### Add the system of record If your pipeline lives in HubSpot, Salesforce, Pipedrive, or Attio, connect it too. If your team works leads in Notion or a spreadsheet, send them to a database or a Google Sheets tab. Slack, HubSpot, Salesforce, Pipedrive, Attio, Notion, and Google Sheets run side by side from the same events. ### 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, and so can several accounts of one tool, such as [an Emelia account per seat](/help/integrations/emelia/#connect-more-than-one-emelia-account). Point one configuration at a list or a paused campaign and watch a few leads land before you point it at a running campaign. ### 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, Salesforce, Pipedrive, or Attio, or an automation tool in the middle. ### 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](/help/leads/how-scoring-works/) is above zero, it matched your ICP or you approved it by hand, and its company is not on your [blocklist](/help/leads/company-blocklist/). Blocklisted companies never leave Embers. Slack, HubSpot, Salesforce, Pipedrive, Attio, Notion, Google Sheets, and each HeyReach, Instantly, Smartlead, or Emelia configuration then apply their own [delivery rules](/help/integrations/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](/help/outreach/lead-enrichment-and-contact-info/) are not part of the free trial. Everything above is automatic. [Send to](/help/leads/send-to-destination/) is the manual half: pick leads on the Leads page or in the [Priority Queue](/help/leads/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 - [Send qualified leads to Slack](/help/integrations/slack/): One channel, two event toggles, and what the card shows. - [Push qualified leads into HeyReach](/help/integrations/heyreach/): Each agent into its own campaign, with the signal attached. - [Control which leads reach each destination](/help/integrations/delivery-rules/): Narrow what each destination receives. - [Send lead events to your own endpoint](/help/integrations/webhooks/): Every field, signed, with retries. ## Frequently asked questions **Do Zapier, Make, and Clay each need their own destination?** No. All three read the same signed HTTPS webhook. Each has a row on the Integrations page, and its Set up button adds the tool's receiving URL as a webhook endpoint for you. **Which leads actually get sent?** A lead is sent when its score is above zero, it matched your ICP or you approved it by hand, and its company is not on your blocklist. Each native destination can narrow that further with delivery rules. **Can I connect several destinations at once?** Yes. Every destination runs side by side, and a qualifying lead can reach all of them. That includes both email tools, Instantly and Smartlead, on one workspace, and on Growth and above several accounts of one outreach tool, such as an Emelia account per seat.