# Push qualified leads into HeyReach

URL: https://useembers.com/help/integrations/heyreach/
Category: Integrations
Plan: Solo and above
Updated: 2026-10-31
Last verified: 2026-10-31

> Connect HeyReach with an API key, then add configurations that send each agent's leads into its own campaign or list, with the signal attached.

HeyReach runs LinkedIn sequences; Embers decides who is worth one. Connect the two and a lead Embers qualified lands in a HeyReach campaign as soon as it surfaces, carrying the signal that put it there.

> **Warning: Solo and above, administrators only**
>
> Integrations require Solo or above, and only a workspace admin can connect HeyReach or change its configurations. Solo connects one HeyReach workspace per Embers workspace; Growth connects up to 5, and Enterprise and Agency up to 10.

Embers never sends connection requests, messages, comments, or reactions on LinkedIn. HeyReach does the sending; Embers pushes the lead.

## Before you start

- A HeyReach workspace you administer. An agency on a HeyReach organization has one key per workspace, so pick the workspace whose campaigns you want to feed. To feed more than one, [connect each workspace](#connect-more-than-one-heyreach-workspace).
- A target for the leads: a HeyReach campaign that is **running**, has at least one sender assigned, and was created with HeyReach's **Create empty list** option, or a lead list.
- At least one [agent](/help/getting-started/choose-your-agents/) producing leads, if you want to route agents to different campaigns.

## Connect HeyReach

### Copy your HeyReach API key

In HeyReach, open **Settings**, then **Integrations**, then **HeyReach API**, and choose **Get API Key**. HeyReach offers no sign-in for other apps, so a key is the only way in. Keys do not expire, but they can be deleted in HeyReach at any time.

### Save it in Embers

Open **Integrations** in the sidebar (`/integrations`) and choose **HeyReach** (`/integrations/heyreach`). On the **Setup** card, paste the key under **API key** and choose **Save API key**. **Open HeyReach API settings** under the field goes straight to the page where the key lives.

Embers checks the key against HeyReach before storing it, so a wrong key fails here rather than at the first lead. The page then opens on one sentence that says whether leads are going out, such as "Not sending yet: add a configuration" or "Delivering to HeyReach", with a line of facts under it, such as "37 leads sent · last sent 3 Oct, 9:31 · 1 configuration on · 3 senders". Below it come the **Configurations**, **Activity**, **Field mapping**, and **Connection** cards.

### Add a configuration

On the **Configurations** card, choose **Add configuration**. A configuration is one route, and you can add as many as you have campaigns to feed:

- **Agents**: **All agents**, or **Choose agents** to tick the agents it listens to, such as **Your profile**, one watched profile, or **Keywords**.
- **Send leads to**: **Campaign** or **List**. Only a running campaign can be picked; a draft or paused one shows **Start it in HeyReach to use it here**. For a campaign, choose the LinkedIn account under **Send from**. It only lists senders assigned to that campaign in HeyReach.
- **Who gets delivered**: starts at a minimum score of 70 with ICP matches only on.
- **Also send leads you already have**: sends the matching leads Embers already found, once.

The name fills itself from the target until you type one. Choose **Add configuration** and it starts sending new leads as they qualify; to push particular leads now, use [Send to](/help/leads/send-to-destination/). [How configurations route leads](/help/integrations/delivery-rules/#how-configurations-route-leads) covers the agent matching, overlapping configurations, and the one-time send in detail.

### Check it

Open the configuration's **...** menu, or use the test button beside the status at the top of the page (with two or more configurations it reads **Test a configuration** and asks which one). For a campaign, **Check readiness** checks the key, the campaign status, and the sender, and never pushes a lead: a campaign push starts a real sequence against a real person. For a list, **Send test lead** pushes one person named "Embers Test" after you confirm; it shows on the **Activity** card badged "Test lead". Remove them from the list afterwards.

## Connect more than one HeyReach workspace

Each HeyReach workspace has its own API key and campaigns. To feed several of them from one Embers workspace, connect each one. On the HeyReach page, open the **...** menu at the top and choose **Connect another HeyReach account**, give the connection a name such as "Client A", and paste that workspace's API key. Then add its configurations as in the steps above. Once there are two, the page opens on **All accounts**, with a tab for each account after it. Each tab shows the account's state as a dot (green while it sends, amber when it is paused, grey when no configuration is on) and, when it has any, its number of failed leads. **All accounts** says how many accounts are sending, lists what needs a hand on any of them with the account's name beside it, and shows every configuration and one activity log, whose **Sent from** column names the account. Choose an account's tab to change its configurations, rename it from the **...** menu, or replace its key. The page's address keeps the tab, so a link or a reload opens the same account. **Connect another HeyReach account** sits beside the tabs.

- **Its own setup.** A connection has its own key, field mapping, and configurations: which agents feed it, which campaign and sender or list, its delivery rules, and its switch.
- **A name.** Left blank, a connection is named "HeyReach", then "HeyReach 2", "HeyReach 3". Names are unique per tool in a workspace, and you can rename one with **Rename this account** in the **...** menu. Embers shows a connection with its tool, such as "HeyReach: Client A".
- **Every match is sent, by default.** Automatic delivery sends a lead to every configuration it matches, across all connections, so two HeyReach workspaces whose configurations both match a lead each get it. To keep each prospect with one workspace, turn on [One sender per prospect](/help/integrations/delivery-rules/#one-sender-per-prospect): the first connection a prospect is sent to keeps them, and every other outreach connection holds them back with a reason such as `already with HeyReach: Client A`. Splitting the configurations by agents or by delivery rules also works.
- **Send to asks.** Send to lists the configurations of each connection under its name, such as **HeyReach: Client A**, so two configurations with the same name on two accounts never look alike. A push that does not name a configuration, and could go to more than one connection, asks which to use. Embers never picks one for you.
- **One workspace, once.** HeyReach does not say which workspace a key belongs to, so Embers refuses a key that is already connected, with "This HeyReach account is already connected as HeyReach: Client A." Two different keys from the same HeyReach workspace cannot be told apart. Do not connect one workspace twice: every lead would go in twice.
- **Separate pauses.** Disconnecting one connection, or a rejected key that pauses one, leaves the others sending.
- **Reconnecting brings it back.** Connecting the same API key again later restores that connection's configurations and history. To swap a seat's key without disconnecting, use **Replace API key**, which keeps everything.

Past your [plan's limit](/help/account-and-billing/plans-and-limits/), adding another asks you to upgrade: "Your plan allows 1 HeyReach connection per workspace. Upgrade to connect more." A downgrade keeps the connections you already have and only stops you adding more.

## What HeyReach receives

Each push creates or updates one HeyReach lead with the person's name, LinkedIn profile, company, position, location, headline, and about section, tagged `embers`. It also carries five custom fields you can use as variables in a HeyReach sequence, with nothing to create in HeyReach first:

| Custom field | What it holds |
| --- | --- |
| `embers_signal` | The engagement that surfaced them |
| `embers_icp_reason` | Why Embers judged them a fit |
| `embers_score` | The score at the time of the push |
| `embers_source` | The agent the lead came from |
| `embers_lead_url` | A link back to the lead in Embers |

Open with `embers_signal`. A first line that names what someone actually posted or commented on is the reason to connect the two tools.

HeyReach finds a person by their public profile URL. A lead Embers first saw through a reaction is often known only by LinkedIn's id link (`linkedin.com/in/ACoAA…`). That link opens in your browser, so the lead page shows a working LinkedIn link, but HeyReach cannot open it. Embers looks the profile up once to get the public URL, and the lead waits as pending meanwhile. A lead that still has no public URL is skipped with `profile URL is not a public LinkedIn slug` (or `LinkedIn returned no public profile URL for this lead`), even with **ignore rules**. Email is sent only when Embers already holds one, which needs a paid plan: [contact details](/help/outreach/lead-enrichment-and-contact-info/) are not part of the [free trial](/help/account-and-billing/free-trial/).

**Change which Embers value fills each field**

The **Field mapping** card sums up what each lead carries; choose **Edit fields**. The mapping belongs to the connection, so every configuration of that connection sends the same fields.

- Any unlocked field can take any Embers value (name, company, job title, headline, location, industry, country, company size, company industry, company LinkedIn URL, company website, company domain, signal, ICP reason, score, and more), or **Not sent**.
- First name, last name, and the LinkedIn profile URL are locked: HeyReach needs the URL to find the lead, and every LinkedIn step greets the lead by name.
- Add a custom field with a name and a value. Names use letters, digits, and underscores, start with a letter, and you can have up to 25.
- **Reset** returns every field to the defaults. Choose **Save fields** to keep your changes.

**Campaign statuses**

HeyReach reports eight campaign statuses. Only **Running** accepts pushed leads; Draft, Starting, Scheduled, Paused, Finished, Canceled, and Failed do not. If none of your campaigns is running, the picker offers **Open HeyReach**, **Refresh**, and **Send to a list instead**.

Embers never starts, pauses, or resumes a campaign. The only thing it creates in HeyReach is an empty lead list, from **Or create a new list**. A list target warns that leads added to a list do not start in a campaign that has finished or already used its list.

**Repeat pushes**

Embers sends a lead to each campaign or list once, whichever configuration sends it. Another push to the same target is skipped as `already pushed to` that target, unless you push with **ignore rules**. A different campaign counts as a new push, so the same person can enter a second sequence deliberately. HeyReach treats a repeat as an update to the lead it already holds.

**Rate limits and the key**

HeyReach allows 300 API requests a minute per key. Embers uses at most 240, so your own automations on the same key keep headroom. Rate limits and HeyReach outages are retried on the standard schedule.

The key is stored encrypted and is never shown again or returned by the Embers API. To swap it, choose **Replace API key** on the **Connection** card, paste the new key, and choose **Save new key**: every configuration and the delivery history stay. **Disconnect HeyReach** (with several connections, **Disconnect** followed by the connection's name), in the **...** menu at the top of the page, wipes the key, and every configuration of that connection goes with it; anything already in HeyReach stays there, and your other HeyReach connections are untouched. Deleting the key in HeyReach stops delivery immediately.

## Troubleshooting

A problem with one campaign pauses only the configuration that sends to it, and its row shows **Paused**. A problem with the key pauses the whole connection. Either way a **Needs attention** card appears under the status at the top of the page with the reason, and each item carries the button that fixes it. [HeyReach delivery is paused](/help/troubleshooting/heyreach-delivery-paused/) covers each reason in more depth.

**Nothing is sent and Needs attention says a configuration "is off."** Every configuration is switched off, so no lead goes to HeyReach. Choose **Turn on** beside it. With several configurations it reads "Every configuration is off"; choose **Choose one** and switch one on in the **Configurations** card.

**Needs attention shows "Campaign is not running."** The campaign was paused or finished in HeyReach. Start it there, then choose **Resume** beside it.

**Needs attention shows "The campaign has no sender assigned."** The LinkedIn account was removed from the campaign in HeyReach. Assign one there, then resume.

**Needs attention shows "Campaign or list no longer exists in HeyReach."** It was deleted. Choose **Edit** on the configuration, pick another target, and save.

**Needs attention shows "HeyReach API key was rejected."** The key was deleted or deactivated. Get a new key in HeyReach, choose **Replace API key** on the **Connection** card, paste it, and choose **Save new key**. Your configurations stay, and delivery resumes.

**Needs attention shows "HeyReach delivery retries were exhausted."** HeyReach kept failing for about 6.3 days. Check HeyReach is working, then choose **Resume** beside it.

**One lead is marked failed and nothing paused.** HeyReach refused that lead alone, for example a malformed profile URL. Its row on the **Activity** card shows HeyReach's message, and the newest failures also appear in **Needs attention** with **Retry**. Everything else keeps flowing.

**Leads are held back rather than sent.** A [delivery rule](/help/integrations/delivery-rules/) held them back, or the lead has no public profile URL. Choose **Held back** on the **Activity** card to see the reason on each row; **Send anyway** overrides a rule, not a missing URL.

## Related

- [Fix HeyReach delivery when it is paused](/help/troubleshooting/heyreach-delivery-paused/): Every pause reason and how to clear it.

- [Send a lead to a destination](/help/leads/send-to-destination/): Push the leads you pick into a campaign by hand.

- [Push leads into Emelia](/help/integrations/emelia/): One sequence that mixes LinkedIn and email steps.

## Frequently asked questions

**Does Embers send the LinkedIn messages?**

No. Embers never sends connection requests, messages, comments, or reactions on LinkedIn. HeyReach does, from the LinkedIn accounts connected there. Embers pushes leads.

**Why can I not pick my draft campaign?**

HeyReach only accepts leads into a running campaign, so a draft or paused one is greyed out with "Start it in HeyReach to use it here." Start it in HeyReach, then choose Refresh.

**I have no running campaign yet. What now?**

Choose Send to a list instead. Embers fills in the name Embers leads; choose Create list. Later, build a HeyReach campaign on that list, start it, and edit the configuration to send to the campaign.

**Can I connect more than one HeyReach workspace?**

Yes, on Growth and above. Connect each HeyReach workspace with its own API key, field mapping, and configurations. Growth connects up to 5 per Embers workspace, Enterprise and Agency up to 10, and Solo one.

**Do accepts and replies come back into Embers?**

Not yet. Embers pushes leads into HeyReach and does not read results back today.
