# 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-01
Last verified: 2026-10-01

> 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 **Full details** 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, 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. 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 log as skipped with the reason. A lead whose company is [blocked](/help/leads/company-blocklist/) never goes.

To send a skipped lead anyway, an administrator retries its row in the destination's delivery log. 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 |
| 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 |

## Where the result shows up

Slack, HeyReach, Instantly, Smartlead, and Emelia each keep a delivery log for 30 days on their page under **Integrations** in the sidebar (`/integrations/slack`, `/heyreach`, `/instantly`, `/smartlead`, or `/emelia`). It records every attempt, manual or automatic, as delivered, skipped, or failed, with the reason, and for the outreach tools the configuration that sent it. A failed row can be retried there. HubSpot's page (`/integrations/hubspot`) shows only the state of the last delivery.

A lead pushed to HeyReach, Instantly, Smartlead, or Emelia also gets a **Sent to** pill in the header of its full lead page. Slack and HubSpot pushes leave no mark on the lead, so check the Slack log or HubSpot's last delivery state.

## Related

- [Control which leads reach each destination](/help/integrations/delivery-rules/): The rules a push runs through, and what skipped 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 skipped?**

Yes. An administrator can retry the skipped row from the destination's delivery log. Retrying a skipped row sends that lead anyway, whatever the rules say.

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

Embers never sends anything itself. Slack, HubSpot, 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.

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

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