Skip to main content
Connect your Slack workspace and Tap will post when things happen — a hot lead captured, a CRM export finished, credits running out. You choose which channels Tap may write to, and which event goes where.
Only full-team admins can manage Slack. Find it under Integrations → Slack.

​
How it’s set up

There are two steps, deliberately separate: allow the channels, then map the events.
1

Connect the workspace

Connect Slack takes you to Slack to approve access, then brings you back.
2

Allow the channels Tap may post to

Tap lists the channels it can see and you tick the ones it’s allowed to use. Tap never posts anywhere else.For a channel Tap isn’t a member of yet, invite it in Slack first, then Refresh from Slack.
3

Map each event to a channel

Every event starts off. Turn on the ones you want and pick a channel for each, from the ones you allowed.Send test posts a test message so you can confirm it lands before you rely on it.
There is no fallback channel, ever. If a channel is removed or archived, the event stops posting and says so rather than quietly posting somewhere else. Pick another channel and it resumes.

​
The events

New lead captured posts every single lead. At a busy event that’s a channel nobody can read. Use Hot lead instead unless your volume is genuinely low — Tap warns you when you turn it on.Turning on both, pointed at the same channel, posts hot leads twice. Tap tells you when that’s about to happen.
The credits events are the ones most worth having on. They’re the only alerts that warn you about something that will otherwise stop working silently.

​
Checking what was sent

The Activity tab lists every message Tap tried to post — the event, the channel, whether it was Sent, Failed, or Queued, when, and how many attempts. Filter by status or event. It records the channel as it was at the time, so a message that went to a channel you’ve since renamed still shows where it actually landed.

​
When something stops posting

Tap can see the channel but isn’t in it. Invite it in Slack, then Refresh from Slack. Nothing is lost — the mapping stays.
The channel is gone or archived. The event stops and is flagged in the settings screen. Pick another channel.
If an event still uses it, Tap refuses and names the events: “Move these events off the channel first.” That’s deliberate — silently unmapping your alerts would be worse than refusing.
Access was revoked from the Slack side. Reconnect Slack — your allowed channels and event mappings are kept.
The approval Slack granted doesn’t cover what Tap needs. Disconnect and reconnect to approve again.

​
Disconnecting

Disconnect stops Tap posting. Your allowed channels and event mappings are kept for when you reconnect, so turning Slack off for a quiet month costs you no setup.

Integrations overview

Everything Tap connects to.