Last updated:
Missing Integration Warnings
When you see a "Missing integration" badge or warning in the automation editor, it means the automation requires an external integration that isn't connected yet.
What the Warning Means
"Missing integration" badge on trigger:
- The trigger type requires an external service (Slack, GitHub, GitLab, Linear)
- That service's integration isn't connected to your Dash0 organization
- You can save the automation, but it won't trigger until the integration is connected
"Missing integration" in allowed tools:
- You're allowing tools from an integration that isn't connected
- The automation can run, but those specific tool calls will fail
Which Triggers Need Integrations
Slack Triggers
All Slack triggers require the Slack integration:
- Slack: Message
- Slack: Reaction
- Slack: Failed Check
What's needed:
- Slack workspace connection via OAuth
- Dash0 bot added to relevant channels
GitHub Triggers
All GitHub triggers require the GitHub integration:
- GitHub: Pull Request
- GitHub: Pull Request Review
- GitHub: Pull Request Review Comment
- GitHub: Deployment
- GitHub: Deployment Status
- GitHub: Release
What's needed:
- GitHub organization or account connection
- Repository access permissions
GitLab Triggers
All GitLab triggers require the GitLab integration:
- GitLab: Merge Request
- GitLab: Comment
What's needed:
- GitLab organization connection and the integration's webhook registered in GitLab, on a group or project
- The automation's creator connected their own GitLab account, with read-write access for any write. GitLab work runs as the creator, not a shared bot, so an automation created via the API, CLI, or Terraform has no acting user and cannot reach GitLab.
Linear Triggers
Linear triggers require the Linear integration:
- Linear: Comment
What's needed:
- Linear workspace connection via OAuth
- Access to relevant Linear teams/projects
Triggers That Don't Need Integrations
These work without external integrations:
- Schedule
- Failed Check
- Manual (test runs)
How to Connect Integrations
Connect Slack
- Go to Settings → Notifications.
- Add a notification channel and select Slack.
- Follow the authorization flow to connect your Slack workspace and grant permissions.
- Invite
@dash0to channels where automations should trigger.
For detailed setup instructions, see Set Up Slack Integration.
Connect GitHub
- Go to Settings > Integrations
- Find GitHub in the list
- Click Connect
- Follow the OAuth flow
- Grant repository access
- Add further GitHub installations if your automation needs repositories from other accounts or organizations. A Dash0 organization can connect multiple installations.
Connect Linear
- Go to Settings > Integrations
- Find Linear in the list
- Click Connect
- Follow the OAuth flow
- Grant workspace access
After Connecting
Once the integration is connected:
- Return to your automation
- The "Missing integration" badge should disappear
- Save the automation
- Enable it
- Test to verify the trigger works
If the badge persists after connecting:
- Refresh the page
- Verify the integration shows as "Connected" in Settings
- Check that you granted all required permissions during OAuth
Tools Require Integrations Too
Even if your trigger doesn't need an integration, using certain tools does.
Slack Tools
To call Slack tools (post messages, read channels):
- Slack integration must be connected
@dash0bot must be in target channels- Network Access setting: Works with No Network or Full Network
Sandbox operations need access to their destination hosts. Trusted hosts only allows listed hosts; use Full Network for other destinations. Slack connector tools work under any network setting.
GitHub Tools
To use GitHub read operations:
- GitHub integration must be connected (provides
githubListRepostool) - Repository access must be granted
- Network Access setting: Works with No Network or Full Network
For GitHub write operations (commenting on PRs, creating issues):
- Use
ghCLI via bash with Trusted hosts only or Full Network and repository write access - GitHub connector itself is read-only (
githubListReposonly)
The GitHub connector tools provide read-only access. Sandbox CLI operations use separate network and credential controls, not the tool allowlist or a matching trigger.
Linear Tools
To use Linear read operations:
- Linear integration must be connected
- Workspace access must be granted
- Network Access setting: Works with No Network or Full Network
Linear issue and comment write tools are available only when enabled for your organization. They still require integration access and permission under the automation's guardrails. If unavailable, post findings to another connected integration.
Dash0 Tools
Query tools (metrics, logs, traces) work without external integrations:
- Always available
- Work with No Network access level
- No integration setup needed
Troubleshooting Integration Issues
Integration Shows as Connected But Trigger Still Fails
Check:
- For Slack: Is
@dash0bot in the specific channel? - For GitHub: Do you have access to the specific repository?
- For Linear: Do you have access to the specific project?
Fix:
- Slack: Invite bot to channel:
/invite @dash0 - GitHub: Verify repository access in integration settings
- Linear: Verify team/project access in integration settings
Integration Connection Lost
OAuth tokens can be revoked (e.g., if the app is removed from your workspace or permissions are changed).
Symptoms:
- Integration shows as connected
- Tool calls fail with authentication errors
- Triggers stop working
Fix:
- For Slack, go to Settings → Notifications. For GitHub or Linear, go to Settings → Integrations.
- Inspect the affected connection and repository or channel access before reconnecting. A reconnection can affect other automations using it.
- Follow the integration's reconnection flow and reauthenticate if needed.
Multiple Workspaces/Organizations
Some services require you to choose which workspace/organization to connect.
Important:
- You can only connect one Slack workspace per Dash0 organization
- You can connect multiple GitHub installations to a Dash0 organization. Each installation controls access to its own repositories.
- Check that the installation covering the automation's repository is connected and has the required repository access.
To switch Slack workspaces, change the connection under Settings → Notifications and update automations that reference the old workspace. To add access to another GitHub account or organization, add its installation under Settings → Integrations without disconnecting existing installations.
Testing Integration Setup
Verify the integration works before enabling automations.
Test Slack Integration
- Create a test automation with Slack trigger
- Post a test message in Slack
- Verify the automation triggers
Test GitHub Integration
- Create a test automation with GitHub trigger
- Open a test pull request
- Verify the automation triggers
Test Linear Integration
- Create a test automation with Linear trigger
- Comment on a Linear issue
- Verify the automation triggers
Common Scenarios
New to Dash0, Setting Up First Slack Automation
Steps:
- Connect Slack under Settings → Notifications
- Invite
@dash0to relevant channels - Create automation with Slack trigger
- Test by posting a message
- Check run history to confirm it triggered
Adding GitHub PR Review Automation
Steps:
- Connect GitHub integration in Settings
- Grant access to repositories
- Create automation with PR trigger
- Open a test PR
- Verify automation runs and can comment
Slack Trigger Works But Can't Post Back
Problem:
- Trigger fires correctly
- But
slackSendMessagetool fails
Fix:
- Verify
@dash0bot is in the target channel - Open Tools & Skills → Configure tools, select
slackSendMessage, and check that Allowed is on. If every run must post, also turn Required on. - Review run logs to see the exact error message
Further Reading
- About Troubleshooting — Overview of common automation issues
- Configure Triggers — Set up triggers correctly
- Agent0 Doesn't Call Expected Tools — Fix tool access issues
- Automation Doesn't Trigger — Diagnose trigger problems