Skip to main content
The Deck Slack app is a read-only assistant for your Deck account. Mention it or DM it to check on task runs, see which credentials are verified, pull metrics, or get answers straight from the Deck docs. It never changes anything in your account, so anyone on your team can use it safely. You don’t need a Deck account to ask it documentation questions. Connecting your account unlocks everything else.

​
Set it up

The Slack app is installed and removed in Slack itself, not the Deck Console. Uninstalling it doesn’t change anything in your Deck account.
1

Add Deck to your workspace

Add Deck to Slack and approve the install. You may need a Slack workspace admin to do this, depending on your workspace settings.
2

Connect your Deck account

Run /deck connect (or just DM the bot “connect”). You’ll be sent to a Deck sign-in page in your browser. Sign in with your normal Deck login.
3

Pick your organization

If you belong to one Deck organization, you’re connected automatically. If you belong to several, you’ll choose one. You can change it later by telling the bot “switch org” or running /deck switch-org.
The bot confirms the connection in Slack with the organization you’re signed into. From there, just ask it things.
Connecting is per person, not per workspace. Anyone in the workspace can ask documentation and general questions without connecting anything. Questions about account data (runs, credential status, metrics) require the person asking to connect their own Deck account: the bot answers with a token scoped to that person’s Deck role and organization, so teammates only ever see what their own access allows, and one person’s connection is never used to answer someone else’s question.

​
What it can do

Ask in plain language. A few examples:
  • “Did any task runs fail overnight?”
  • “Show me the last run for the utility bill task”
  • “How many credentials are unverified right now?”
  • “What’s our task success rate this week?”
  • “Which webhook deliveries failed yesterday?”
  • “How does session reuse work?” (answered from the docs)
  • “What’s new in Deck this month?” (answered from the changelog)
Behind the scenes it can look up:

​
Where to talk to it

  • DM the bot for anything, including questions about your account data.
  • @mention it in a channel to bring an answer into a team conversation. Replies post in the thread, visible to everyone in the channel. One mention is enough: the bot follows the thread from there, so people already talking with it can ask follow-ups without mentioning it again. It reads the room on those follow-ups, replying only when the message is for it and staying out of exchanges between teammates. People it hasn’t been talking to don’t get answered unless they mention it, and another app’s message is never treated as a question.
  • Use /deck commands for quick, structured lookups. Responses are only visible to you.
When you @mention the bot in a channel, answers about account data post in the thread, visible to everyone, labeled with the organization they came from. Use a DM or a /deck command when you want the answer kept to yourself. Personal messages, like connect prompts, org switching, and “which org am I in?”, are always shown only to you.
The bot remembers the last day of conversation in each thread, so you can ask follow-ups like “and the one before that?” without repeating context. In channel threads it has joined, it also reads the recent messages in that thread, so “what about the run above?” works even when someone else posted it.

​
Slash commands

/deck gives you instant, structured results without going through the assistant: Anything else you type after /deck is answered conversationally, same as a DM.

​
Limitations

  • Read-only. The bot can’t create, edit, run, or cancel anything. For state changes, like running a task or answering an interaction, it points you to the Console or the API.
  • One organization at a time. Ask it to “switch org” to move between organizations. Switching clears the conversation history for that thread.
  • Short memory. Conversation context is kept per thread for 24 hours, then discarded. Start fresh threads for unrelated questions.
  • Slack only. DMs, channel mentions, and the /deck command are the supported surfaces.

​
Security and privacy

  • Your permissions, not shared ones. Every person links their own Deck account, and the bot acts with a short-lived token scoped to that person’s role and organization. There is no shared workspace login.
  • Read-only by design. The bot’s tokens are only used to read data. It performs no writes against your account, which means it can’t create credentials or sources, start a task run, or make any other change on your behalf. Credential questions are answered from status metadata; stored secrets like passwords are never readable through the bot, or through the Deck API at all.
  • Connections expire. Access tokens are short-lived and refreshed automatically. If you don’t use the bot for 45 days, the connection expires and you’ll be asked to reconnect.
  • Nothing is stored long term. Conversation history is deleted after 24 hours. Sign-in links expire after 10 minutes. The bot keeps no lasting record of your messages or account data.
  • Verified requests. Every message from Slack is signature-verified before the bot processes it, and uninstalling the app immediately deletes the workspace’s credentials.
  • What leaves Deck. To answer a question, your message and the account data needed to answer it are processed by Deck’s LLM provider for that turn. In channel threads the bot has joined, that includes the thread’s recent messages, which it reads as context for follow-ups. Documentation questions are answered against the Deck docs and involve no account data.
To disconnect the bot from your workspace entirely, remove the app in Slack (Workspace settings → Manage apps). Individual connections also lapse on their own after 45 days without use.

​
Troubleshooting