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 and HubSpot it is a section of the settings card, under the event toggles. On HeyReach, Instantly, Smartlead, and Emelia it is part of each configuration: open the row’s … menu and choose Edit.

3. Set the rules and save

   Choose Save rules on Slack and HubSpot, 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.

• Signals. All agents sends every agent’s leads, including agents you add later. Only some lets you tick specific agents. A watchlist agent matches people who engaged with that profile’s posts or comments; the other agents match by the kind of signal the lead has.
• 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, the row warns you and it sends nothing until you choose new signals.
• 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 and the outreach tools list their recent deliveries, 30 days of them, on the integration’s page. HubSpot’s page shows only the state of the last delivery. Each row is in one of these states:

A skipped 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