# Push qualified leads into Emelia

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

> Connect Emelia with an API key, then add configurations that send each agent's leads into a campaign that mixes LinkedIn and email steps.

Emelia runs sequences that mix LinkedIn and email steps: a profile visit, a connection request, a message, then an email if the person has not replied. Embers decides who is worth one. Connect the two and a lead Embers qualified lands in an Emelia 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 Emelia or change its configurations. Solo connects one Emelia account per workspace; Growth connects up to 5, and Enterprise and Agency up to 10.

Embers never sends anything on LinkedIn and never emails a lead. Emelia does the sending; Embers pushes the lead.

## Before you start

- An Emelia workspace you administer.
- A target for the leads: a campaign with a contact list attached, or a contact list.
- At least one [agent](/help/getting-started/choose-your-agents/) producing leads, if you want to route agents to different campaigns.

## Connect Emelia

### Copy your Emelia API key

In Emelia, open **Settings**, then **Integrations**, then **API**, and copy the key. Emelia has no sign-in for other apps, so a key is the only way in. Embers uses it to read your campaigns and lists and to add contacts to lists; it never starts, pauses, or edits a campaign.

### Save it in Embers

Open **Integrations** in the sidebar (`/integrations`) and choose **Emelia** (`/integrations/emelia`). On the **Setup** card, paste the key under **API key** and choose **Save API key**.

Embers checks the key against Emelia before storing it. 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 Emelia", with a line of facts under it: leads sent, the last send, and how many configurations are on. Below it come the **Configurations**, **Activity**, **Field mapping**, and **Connection** cards. Emelia shares no workspace name or sender count, so the facts line shows neither.

### Add a configuration

On the **Configurations** card, choose **Add configuration**. A configuration is one route, and you can add one per campaign:

- **Agents**: **All agents**, or **Choose agents** to tick the agents it listens to.
- **Send leads to**: **Campaign** or **List**. Archived campaigns are left out. There is no sender to choose, because an Emelia campaign already owns its LinkedIn accounts and mailboxes.
- **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.

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 agent matching and overlapping configurations.

### 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 and the campaign, and never pushes a lead. 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 Emelia account

Every Emelia seat is its own Emelia account, with its own login, API key, and campaigns, and no seat sees another's. To feed several seats from one Embers workspace, connect each one.

On the Emelia page, open the **...** menu at the top and choose **Connect another Emelia account**, give the connection a name such as "Assistant 1", and paste that account'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 Emelia account** sits beside the tabs. Each connection stands on its own:

- **Its own setup.** A connection has its own key, field mapping, and configurations: which agents feed it, which campaign or list, its delivery rules, and its switch.
- **A name.** Left blank, a connection is named "Emelia", then "Emelia 2", "Emelia 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 "Emelia: Sean".
- **Every match is sent, by default.** Automatic delivery sends a lead to every configuration it matches, across all connections. If configurations on two seats both match a lead, both seats get it, because each Emelia account is a separate place. To keep each prospect with one seat, 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 Emelia: Sean`. 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 **Emelia: Sean**, 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 account, once.** Connecting an Emelia account that is already connected is refused with "This Emelia account is already connected as Emelia: Sean." Emelia does not say which account a key belongs to, so Embers compares keys, and two different keys from the same Emelia account cannot be told apart. Do not connect one account 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 Emelia connection per workspace. Upgrade to connect more." A downgrade keeps the connections you already have and only stops you adding more.

## Campaigns and contact lists

In Emelia, contacts live in lists, and a campaign enrolls the contacts of the lists attached to it. So every push writes to a list:

- **A campaign target**: Embers adds the lead to the campaign's first attached list, read at the moment of the push. If the campaign is running, that starts the sequence for that person.
- **A list target**: Embers adds the lead to that list. Nothing is sent until you attach the list to a running campaign in Emelia, and the configuration says so.

A campaign that is draft, paused, or finished still accepts the lead: it waits in the list, and **Needs attention** at the top of the page shows a warning with **Open Emelia** rather than pausing anything. The only thing Embers creates in Emelia is an empty contact list, from **Or create a new list**.

### Older LinkedIn-only campaigns

Emelia's earlier LinkedIn-only campaigns are listed with the others, with **(LinkedIn)** after the name. Each keeps its own contact list, so Embers adds the lead straight to the campaign instead of to a list. Pasting the id from the campaign's Emelia URL also works.

- **A public LinkedIn URL is required.** These campaigns have no email step. A lead known only by LinkedIn's id link waits while Embers looks up its public profile (see below). A lead that still has no public URL, or has only an email, is skipped with `no public LinkedIn URL (this campaign is LinkedIn-only)`, even with **ignore rules**. Embers never looks up an email for it.
- **Two extra variables**: `field1` carries the signal that surfaced the lead and `field2` its Embers score, unless you map them differently.
- **Draft and paused campaigns** hold the lead, as above.
- **Already in the campaign**: when Emelia answers that the person is already included, Embers marks the push **Delivered** and records the lead as sent there, so a later push to that campaign is skipped as `already pushed to` it.

## A public LinkedIn URL or an email

Emelia finds a person by LinkedIn profile or by email, and removes duplicates on either. Embers sends the public profile URL whenever the lead has one, and the email whenever Embers already holds it.

- **Public profile**: sent, with or without an email.
- **Email only**: sent by email.
- **Neither**: skipped with `no public LinkedIn URL or email for this lead`, even with **ignore rules**.

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 Emelia cannot use it. Embers fetches every matched lead's full profile, which brings the public URL, but a new lead can qualify a few minutes before that finishes. So the lead waits as pending until the public URL is in, looking the profile up itself only if nothing else will. If LinkedIn returns no public URL it is skipped with `LinkedIn returned no public profile URL for this lead`, and if the lookup has not finished after 2 hours, with `the profile lookup did not finish in time`. That lookup is the same profile fetch Embers makes to enrich a lead, and it is not available during a [free trial](/help/account-and-billing/free-trial/) that has reached its cap.

Embers never looks up an email for Emelia and never calls Emelia's email or phone finders, so no credits are spent on either side for you. Emails come only from [contacts you have already revealed](/help/outreach/lead-enrichment-and-contact-info/), which needs a paid plan; during the [free trial](/help/account-and-billing/free-trial/) leads go in by profile only.

## What Emelia receives

Each push adds or updates one contact with the LinkedIn profile URL, email when known, first and last name, job title, company name, phone when known, city, industry, and bio. Six custom variables come with it, usable in any LinkedIn or email step as `{{embers_signal}}` and so on: `embers_signal`, `embers_icp_reason`, `embers_score`, `embers_source`, `embers_lead_url`, and `headline`. Emelia creates each variable the first time a lead carries it.

**Change which Embers value fills each field**

On the **Field mapping** card, 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 (including country, company size, company industry, company LinkedIn URL, company website and company domain), or **Not sent**. On a connection made from 16 October 2026, Website takes the company website by default. An older connection keeps **Not sent** until you choose Company website in its field mapping.
- The LinkedIn profile URL is locked and always sent when public, because Emelia finds the lead by it or by the email.
- Add custom variables 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**

Emelia reports Draft, Running, Paused, Finished, and Archived. Only Running is sending. Draft, Paused, and Finished campaigns hold pushed leads in their list; Archived campaigns are not offered.

**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. Emelia checks as well: a person already in the list or campaign, matched by profile URL or email, is updated rather than added twice, and the push counts as delivered, never as an error. That covers people you added in Emelia yourself. A different campaign counts as a new push.

**Rate limits and the key**

Emelia does not publish a rate limit, so Embers keeps to at most 120 requests a minute per connection. Rate limits and 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 Emelia** (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 Emelia stays there, and your other Emelia connections are untouched.

## Troubleshooting

A problem with one campaign or list pauses only the configuration that sends to it; 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, and each item carries the button that fixes it. [Emelia delivery is paused](/help/troubleshooting/emelia-delivery-paused/) covers each reason in depth.

**Nothing is sent and Needs attention says a configuration "is off."** Every configuration is switched off, so no lead goes to Emelia. 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 "The campaign has no contact list attached."** The campaign has nowhere to put the lead. Attach a list to it in Emelia, then choose **Resume** beside it.

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

**Needs attention shows "Emelia API key was rejected."** The key was revoked. Copy a new key in Emelia, choose **Replace API key** on the **Connection** card, paste it, and choose **Save new key**. Your configurations stay, and delivery resumes.

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

**Leads land in the list but nobody is contacted.** The list is not attached to a running campaign, or the campaign is not running. Fix it in Emelia; the waiting contacts are enrolled once it runs.

**Leads are skipped with "no public LinkedIn URL or email for this lead".** Embers only knows that person by LinkedIn's internal id, could not look up a public profile, and holds no email. Leads skipped this way before 15 October 2026 were never looked up: choose **Send anyway** beside each one in Activity to look it up and send it. [Instantly](/help/integrations/instantly/) and [Smartlead](/help/integrations/smartlead/) look an email up before sending; Emelia never does.

## Related

- [Emelia delivery is paused](/help/troubleshooting/emelia-delivery-paused/): Every pause reason and how to clear it.

- [Control which leads reach each destination](/help/integrations/delivery-rules/): Rules, configurations, and the delivery log.

- [Push leads into HeyReach](/help/integrations/heyreach/): LinkedIn-only sequences, with a sender per campaign.

- [Push leads into Instantly](/help/integrations/instantly/): Email-only sequences, with the signal as the opener.

## Frequently asked questions

**Does Embers send the messages or the emails?**

No. Embers never sends anything on LinkedIn and never emails a lead. Emelia runs every step of the sequence, from the LinkedIn accounts and mailboxes connected to the campaign.

**What does a lead need to be sent to Emelia?**

A public LinkedIn URL or an email. A lead with a public profile goes in by its profile, a lead with only an email goes in by email, and a lead with neither is skipped.

**Does Embers look up a missing email for Emelia?**

No. A public LinkedIn URL is already enough for Emelia, so Embers never spends a contact lookup on its behalf. Emelia's own finder can add an address inside Emelia if your sequence needs one.

**My Emelia campaign is LinkedIn-only and Embers shows no campaigns. What now?**

Older Emelia LinkedIn-only campaigns are listed too, with "(LinkedIn)" after the name. Pick one as the target. They take a lead by its public LinkedIn URL only. A lead known only by LinkedIn's id link waits while Embers looks up its public profile; a lead with just an email is skipped for that campaign.

**We pay for several Emelia seats. Can each seat get leads?**

Yes. Each seat is its own Emelia account, so connect each one with its own API key, field mapping, and configurations. Growth connects up to 5 Emelia accounts per workspace, Enterprise and Agency up to 10, and Solo one. To keep each prospect with one seat, turn on One sender per prospect under Integrations.

**Can I connect Emelia, HeyReach, Instantly, and Smartlead together?**

Yes. Each has its own page and its own configurations, and a qualifying lead can go to all four, unless One sender per prospect is on. Then it stays with the first connection it reached.
