AutoMerge is generally available

Last updated:

Explore Slack Integration Examples

Example automations demonstrating Slack integration patterns and use cases.

Example automations demonstrating common patterns for integrating Agent0 with Slack.

Example 1: Incident Triage from Slack

Goal: When someone posts "incident" in #incidents, automatically investigate and post findings.

Trigger:

  • Type: Slack message
  • Message keyword: incident
  • Channel names: incidents

Prompt:

Incident reported by {{slack.user.handle}} in #{{slack.channel.name}}.

Message: "{{slack.message.text}}"

Steps:
1. Parse the message for service names, symptoms, and time references
2. Query error rate, latency, and active alerts for affected services
3. Check recent deployment activity
4. Query logs for error messages matching the symptoms
5. Reply in thread — call `slackSendMessage` with channel `{{slack.channel.name}}` and threadTimestamp `{{slack.message.timestamp}}` — including:
   - Summary of what you found
   - Likely root cause or areas to investigate
   - Recommended next steps

Guardrails:

  • Allowed tools: slack:*, dash0:*
  • Required tool calls: slackSendMessage

Example 2: Failed Check Notification with Context

Goal: When a check fails, post detailed context to Slack.

Prerequisites:

  • A Slack notification destination configured for the check
  • The check must post to a channel where the Dash0 bot is a member

Trigger:

  • Type: Slack failed check
  • Channel names: alerts
  • Label filters: severity=high

Prompt:

Check "{{check.name}}" failed for service {{label.service}}.

Query the following for the last 30 minutes:
- Error rate and top 3 error messages
- p99 latency trend
- Recent deployments
- Correlated service health

Reply in thread to the alert — call `slackSendMessage` with channel `{{slack.channel.name}}` and threadTimestamp `{{slack.message.timestamp}}` — with:
- What changed recently
- Correlation with other metrics
- Recommended actions

Guardrails:

  • Allowed tools: slack:*, dash0:*
  • Required tool calls: slackSendMessage

Example 3: Service Status on Demand

Goal: Let team members ask about service health in any channel.

Trigger:

  • Type: Slack message
  • Message keyword: status
  • Channel names: (empty, match all channels)

Prompt:

{{slack.user.handle}} asked about service status in #{{slack.channel.name}}.

Message: "{{slack.message.text}}"

Parse the message for service names. For each service:
1. Query current error rate
2. Query p99 latency
3. Check for active alerts
4. Check recent deployment activity

Reply in thread — call `slackSendMessage` with channel `{{slack.channel.name}}` and threadTimestamp `{{slack.message.timestamp}}` — with a concise status summary for each service.

If the user asks follow-up questions, answer them with additional queries as needed.

Guardrails:

  • Allowed tools: slack:*, dash0:*
  • Required tool calls: slackSendMessage
  • Concurrency: Queue (prevent overlapping conversations)

Example 4: Emoji Reaction for Quick Checks

Goal: React with 🚀 to trigger a deployment health check.

Trigger:

  • Type: Slack reaction
  • Emojis: rocket
  • Channel names: deployments

Prompt:

{{slack.user.handle}} reacted with :rocket: to verify a deployment in #{{slack.channel.name}}.

Original message: "{{slack.message.text}}"

Parse the message for:
- Service name
- Deployment version or time

Query Dash0 for the 15 minutes after the deployment:
- Error rate compared to baseline
- Latency compared to baseline
- New error types introduced

Reply in thread using `slackSendMessage` with channel `{{slack.channel.name}}` and threadTimestamp `{{slack.thread.timestamp}}`, with a deployment health assessment. State whether the deployment is healthy or has issues in the reply.

Guardrails:

  • Allowed tools: slack:*, dash0:*
  • Required tool calls: slackSendMessage

Further Reading