Push qualified leads into Emelia

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.

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 producing leads, if you want to route agents to different campaigns.

Connect Emelia

1. 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.

2. 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 shows three cards: Connection, Configurations, and Delivery. Emelia shares no workspace name or sender count, so the Connection card shows neither.

3. Add a configuration

   Choose Add configuration. A configuration is one route, and you can add one per campaign:

   • Signals: All agents, or Only some to pick 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. How configurations route leads covers agent matching and overlapping configurations.

4. Check it

   Open the configuration’s … menu. For a campaign, Check readiness checks the key and the campaign, and never pushes a lead. For a list, Send a test lead pushes one person named “Embers Test” after you confirm. Remove them from the list afterwards.

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 the configuration shows a warning rather than pausing. 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, so a lead with only an email is skipped with no public LinkedIn URL (this campaign is LinkedIn-only), even with ignore rules. Embers never looks one up.
• 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.
• No update on repeats: Emelia only confirms the lead was accepted, so a person already in the campaign is not reported as updated.

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.

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, which needs a paid plan; during the 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.

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. Emelia delivery is paused covers each reason in depth.

A configuration 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 from the row’s … menu.

A configuration shows “Campaign or list no longer exists in Emelia.” It was deleted in Emelia. Choose Edit, pick another target, and save. Other configurations keep sending.

The Connection card shows “Emelia API key was rejected.” The key was revoked. Copy a new key in Emelia, choose Disconnect, and save the new key on the Setup card.

The Connection card shows “Emelia delivery retries were exhausted.” Emelia kept failing for about 6.3 days. Check Emelia, then choose Resume on the Connection card.

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 and holds no email. Instantly and Smartlead look an email up before sending; Emelia never does.

Related