# Send a lead to a destination

URL: https://useembers.com/help/leads/send-to-destination/
Category: Leads and scoring
Plan: Solo and above
Updated: 2026-10-31
Last verified: 2026-10-31

> Send to pushes the leads you pick to a connected destination from the leads list, the Priority Queue, or a lead's full page, without waiting for a scan.

Automatic delivery handles the steady stream. **Send to** is for the rest: the lead you found while browsing, the ten people from one post you want in the CRM now, or the person a rule held back yesterday.

> **Warning: Solo and above**
>
> Send to needs Solo or above and a destination an administrator has already connected. Any member can then send. Connecting a destination, editing its rules, and retrying from its delivery log are administrator only.

## Send leads

### Pick the leads

- **The leads list** (`/leads`): tick rows, then choose **Send to** in the bulk bar.
- **The Priority Queue** (`/priority-queue`): open **More** on a card, then **Send to**.
- **A lead's full page**: choose **Send to** in the header.
- **An AI assistant**: [connect one with MCP](/help/integrations/mcp/) and ask it to push leads, up to 100 per call. It asks before each push.

The lead sheet that opens over the list has no Send to; choose **Open full page** to reach the [full lead page](/help/leads/lead-detail/).

### Choose the destination

The menu lists every connected destination that takes a manual push: Slack, HubSpot, [Salesforce](/help/integrations/salesforce/), [Pipedrive](/help/integrations/pipedrive/), [Attio](/help/integrations/attio/), Notion, Google Sheets, HeyReach, Instantly, Smartlead, and Emelia. When HeyReach, Instantly, Smartlead, or Emelia has more than one [configuration](/help/integrations/delivery-rules/#how-configurations-route-leads), the tool opens a submenu of them by name, each with its campaign or list. When [Instantly](/help/integrations/instantly/) and [Smartlead](/help/integrations/smartlead/) are both connected, their configurations are grouped under each tool's name and you pick the one to push into; Embers never guesses between them. The same goes for several accounts of one tool, such as two Emelia seats: the submenu lists each connection's configurations under its name, such as **Emelia: Sean**, and the confirmation reads "Emelia: Q4 list (Sean)". A connected tool with no campaign configured shows a **Set up a campaign** row. When all its configurations are paused, or its connection is, the row carries a hint to resume, linking to that tool's settings page. Send to never pushes from that row. A paused configuration is not offered. One that is switched off still is, because its switch only stops automatic sending.

### Read the result

The leads go as soon as you choose; there is no confirmation step. A toast reports how many were sent, and how many were skipped or blocked with the first reason. When anything was held back, its **Delivery rules** button opens that destination's settings.

## How many, how often

Each request carries up to 100 leads. A larger selection is split into batches of 100 for you, so selecting 350 leads makes four requests. Each person gets **60 requests an hour**, counted per user rather than per workspace, so two colleagues clearing a backlog do not share a budget. If the limit stops a large selection part-way, the batches that already went stay sent and the rest are reported as blocked.

## Rules still apply

A manual push runs through the destination's [delivery rules](/help/integrations/delivery-rules/) exactly as automatic delivery does: the same score, ICP, and exclusion checks. For HeyReach, Instantly, Smartlead, and Emelia those are the chosen configuration's rules. Leads that fail are written to the destination's **Activity** card as **Held back**, with the reason. A lead whose company is [blocked](/help/leads/company-blocklist/) never goes.

To send a held-back lead anyway, an administrator chooses **Send anyway** on its row. If you find yourself doing that every time, the rule is set wrong.

Think twice with HeyReach, Instantly, Smartlead, and Emelia: a push into a running campaign starts a real LinkedIn or email sequence against a real person.

## What each destination does with a repeat

| Destination | Sending the same lead again |
| --- | --- |
| Slack | Posts another card. Slack has no record to update |
| HubSpot | Updates the contact Embers already linked to that person rather than creating a second one |
| Salesforce | Skips a lead already linked to a Lead or Contact in the connected org as `already synced to Salesforce Lead` (or `Contact`) and its record ID. Tick **ignore rules** to send it again, which updates that record rather than creating another |
| Pipedrive | Skips a lead already linked to a Person in the connected company as `already synced to Pipedrive person` and its ID. Tick **ignore rules** to send it again, which updates that Person's mapped fields rather than creating another, and adds no second Lead or note |
| Attio | Skips a lead already linked to a person in the connected workspace as `already synced to Attio person` and its record ID. Tick **ignore rules** to send it again, which updates that person rather than creating another, and adds no second note |
| Notion | Skips a lead already on a page of the current database as `already synced to Notion`. Tick **ignore rules** to send it again, which updates that page rather than adding another |
| Google Sheets | Skips a lead already in the current tab as `already synced to Google Sheets`. Tick **ignore rules** to send it again, which updates that row rather than adding another |
| HeyReach | Skips the lead as already pushed to that campaign. A different campaign is a new push |
| Instantly | Skips the lead as already pushed, and Instantly also skips anyone already in the campaign |
| Smartlead | Skips the lead as already pushed. Someone Smartlead already holds in that campaign counts as delivered; Smartlead refuses anyone in another campaign or on its global block, unsubscribe, or community bounce list |
| Emelia | Skips the lead as already pushed, and Emelia updates a person already in the list |

When a workspace admin has turned on [One sender per prospect](/help/integrations/delivery-rules/#one-sender-per-prospect), a push to HeyReach, Instantly, Smartlead, or Emelia also holds back a lead another outreach connection already has, such as `already with Emelia: Sean`. To send it there anyway, an administrator chooses **Send anyway** on its held-back row. It goes out once, and the lead stays with the first connection.

## Where the result shows up

Every destination that takes a push keeps a delivery log for 30 days on the **Activity** card of its page under **Integrations** in the sidebar (`/integrations/slack`, `/hubspot`, `/salesforce`, `/pipedrive`, `/attio`, `/notion`, `/google-sheets`, `/heyreach`, `/instantly`, `/smartlead`, or `/emelia`). It records every attempt, manual or automatic, as **Delivered**, **Held back**, **Failed**, or **Blocked** (and **Queued** or **Retrying** while it is still going out), with the reason, and badges a manual push "Sent by hand". A failed or blocked row can be retried there, and a held-back one sent anyway. A row blocked because your plan could not deliver it (a trial that ended while a scan was finishing) goes out on its own once the plan can again, within about five minutes, if the destination is connected and on and the person is still a lead; HeyReach, Instantly, Smartlead, and Emelia also skip anyone who reached that campaign or list in the meantime. Slack is the exception: a lead card blocked that way is not posted later. On [Notion](/help/integrations/notion/), HubSpot, and Salesforce a delivered row links to the page, contact, or record it wrote; on the four outreach tools a **Sent to** column names the configuration when the tool has two or more.

A lead pushed to HeyReach, Instantly, Smartlead, Emelia, Notion, Google Sheets, Salesforce, Pipedrive, or Attio also gets a pill under **Sent to**, in the side column of its [full lead page](/help/leads/lead-detail/). **Sent to Notion** opens the page in Notion, **Sent to Google Sheets** opens the lead's row, **Sent to Pipedrive** and **Sent to Attio** open the person, and Salesforce's pill, **Salesforce Lead** or **Salesforce Contact**, opens that record. Slack and HubSpot pushes leave no mark on the lead, so check the **Activity** card on the Slack or HubSpot page.

## Related

- [Control which leads reach each destination](/help/integrations/delivery-rules/): The rules a push runs through, and what held back means.

- [Push leads into HeyReach](/help/integrations/heyreach/): Configurations, campaigns, and senders.

- [Send leads to Slack](/help/integrations/slack/): What a card in the channel holds.

- [Create HubSpot contacts](/help/integrations/hubspot/): How Embers matches and updates contacts.

## Frequently asked questions

**Can I send a lead that a rule held back?**

Yes. An administrator can choose Send anyway on its Held back row in the Activity card on the destination's page. That sends the lead anyway, whatever the rules say.

**Does sending a lead do anything on LinkedIn?**

Embers never sends anything itself. Slack, HubSpot, Salesforce, Pipedrive, Attio, Notion, Google Sheets, and signed webhooks only receive the lead record. A push into a HeyReach campaign can start a LinkedIn sequence, an Instantly or Smartlead campaign an email sequence, and an Emelia campaign either, but the tool does the sending.

**I use Instantly and Smartlead. Which one does Send to use?**

The configuration you pick. Both tools list their configurations under their own names, and every push goes to the one you chose, never to a guess.

**We connected two Emelia accounts. Which one does Send to use?**

The configuration you pick. Configurations are listed under their connection, such as **Emelia: Sean**, and Embers never picks a connection for you.

**Why does Send to only offer Connect a destination?**

Nothing that accepts a manual push is connected yet. A workspace admin connects one from Integrations in the sidebar. Webhook endpoints only receive automatic events, so they never appear in Send to.
