Notification Sinks¶
Get real-time alerts in Slack when important chatbot events happen — new conversations, incoming messages, or auto-paused threads that need human attention.
Availability
Notification sinks are available on Medium and Pro plans. You can also manage sinks through the platform support assistant using natural language.
What Are Notification Sinks?¶
Notification sinks deliver alerts to external services (currently Slack) when events occur in your chatbot conversations. Instead of checking the dashboard constantly, you get notified in the tools you already use.
Use cases:
- Get a Slack ping when a new customer starts chatting
- Alert your support team when a conversation is auto-paused because a customer is upset
- Monitor all incoming messages across channels in a dedicated Slack channel
Trigger Types¶
Each sink listens for one or more trigger types:
| Trigger | Fires When | Best For |
|---|---|---|
| NEW_CONVERSATION | First message in a new thread | Knowing when customers reach out |
| EVERY_MESSAGE | Every incoming message | Full visibility on active threads |
| AUTO_PAUSED | A channel rule triggers and pauses AI | Escalation alerts that need human action |
A single sink can listen for multiple triggers. For example, you might want both NEW_CONVERSATION and AUTO_PAUSED on one Slack channel.
How Triggers Interact¶
- EVERY_MESSAGE fires on all messages, including the first message in a new thread
- NEW_CONVERSATION fires only on the first message — if you have both triggers on one sink, the first message matches both (you'll get one combined notification)
- AUTO_PAUSED fires separately when a channel rule detects a condition and pauses the conversation
Origin Filtering¶
By default, sinks receive notifications from all channels (Shopify Widget, Instagram DM, Website Widget, Gmail, etc.). You can narrow this with an origin filter.
Supported origins:
SHOPIFY_WIDGET · WEBSITE_WIDGET · IG_DM · IG_COMMENT · FB_MESSENGER · FB_COMMENT · GMAIL
Examples:
- Only Shopify alerts: set origin filter to
SHOPIFY_WIDGET - Only social media: set origin filter to
IG_DM,IG_COMMENT,FB_MESSENGER,FB_COMMENT - Everything: leave origin filter empty
Setting Up a Slack Notification Sink¶
Step 1: Create a Slack Webhook¶
- Go to Slack API: Incoming Webhooks
- Create a new app or use an existing one
- Enable Incoming Webhooks
- Add a webhook to your desired channel
- Copy the webhook URL (starts with
https://hooks.slack.com/)
Step 2: Create the Sink¶
You can create notification sinks in two ways:
- Go to Conversations > Channel Rules
- Find the Notification Sinks section
- Click Create Sink
- Enter a name (e.g., "#support-alerts")
- Paste your Slack webhook URL
- Select trigger types
- Optionally set an origin filter
- Save
Ask the platform support assistant directly:
"Create a notification sink called #escalations with my Slack webhook https://hooks.slack.com/services/... for AUTO_PAUSED triggers on SHOPIFY_WIDGET"
The assistant can create, list, and test sinks for you.
Step 3: Test It¶
After creating a sink, send a test notification to verify the webhook works:
- Dashboard: Click the Test button next to your sink
- Support assistant: Ask "test my notification sink"
You should see a test message appear in your Slack channel within a few seconds.
Health Monitoring¶
Notification sinks track delivery health automatically:
| Field | Meaning |
|---|---|
| Last success | Timestamp of the last successful delivery |
| Consecutive failures | Number of failed deliveries in a row |
| Last error | Error message from the most recent failure |
Auto-Disable¶
If a sink fails 10 consecutive times, it is automatically disabled to prevent wasted resources. You'll receive an in-app notification when this happens.
Common failure causes:
- Slack webhook URL was revoked or the Slack app was deleted
- The Slack channel was archived
- Network issues (temporary — sink will recover on next success)
To fix: Update the webhook URL or re-enable the sink after resolving the issue.
Multiple Sinks¶
You can create up to 10 notification sinks per account. Use multiple sinks to route different events to different Slack channels:
| Sink | Triggers | Origin Filter | Slack Channel |
|---|---|---|---|
| #new-leads | NEW_CONVERSATION | WEBSITE_WIDGET | #sales |
| #shopify-alerts | NEW_CONVERSATION, AUTO_PAUSED | SHOPIFY_WIDGET | #support |
| #escalations | AUTO_PAUSED | (all) | #urgent |
Slack Message Format¶
Notifications arrive as formatted Slack messages with:
- Channel origin (e.g., Shopify Widget, Instagram DM)
- Customer name or visitor identifier
- Message preview — the customer's message text
- Thread ID for quick reference
Auto-pause notifications additionally include:
- Triggered conditions — which detection rules fired
- Evaluation phase — PRE or POST
- Pause count — how many times this thread has been paused
Troubleshooting¶
Not receiving notifications
Check in order:
- Sink is active? — Check the sink status in Channel Rules
- Correct triggers? — Does the sink listen for the event type you expect?
- Origin filter? — Is the message coming from a filtered-out channel?
- Webhook valid? — Send a test notification to verify
- Auto-disabled? — Check consecutive failures count
Getting too many notifications
- Remove
EVERY_MESSAGEtrigger if you only care about new conversations - Add an origin filter to limit which channels trigger alerts
- If volume is still high, consider using
NEW_CONVERSATION+AUTO_PAUSEDonly instead ofEVERY_MESSAGE
Notifications stopped working suddenly
- Check if the sink was auto-disabled (10+ consecutive failures)
- Verify the Slack webhook is still valid (webhooks can be revoked)
- Check if your Slack app is still installed in the workspace
Next Steps¶
- Set up channel rules with auto-pause conditions that trigger
AUTO_PAUSEDnotifications - View conversations to follow up on alerts
- Reply to users when you receive an escalation alert