# Where Embers can send your leads URL: https://useembers.com/help/integrations/overview/ Category: Integrations Plan: Solo and above Updated: 2026-09-12 Last verified: 2026-09-12 > Compare every Embers destination: Slack, HubSpot, signed webhooks, Zapier, Make, Clay, n8n, and CSV export, with the plan and role each one needs. Embers can hand a qualified lead to a person, to a CRM, to your own code, or to a spreadsheet. This page compares every destination so you can pick one and stop there. > **Warning: Solo and above, administrators only** > > Every destination screen, including CSV export, requires Solo or above, and only an account administrator can reach it. Free can see the lead list and the dashboard, and nothing more. ## The destinations | Destination | How it is built | Where you set it up | | --- | --- | --- | | [Slack](/help/integrations/slack/) | Native. Embers talks to Slack directly | Settings, then Integrations (`/settings/integrations`) | | [HubSpot](/help/integrations/hubspot/) | Native. Private-app token, or OAuth when it is configured | Settings, then Integrations | | [Signed webhooks](/help/integrations/webhooks/) | Native. Signed HTTPS POSTs to your URL | Developer, then Webhooks (`/developer/webhooks`) | | [Zapier](/help/integrations/zapier/) | A recipe on the signed webhook | Developer, then Webhooks | | [Make](/help/integrations/make/) | A recipe on the signed webhook | Developer, then Webhooks | | [Clay](/help/integrations/clay/) | A recipe on the signed webhook | Developer, then Webhooks | | [n8n](/help/integrations/n8n/) | A community recipe on the signed webhook. It is not listed in the app | Developer, then Webhooks | | [CSV export](/help/integrations/csv-export/) | A file you download | The leads list and priority queue | Every row is Solo and above. ## What each one can and cannot do **Slack** posts one card per event into a single channel, with the score, the ICP verdict, the evidence, and a suggested opening line. One Slack workspace, one channel. It cannot route different events to different channels, and it never reads your Slack messages. **HubSpot** creates or updates one contact per lead and attaches one note on first create. It does not create companies and it does not create deals. One HubSpot portal per Embers account. **Signed webhooks** send the full JSON event to your own HTTPS endpoint, with Standard Webhooks signature headers, automatic retries, and a 30-day delivery log. Up to 10 endpoints per account. This is the only destination that gives you every field. **Zapier, Make, and Clay** are not separate connections. You create a Catch Hook, a Custom webhook, or an HTTP API source in that tool, paste the URL into Developer, then Webhooks, and verify the signature there. Everything the webhook carries is available to them. **n8n** works the same way, with an n8n Webhook node. It is a community recipe, so it does not appear in the app's destination list. **CSV export** is a point-in-time download of the leads you selected, including contact columns. It is not a live feed and it does not push anything anywhere. ## How to choose ### Start with the person who acts on the lead If a human decides what to do next, send it to Slack. It is the shortest path from signal to a reply on LinkedIn. ### Add the system of record If your pipeline lives in HubSpot, connect HubSpot as well. Slack and HubSpot can run side by side, and both draw from the same events. ### Reach for a webhook when you need everything Choose the signed webhook when you want fields the other destinations do not carry, when your CRM is not HubSpot, or when an automation tool sits in the middle. Names in the payload are limited: first and last name are not in it. ### Use CSV only for one-off work A list for a campaign, a hand-off to an agency, or an audit. Anything recurring belongs on a live destination. ## Which leads get delivered The same rule applies to every destination. Embers sends a lead when its score is above zero, it matched your ICP or you approved it manually, and its company is not on your blocklist. Tests are the exception: they use the `webhook.test` event type, so a test can never create a CRM record. ## Related - [Send qualified leads to Slack](/help/integrations/slack/): One channel, four event toggles, and what the card shows. - [Connect HubSpot](/help/integrations/hubspot/): One contact and one note per lead, with a private-app token. - [Signed webhooks](/help/integrations/webhooks/): Your own endpoint, signed, retried, and logged. - [Export leads to CSV](/help/integrations/csv-export/): A one-off download of the leads you selected. ## Frequently asked questions **Do Zapier, Make, and Clay each need their own destination?** No. All three consume the same signed HTTPS webhook. In Settings, then Integrations they appear as recipes on the HTTPS destination rather than as separate connections. **Which leads actually get sent?** A lead is sent when it has a score above zero, it matched your ICP or you approved it manually, and its company is not on your blocklist.