Sources
Slack source
Route incoming personal DMs, exact mentions, and opt-in channel posts and replies into a mailbox.
When to use it
Choose Slack when you want an agent to handle messages that need your attention without forwarding them or interacting with Doorbell in Slack.
Example
A colleague DMs you or @mentions you in a channel you can read. Doorbell stores the message if your Slack capture settings allow it. A matching route admits it to Ops, where separate Inbox triggers notify Amp and Grok independently.
Set it up
- Open Sources → New source → Slack account. If Slack is not configured, ask the service operator to enable the integration.
- Choose Connect with Slack and review the requested access. Verify the connected person and workspace shown in Doorbell. Installing the app in Slack alone does not connect your Doorbell source. Your organization may require administrator approval.
- Choose what to capture. Incoming personal DMs, direct mentions of you, deliberate messages to Doorbell, and message text start on. Group DMs start off. Disable message text to retain metadata only.
- For channel capture, enter allowed channel IDs and enable posts, thread replies, or both. Each choice starts off. An empty list captures no additional channel traffic. Choose Review changes, inspect affected mailbox routes and inbox triggers, then Apply reviewed changes. All-message routes receive every newly permitted message.
- In Mailboxes, select a mailbox and open Configure > Routes. Add a route from your connected Slack account. Choose a Slack message kind and an optional channel ID. Both conditions must match. Saved-policy warnings do not change capture or verify Slack access; a route cannot enable message text or additional message kinds.
- Grant each receiving agent the mailbox separately. For push notices, add an Inbox trigger for each tested destination with match.source set to slack. Polling agents check Inbox directly.
- Have another person send a fresh DM to your connected human, then directly @mention that human in an accessible channel. Check Mail and each destination's handoff. Test a nonmatching message if you added a condition.
Important limits
- Personal DMs and exact human mentions belong to the authorized recipient. Your own outgoing personal messages are excluded. Deliberate DMs and @mentions addressed to Doorbell belong to their connected sender. Channel-wide mentions do not qualify.
- One source connects one human identity in one workspace. The identity belongs to one Doorbell customer, even after disconnect. Reconnect through that customer's account. You can link up to ten identities.
- Slack requires broad conversation-history permissions. Doorbell retains only selected new messages while connected, not conversation history. Slack notification preferences, unread state, and Do Not Disturb do not control capture.
- Channel capture never grants Slack access or includes your own channel messages. Exact mentions keep their existing kind and switch, including in threads. Parent context is a separate opt-in that requires message text. Doorbell links only an available parent already captured by the same source. It never fetches or copies parent text. Erased or expired parents stay unavailable.
- Messages expire seven days after acceptance. Reading, organizing, and notification delivery do not extend that lifetime. Text is limited to 8,192 characters and marked when truncated. Files, attachments, history import, later edits and deletes, posting as you, and agent replies to Slack are not supported.
- Pausing a trigger stops its notifications, not Slack capture or mailbox entries. Resuming does not notify about skipped arrivals. To stop storing new messages, turn off the relevant capture choices in Slack settings. This does not erase old content.
- Capture changes apply to future messages and do not rewrite existing content. Disconnect or provider revocation erases captured content and derived copies throughout Doorbell. A pending reference-only notice may still deliver if it also covers other available mail. Reconnecting does not restore revoked content or import missed messages. External originals are unchanged. Data already retrieved or transmitted and requests in flight cannot be recalled.
- Doorbell does not run the receiving agents. A running or scheduled agent checks Inbox directly; a push workflow needs a compatible webhook. Generic tests do not establish live Grok Bot or Dots compatibility.
Troubleshooting
- For Reconnect required, open the Slack source and authorize the same human and workspace again. If access is denied, check your organization's app policy or request administrator approval.
- If your workspace cannot install Doorbell, ask the service operator whether the app is available outside its original workspace. A working installation in one workspace does not establish availability elsewhere.
- If no message arrives, check the connected identity, Slack capture choices, the route, and its conditions. Use a fresh incoming message from another person, not an old message, an edit, or your own outgoing DM.
- If applying capture reports a configuration conflict, review again. The source, selecting routes, or inbox triggers changed after the previous review. Your draft is preserved, but its earlier approval cannot save changed configuration.
- If a stored message has no mailbox entry, check the route's conditions. If mail arrived without a notice, check trigger status, fixed-batch timing, quiet hours, and delivery history. Pending is not delivered, and delivered is not completed.
- If disconnect reports that Slack could not confirm remote revocation, remove Doorbell's authorization in Slack too. Local disconnection still blocks capture and message reads.
Technical reference
Slack capture, mailbox membership, and notification delivery are separate. Source message history can show mail without a matching route. Several mailboxes can share one canonical message; each agent's per-message read state remains independent within each mailbox.
read_mailbox checks unread Inbox by default. Follow nextCursor until complete, then start the next check without a cursor. set_mailbox_read_state changes only the caller's state. mailbox_delivery_status reports related recipient names and independent handoffs without admin access or webhook secrets.
For optional Amp confirmation mail in shared Ops, explicitly approve Ops as its own recipient. Amp sends to Ops with replyTo and a declared kind. Grok's confirmation trigger uses match.source internal, match.authorAgentId for Amp, and a separate fields.kind rule. Display names, fields.agent, and ordinary MCP payload claims do not authenticate Amp. All Ops readers can still see the confirmation, even if only Grok is notified.
Use list_slack_sources or list_routable_sources to discover owned connection IDs, actual capture, and effective policy. The latter also lists typed stored fields. Effective policy describes consent, not verified Slack reachability. Use save_mailbox_route with source family slack and source-relative paths such as kind, sender.id, and channelId. Text and parent-context conditions require those fields in saved capture.
Admin agents with configuration:write can call review_slack_capture with the complete desired policy, preserving unrelated choices. Show the customer its capture delta, mailbox routes, and inbox triggers. After approval, apply through set_source_capture with family slack, instanceId, reviewed capture, expectedGeneration, reviewToken, and approved true. Messaging-only connections cannot use these tools. OAuth and credential actions remain website-only. A review token detects stale configuration, not human consent.
Slack events contain kind, channelId, messageTs, sender: {id,kind}, and optional text. Message kinds are direct_message, group_direct_message, mention, doorbell_direct_message, doorbell_mention, channel_message, and thread_reply. Disabled message kinds are not captured. Metadata-only capture removes text and parent-context links before matching.
Threaded events preserve threadTs and optional parentUserId. A reply has isThreadReply true and parentRef with the root's channelId and messageTs. Broadcasts have isThreadBroadcast true. Optional parentContext contains a linked messageId or an unavailable status. A parent reference does not grant access to another mailbox; every read checks current availability.
The Slack HMAC preset under Webhook sources only verifies incoming HTTP events. It does not connect a human Slack identity or subscribe to that user's DMs and mentions. Use this dedicated Slack source for personal notifications.