Set Up Slack Integration

Connect your Slack workspace to Dash0 so your team can mention @dash0 in a channel to ask Agent0 questions, run automations that trigger from Slack messages, reactions, and check alerts, and let Agent0 post messages, add reactions, and read channel content.

Prerequisites

Before installing the Slack integration:

• Slack workspace admin access: You need permission to install apps in your Slack workspace.
• Dash0 organization: The integration connects to one Dash0 organization.
• Choose the right workspace: Each Dash0 organization can connect to one Slack workspace. Ensure you install in the workspace where your team collaborates on observability and incidents.

Install the Integration

1. Navigate to Integrations Settings

1. Open Dash0 and navigate to Settings → Integrations.
2. Find Slack in the integrations list.
3. Click Connect or Install.

2. Authorize the Dash0 App

You'll be redirected to Slack's OAuth authorization page.

1. Select your workspace from the dropdown if you're signed into multiple workspaces.
2. Review the permissions Dash0 requests.
3. Click Allow to grant access.

Slack redirects you back to Dash0 after authorization completes.

3. Verify the Installation

After authorization:

1. Return to Settings → Integrations in Dash0.
2. Confirm the Slack integration shows as Connected.
3. Note the connected workspace name.

The Dash0 bot is now installed in your Slack workspace.

4. Add the Bot to Channels

The Dash0 bot must be a member of channels where automations should trigger or post messages.

1. Open a Slack channel where you want to use automations.
2. Type /invite @dash0 and press Enter.
3. The bot joins the channel and can now receive messages, reactions, and post responses.

Repeat for each channel where automations will operate, or where your team wants to ask Agent0 questions. Once the bot is in a channel, anyone can tag it: see Ask Agent0 in a Slack Channel.

What Permissions Are Granted

The Dash0 Slack app requests these OAuth scopes. Each one is listed with what Dash0 does with it.

Alerting and notifications:

• chat:write: Post messages as the Dash0 bot, and edit or delete the messages it posted.
• chat:write.public: Post to a public channel without joining it first.
• channels:read: Look up public channels by name, so you can pick one as a notification target.
• channels:join: Join a public channel when a notification needs to be posted there.
• groups:read: Look up private channels the bot is a member of, for the same channel picker.
• files:read: Read files shared in channels the bot is in, so Agent0 can look at a screenshot someone posted. Dash0 also uses it to confirm that a chart image it uploaded finished processing.
• files:write: Upload chart images that are attached to alert notifications.

Agent0, for both mentions and automations:

• app_mentions:read: Detect when someone tags @dash0 in a channel.
• channels:history: Read the thread Agent0 was tagged in, so it can see what was said before the mention, and look up other messages a question refers to. Public channels the bot is in.
• groups:history: The same, in private channels the bot is in.
• reactions:read: Detect emoji reactions, which automations can use as a trigger.
• reactions:write: Add 👀 while Agent0 works and replace it with ✅ when it finishes, and let automations react to messages.
• users:read: Look up who tagged Agent0, and confirm that person belongs to the workspace before linking their account.
• users:read.email: Read that person's email address, which is how Dash0 matches a Slack user to a Dash0 account.
• im:history: Receive direct messages sent to the bot, so Agent0 can read the conversation and answer in it.
• im:write: Open a direct message with a person, so Agent0 can send one when an answer or an automation is meant for them alone.
• assistant:write: Run Agent0 conversations in Slack's assistant view: set the thread status while it works, and offer suggested prompts.

Sign in with Slack:

• openid, email, profile: Granted when a person signs in to Dash0 with Slack. They read that person's own name, profile photo, and email address, and nothing in the workspace.

What Events Are Captured

After installation, Slack sends these events to Dash0:

• message.channels: Messages posted in public channels where the bot is a member.
• message.groups: Messages posted in private channels where the bot is a member.
• message.im: Direct messages sent to the bot.
• reaction_added: Emoji reactions added to messages in channels where the bot is a member.
• app_mention: Messages mentioning @dash0.
• assistant_thread_started: Someone opens an Agent0 conversation in Slack's assistant view.
• assistant_thread_context_changed: The channel that assistant view is looking at changes.
• app_uninstalled: The app is removed from your workspace.

Dash0 matches message and reaction events against your enabled automations and triggers those with matching filters. The mention and assistant events drive Agent0 conversations instead.

Security and Data Handling

Token Storage

Dash0 stores your Slack bot token encrypted in the database. The token is used only to call Slack APIs on behalf of your automations.

Message Visibility

The Dash0 bot only receives messages from channels where it's explicitly invited. It cannot read messages from channels where it's not a member.

Data Retention

Event data (message text, user handles, timestamps) is retained only for the duration needed to match triggers and execute automations. Historical event data is not stored beyond what's needed for audit logs.

Messages Agent0 reads to answer a mention are kept in that Agent0 conversation, which is the context the agent works from and which you can open in Dash0. They are not stored anywhere else.

Manage the Installation

Update an Older Install

An install from an older version of the Dash0 Slack app is missing the Agent0 scopes, so mentions and Slack tools do not work until an admin re-authorizes.

Symptom: Dash0 reports "An organization admin needs to update the Slack app to the latest version to enable all features."

Fix: Disconnect and connect the integration again, following the steps in Reconnect After Token Revocation. Alert notifications keep working either way.

Reconnect After Token Revocation

Slack bot tokens do not expire, but they can be revoked (e.g., if the app is removed from your workspace). If automations stop triggering or Slack tools fail with authentication errors:

1. Go to Settings → Integrations in Dash0.
2. Click Disconnect on the Slack integration.
3. Click Connect again.
4. Complete the OAuth flow to issue a new token.

Existing automations continue to work with the new token without modification.

Switch to a Different Workspace

To connect a different Slack workspace:

1. Disconnect the current integration in Settings → Integrations.
2. Click Connect and authorize the new workspace.
3. Update any automations that reference channel names from the old workspace.

Uninstall the Integration

To remove the Dash0 app from your Slack workspace:

Option A: From Dash0

1. Go to Settings → Integrations.
2. Find Slack and click Disconnect.
3. This removes the integration from Dash0.

Option B: From Slack

1. Open Slack and go to Settings & administration > Manage apps.
2. Find Dash0 in the installed apps list.
3. Click Remove to uninstall.

After uninstalling, automations with Slack triggers will no longer fire, and Slack tools will fail.

Test the Installation

Verify the integration works before building production automations.

Test with a Manual Message

1. Create a test automation with a Slack message trigger.
2. Set the message keyword to something unique like test-dash0.
3. Configure the prompt to call slackSendMessage and reply in thread.
4. In guardrails, add slack:slackSendMessage (or slack:*) to Allowed Tools.
5. Save and enable the automation.
6. In a Slack channel where the bot is a member, post: test-dash0
7. Verify the automation triggers and replies.

Test Bot Visibility

Verify the bot is visible in channels:

1. Open a channel in Slack.
2. Type @dash0 in a message.
3. If the bot appears in autocomplete, it's a member of the channel.
4. If not, use /invite @dash0 to add it.

Troubleshoot Installation Issues

OAuth Authorization Fails

Symptoms:

• Slack shows an error during authorization.
• You're redirected back to Dash0 without a connected integration.

Common causes:

• You don't have admin permissions in the Slack workspace.
• The workspace has app installation restrictions.

Fix:

• Contact your Slack workspace admin to install the app.
• Check workspace app approval settings in Slack admin console.

Bot Doesn't Appear in Channel Member List

Symptoms:

• You typed /invite @dash0 but the bot didn't join.
• The bot isn't visible in the channel member list.

Fix:

• Verify the integration shows as Connected in Dash0 settings.
• Try inviting again: /invite @dash0
• Check that the channel is in the same workspace you authorized.

Automations Don't Trigger from Slack

Symptoms:

• You post a message matching your trigger keyword.
• The automation doesn't run.

Common causes:

• The bot isn't in the channel where you posted.
• The automation is disabled.

Fix:

• Verify the bot is a member of the channel: check the member list or type @dash0.
• Ensure the automation is Enabled in the automation editor.
• Check the automation's run history for errors.

See Automation Doesn't Trigger for detailed troubleshooting steps.

Integration Shows as Connected But Tools Fail

Symptoms:

• The integration appears connected in settings.
• Automations trigger successfully.
• slackSendMessage or other Slack tools fail with errors.

Common causes:

• The bot isn't in the target channel where the tool is trying to post.
• Slack tools are not included in Allowed Tools.

Fix:

• Add the bot to the target channel: /invite @dash0
• Verify Allowed Tools includes slack:* or specific Slack tools like slack:slackSendMessage.

Multiple Workspaces or Organizations

One Workspace Per Dash0 Organization

Each Dash0 organization can connect to one Slack workspace. If your company uses multiple Slack workspaces, you'll need to choose which one to connect.

When to use separate Dash0 organizations:

• Your team operates in multiple isolated Slack workspaces.
• Different teams need separate automation configurations.

When to use one Dash0 organization:

• All teams collaborate in one primary Slack workspace.
• Automations should span multiple services or teams.

Multiple Dash0 Organizations in One Workspace

The same Slack workspace can be connected to multiple Dash0 organizations. Each organization gets its own connection, and they all share the same bot in your workspace.

When connecting additional organizations, follow the same installation process for each one. The bot will respond to triggers configured in each organization's automations.

Next Steps

After installing the Slack integration:

1. Create your first Slack automation: Start with a simple message trigger that queries Dash0 and replies in thread.
2. Add the bot to relevant channels: Ensure the bot is a member of channels where automations should operate.
3. Explore Slack trigger types: Learn about message, reaction, and failed check triggers.
4. Experiment with Slack tools: Test sending messages, adding reactions, and reading channel content from automations.

Further Reading

• Ask Agent0 in a Slack Channel — Mention @dash0 to ask questions from Slack
• Configure Slack Triggers — Configure Slack message, reaction, and failed check triggers
• Use Slack Tools — Send messages, add reactions, and read channel content
• Explore Slack Integration Examples — Example automations and best practices
• Troubleshoot Slack Integration — Resolve common Slack integration issues