# Push qualified leads into Instantly

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

> Connect Instantly with an API key, then add configurations that send each agent's leads into its own campaign, with the signal as the opener.

Instantly runs cold email sequences; Embers decides who is worth one. Connect the two and a lead Embers qualified lands in an Instantly campaign as soon as it surfaces, with the signal that surfaced them as the opening line.

> **Warning: Solo and above, administrators only**
>
> Integrations require Solo or above, and only a workspace admin can connect Instantly or change its configurations. Solo connects one Instantly workspace per Embers workspace; Growth connects up to 5, and Enterprise and Agency up to 10. Instantly can run beside [Smartlead](/help/integrations/smartlead/). Leads are sent with an email, and emails are revealed on paid plans only, not during the free trial.

Embers never emails a lead. Instantly does the sending, from the mailboxes the campaign already owns; Embers pushes the lead.

## Before you start

- An Instantly workspace you administer, and a campaign or lead list to receive the leads.
- A paid plan, for leads to actually arrive. See [Every lead needs an email](#every-lead-needs-an-email).
- At least one [agent](/help/getting-started/choose-your-agents/) producing leads, if you want to route agents to different campaigns.

## Connect Instantly

### Create an Instantly API key

In Instantly, open **Settings**, then **Integrations**, then **API keys**, and create a key. Give it the campaign, lead list, and lead scopes, and nothing more; read access to accounts is not needed, because Embers shows no mailbox count for Instantly. Instantly has no sign-in for other apps, so a key is the only way in.

### Save it in Embers

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

Embers checks the key against Instantly 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 Instantly", with a line of facts under it, such as "37 leads sent · last sent 3 Oct, 9:31 · 1 configuration on · workspace Acme". Below it come the **Configurations**, **Activity**, **Field mapping**, and **Connection** cards; the Connection card names your Instantly workspace.

### 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**. There is no sender to choose, because an Instantly campaign already owns the mailboxes it sends from.
- **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. Each still needs an email, so leads without one are looked up first.

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, which proves the whole path; it shows on the **Activity** card badged "Test lead". Remove them from the list afterwards.

## Connect more than one Instantly workspace

Each Instantly workspace has its own API keys, campaigns, and mailboxes. To feed several of them from one Embers workspace, connect each one. On the Instantly page, open the **...** menu at the top and choose **Connect another Instantly account**, give the connection a name, and paste a key from that workspace. 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 Instantly account** sits beside the tabs.

- **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 takes your Instantly workspace's name, with "2" or "3" added if that name is taken. 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 "Instantly: Acme".
- **Every match is sent, by default.** Automatic delivery sends a lead to every configuration it matches, across all connections, so two Instantly 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 Instantly: Acme`. 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 **Instantly: Acme**, 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.** Embers reads which Instantly workspace a key belongs to, so connecting a workspace that is already connected is refused, even with a different key: "This Instantly account is already connected as Instantly: Acme."
- **Separate pauses.** Disconnecting one connection, or a rejected key that pauses one, leaves the others sending.
- **Reconnecting brings it back.** Connecting a key from the same Instantly workspace 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 Instantly connection per workspace. Upgrade to connect more." A downgrade keeps the connections you already have and only stops you adding more.

## Every lead needs an email

Instantly addresses a lead by email, and public LinkedIn activity carries none. So when a lead headed to Instantly has no email, Embers looks it up first, with the same [contact lookup](/help/outreach/lead-enrichment-and-contact-info/) as the **Reveal** button, and holds the delivery until the lookup finishes.

- **Found**: the lead goes to Instantly with its email, usually within a minute or two.
- **Not found**: skipped with `no email found for this lead`. Embers remembers the empty result for 30 days rather than paying for the same lookup again.
- **Too slow**: a lookup still running after 30 minutes is skipped with `the email lookup did not finish in time`.

A lead is looked up once, however many configurations are waiting on it. These skips stand even with **ignore rules** or **Send anyway**, because there is nothing to send to.

During the [free trial](/help/account-and-billing/free-trial/) contact details are locked, so leads headed to Instantly are skipped with `emails are revealed on paid plans, not during the free trial`. **Needs attention** at the top of the Instantly page says so, as "Only leads that already have an email are sent", with **See plans**. They start flowing once you choose a plan.

## What Instantly receives

Each push creates one Instantly lead with the email, first and last name, company name, job title, and phone when Embers holds one. The signal fills Instantly's own `{{personalization}}` field, so it drops into your opening line with nothing to configure. Seven custom variables come with it, usable in a sequence as `{{embers_signal}}` and so on: `embers_signal`, `embers_icp_reason`, `embers_score`, `embers_source`, `embers_lead_url`, `linkedin_url`, and `location`.

Instantly accepts leads into a campaign in any status and holds them until it runs. For a campaign that is not active, **Needs attention** shows "Campaign is not running (Draft). Instantly holds the leads until you start it." with **Open Instantly**, and the configuration's row shows the status in amber: nothing is lost, and nothing is sent until you start 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.
- Email is locked: Instantly finds the lead by it.
- 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.
- Embers reads the chosen campaign's sequence and offers each `{{variable}}` it uses that nothing fills yet, as a one-click row. Variables Instantly fills itself, such as `{{firstName}}`, are not offered.
- **Reset** returns every field to the defaults. Choose **Save fields** to keep your changes.

**Campaign statuses**

Instantly reports Active, Running subsequences, Draft, Paused, Completed, Accounts unhealthy, Bounce protect, and Account suspended. Only the first two are sending, but every status accepts pushed leads and holds them. Embers never starts, pauses, or resumes a campaign. The only thing it creates in Instantly is an empty lead list, from **Or create a new list**.

**Repeat pushes and verification**

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. Instantly also skips anyone already in the campaign, so one person cannot enter it twice by two routes. A different campaign counts as a new push.

Embers never asks Instantly to verify leads on import, because verification spends your workspace's credits.

**Instantly and Smartlead side by side**

Both email tools can be connected on one Embers workspace. Each has its own page, key, field mapping, and configurations, and each configuration picks one campaign or list in its own tool. Automatic delivery runs every matching configuration, and repeats are checked per tool and campaign, so if Instantly and Smartlead configurations listen to the same agents, one lead goes into both tools; the email is looked up once. To keep one tool per lead, split them by agents or by delivery rules.

When both could take a manual push, [Send to](/help/leads/send-to-destination/) lists each tool's configurations under its name and you pick one. A paused Instantly connection only stops its own configurations; Smartlead keeps sending, and the other way round.

**Rate limits and the key**

Instantly allows 6,000 API requests a minute and 100 a second per workspace, shared by every key including its older API. Embers takes at most 600 a minute. 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 Instantly** (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 Instantly stays there, and your other Instantly 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. [Instantly delivery is paused](/help/troubleshooting/instantly-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 Instantly. 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 "Instantly API key was rejected."** The key was deleted, or lacks a scope. Check the scopes first; otherwise create a new key, choose **Replace API key** on the **Connection** card, paste it, and choose **Save new key**. Your configurations stay, and delivery resumes.

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

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

**Leads are skipped with "no email found for this lead".** The lookup found no address for that person. Nothing more can be done for Instantly; [HeyReach](/help/integrations/heyreach/) or [Emelia](/help/integrations/emelia/) can reach them by LinkedIn profile.

**Leads are skipped during the trial.** Contact details unlock with the first paid month. See [Change your plan](/help/account-and-billing/change-plan/).

**Leads are in the campaign but nobody is emailed.** The campaign is not active. Start it in Instantly.

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

## Related

- [Instantly delivery is paused](/help/troubleshooting/instantly-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.

- [Reveal a lead's email and phone](/help/outreach/lead-enrichment-and-contact-info/): Where the email comes from.

- [Push leads into HeyReach](/help/integrations/heyreach/): The same idea for LinkedIn sequences.

## Frequently asked questions

**Does Embers send the emails?**

No. Embers never emails a lead. Instantly does, from the mailboxes connected to the campaign. Embers pushes leads.

**What happens to a lead that has no email yet?**

On a paid plan, Embers looks the email up first, the same lookup as the Reveal button, and sends the lead once it is found, usually within a minute or two. A lead with no email found is skipped. Embers never guesses an address.

**Can I push into a campaign that is not running yet?**

Yes. Instantly accepts the lead and holds it until you start the campaign. Embers shows a warning under Needs attention at the top of the Instantly page rather than pausing the configuration.

**Can I connect Instantly and Smartlead on the same workspace?**

Yes. Each has its own page, key, field mapping, and configurations, and each configuration picks one campaign. If both listen to the same agents, a lead goes into both tools; split them by agents or delivery rules to keep one tool per lead. In Send to you pick the configuration.

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

Yes, on Growth and above. Connect each Instantly 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.

**Does Embers spend my Instantly verification credits?**

No. Embers never asks Instantly to verify a lead on import. Verify inside Instantly if you want it.
