Send qualified leads to Slack

Slack is the fastest way to get a qualified lead in front of a person. Embers posts one card per event into a single channel, with the score, the reason the person matched, the evidence, and a suggested opening line.

Before you start

• You need permission to install apps in your Slack workspace, or someone who does.
• Decide which channel should receive leads. A quiet, dedicated channel beats a busy one.
• If you want a private channel, invite the Embers bot to it before you pick it.

Connect Slack

1. Open Settings, then Integrations

   In the Embers app, go to Settings, then Integrations (/settings/integrations). Slack is in the list of destinations.

2. Install the Embers Slack app

   Choose Connect Slack. Slack asks you to approve the bot. Embers requests chat:write, chat:write.public, channels:read, and groups:read: enough to list channels and post, and nothing that reads your messages.

   Slack sends you back to the Integrations screen when the install is done.

3. Choose one channel

   Pick the channel Embers should post into. Public channels appear automatically. A private channel only appears once the Embers bot has been invited to it.

   There is one channel per account. Embers cannot route different events to different channels yet.

4. Choose which events post

   Four events can be delivered:

   Event	What it means	Default
   New leads	A scored engager matched your ICP or was approved manually	On
   Engagement and signal refreshes	A lead you already have engaged again. One message per lead per scan	Off
   Status changes	A lead moved to a different pipeline status	Off
   Report ready	A report finished generating. The message links to it	Off

   A new install starts with New leads only. Turning everything on in a busy account produces a lot of messages, so add the others one at a time.

   There is also a master switch. Turning it off keeps the install and your event choices, and stops the posting.

5. Send a test message

   Use Send test. Embers posts a card built by the same code as a real delivery, prefixed with Test, so you can check the channel and the formatting before a real lead arrives.

What the Slack card shows

Each lead card is built to answer one question: is this person worth a message right now?

• Header: the person’s name and company.
• Fields: the score, the ICP verdict, and the strongest signal.
• Why now: one sentence explaining what they just did.
• Evidence: a short quote from the post or comment, its source, and a link to it. Left out when there is nothing to quote.
• Suggested open: the stored DM draft. It is a draft to edit, and you send it from LinkedIn yourself.
• Contact: email and phone, but only when Embers already has them stored. If contact information has not been found, the row is left out rather than showing an empty placeholder.
• Buttons: Open in Embers and a link to the LinkedIn profile.

Report events post a shorter card with an Open report button.

Retries and pauses

Slack delivery uses the same retry schedule as webhooks: the first attempt plus seven retries, spread from 30 seconds out to roughly 6.3 days. Rate limits and Slack server errors are retried.

Some Slack errors are terminal and pause the installation instead of retrying: the token was revoked, the channel was deleted or archived, or the bot was removed from the channel. When that happens, Embers stops posting and shows the reason on the Integrations screen. See Slack delivery is paused for how to fix each case.

Delivery history is kept for 30 days and shown on the Integrations screen, with the state, any error, and the HTTP status of each attempt.

Related