Control which leads reach each destination

Every destination starts by receiving every lead that qualifies. Delivery rules narrow that down per destination, so a Slack channel, a CRM, or an outreach campaign only receives the people worth acting on.

What qualifies a lead in the first place

Before any rule runs, a lead has to qualify for delivery at all: a score above zero, a match with your ICP or a manual approval, and a company that is not on your blocklist. Rules can only narrow that set, never widen it. Rules decide what leaves Embers, not what Embers collects: a lead a rule holds back still appears on your leads list and in the Priority Queue.

Set the rules for a destination

1. Open the integration's page

   Open Integrations in the sidebar (/integrations) and choose the tool. Its page is /integrations/<tool>, for example /integrations/slack.

2. Find Who gets delivered

   On Slack, HubSpot, and Notion it is its own card, Who gets delivered, in the setup at the bottom of the page; Notion shows it once the field mapping is saved. On HeyReach, Instantly, Smartlead, and Emelia it is part of each configuration: choose its row on the Configurations card, or open the row’s … menu and choose Edit. The row’s Who gets through column sums it up, such as “Score 70 and up, ICP only”.

3. Set the rules and save

   Choose Save rules on Slack, HubSpot, and Notion, or Save changes on a configuration. The line under the heading summarises what you set, such as “ICP only, score 70+, 2 excluded titles”.

The five rules

HeyReach, Instantly, Smartlead, and Emelia configurations start tighter because a sequence is a costlier mistake than a message in a channel. They have no Sources rule: the agents a configuration listens to do that job, as the next section explains.

Each exclusion list takes up to 50 terms of up to 80 characters. A term matches whole words and ignores case, so intern holds back “Marketing Intern” and leaves “International Sales Lead” alone.

Embers checks the rules in the order of the table and stops at the first one that fails. That rule becomes the recorded reason, for example score 62 below 90, not an ICP match, or title matches excluded term 'intern'.

How configurations route leads

On HeyReach, Instantly, Smartlead, and Emelia, one connection holds any number of configurations. Each configuration is one route: the agents that feed it, the campaign or list it sends to, and its own rules.

• Agents. All agents sends every agent’s leads, including agents you add later, and says what that covers today, for example “Leads from every agent, including agents you add later. Today that is your profile, 2 watched profiles and every keyword.” Choose agents starts with nothing ticked, and saving asks you to “Choose at least one agent.” until you tick one. Under Profiles, your own profile is one row, Your profile, for your posts and the comments you leave, and each watched profile is one row by name. Under Other agents are Keywords and Qualified posts. Ticking Keywords offers All keywords, including keywords you add later, or Choose keywords to pick from your tracked keywords. A configuration saved before Your profile was one agent may show it half-ticked, with which half it still sends. Click it to choose both.
• How an agent matches a lead. Your profile, like a watched profile, matches people who engaged with that profile’s posts or its comments. With keywords chosen, Keywords matches a person who wrote, or engaged with, a post that matched one of them. Only posts the relevance check kept count, the same posts the leads list counts. All keywords and Qualified posts match by the kind of signal the lead has.
• The Agents column on the Configurations card names what feeds each row: “All agents”, “Your profile”, “Jasmin Alić, all keywords”, “Keyword “crm””, or a count such as “3 profiles, 2 keywords”. A row with only half of Your profile reads “Your posts” or “Your comments”, and one whose chosen keywords were all removed says “Keywords removed”.
• Two configurations, one lead. A lead that matches two configurations with different targets goes to both. With the same target it goes once, and the second is logged as already queued for that target.
• A deleted agent stops feeding the configuration. If every agent a configuration used is deleted, Needs attention at the top of the page warns Every agent this configuration used was deleted. Choose agents again. and it sends nothing until you edit it and choose agents again. If every chosen keyword was removed, it warns Every keyword this configuration used was removed. Choose keywords again. and Keywords matches nothing until you do.
• The switch on each row turns automatic sending on or off for that configuration alone. A configuration that is off can still receive a manual push.
• Also send leads you already have, offered when you add a configuration, sends the matching leads Embers already found, best score first, once. It passes the same rules, skips anyone already sent to that target, and stops at 5,000 leads. The row shows “Sending existing leads · 40 of 120” while it runs.

Read the delivery log

Slack, HubSpot, Notion, HeyReach, Instantly, Smartlead, and Emelia each list their deliveries on the Activity card of their page, newest first, with All, Failed, and Held back filters. Slack, HubSpot, and Notion keep 30 days of them. Each row is in one of these states:

A held-back row is not an error and is not retried on its own. Send anyway sends it regardless of the rules. To push a lead that is not in the log, use Send to and tick ignore rules.

A failed delivery is retried automatically on a fixed schedule: the first attempt plus seven retries, spread from 30 seconds out to about 6.3 days. Some failures, such as a revoked key or a deleted channel, pause the destination instead; each integration’s article lists them. Nothing is sent to a paused destination until you fix the cause and choose Resume.

Signed webhooks are not filtered

Signed HTTPS webhooks carry every qualifying lead so your own code sees the full stream and decides for itself. If you want a filtered feed on an endpoint, filter it on your side or in the automation tool that receives it.

Related