AutoMerge is generally available

Last updated:

About Creating Automations

Create event-driven AI workflows that automate your observability and incident response with Agent0.

Create automations by defining triggers, writing prompts, configuring the sandbox and guardrails, and setting permissions. Dash0 provides several ways to create and manage automations to fit your workflow.

Create from Templates

The fastest way to start is with a pre-built template.

Templates

Templates include working configurations for common scenarios like incident triage, PR reviews, and deployment health monitoring.

  1. Navigate to Automations in the Dash0 sidebar.
  2. Click Templates to browse the catalog.
  3. Select a template that matches your use case.
  4. Review the pre-configured triggers, prompt, notifications, and guardrails.
  5. Customize the template to fit your needs.
  6. Click Create Automation.

See Use Templates for details on available templates.

Create from Scratch

Build automations step-by-step with full control over every configuration setting. Follow these guides for each component:

The form order is General → Triggers → Agent → Tools & Skills → Notifications → Sandbox → Guardrails. On wide screens, Agent appears beside the other sections. If custom skill selection is not available, Tools & Skills is labeled Tools. Configure tool access, required calls, and parameter overrides together through Configure tools in that section.

General automation settings showing name, description, and category fields

See Configure General Settings to set up basic automation information.

Trigger configuration showing scheduled trigger with cron expression

See Configure Triggers to define when automations run.

Prompt editor showing user prompt field with variable syntax

See Write Prompts to create effective instructions for Agent0.

Tools & Skills section showing configured tools and the Skills field

In Tools & Skills, click Configure tools to set Allowed, Required, and Parameter overrides for each tool. Select custom skills in the Skills field when available. See Configure tools and Allowed Skills.

Notifications configuration showing success and failure notification channel selection

See Configure Notifications to set up alerts when automation runs complete or fail.

Sandbox settings showing Setup script, Setup variables, and Parameters

See Configure Sandbox to prepare the runtime before Agent0 starts and define reusable prompt parameters.

Guardrails settings showing network access, tools, timeout, concurrency policy, max parallel runs, debounce, and credit budget options

See Set Guardrails to control Agent0's behavior and ensure safe execution.

Test Your Automation

Test a saved automation using the Test automation button:

Test automation button in the editor toolbar

Follow these steps to prepare and test your automation:

  1. Create and save the automation, then open its latest version with an account that has write permission for it. The Test automation button is not shown while creating a new automation, including from a template.

  2. Review the automation's triggers and external actions before enabling it. Testing requires an enabled automation, and enabling it also allows its configured triggers to start normal runs. Use test destinations for external writes.

  3. Enable the automation and save your changes. Save or discard any other pending changes, including restored drafts, and wait for saving to finish. The test button is disabled while the saved automation is disabled, you have unsaved changes, you are viewing a historical version, or a save is in progress.

  4. Click Test automation beside the Enabled switch on the Runs / Settings tab bar to open the test dialog.

  5. Choose your test method:

    Test automation dialog showing manual invocation and past trigger options

    • Manual invocation: Trigger a manual invocation of the automation with a simulated event. Enter custom values for variables to test different scenarios.
    • Choose a past trigger: Choose from events matching the trigger from the past 7 days. Replay a previous run's event data to debug "why did this behave differently?"
  6. Review the automation's setup script, allowed tools, and external actions before clicking Run test. A test starts a real automation run, including setup, and can perform permitted actions such as posting to Slack.

  7. Review the summary, tool calls, and status in the Runs tab.

  8. If the run failed or didn't do what you expected, adjust the prompt or guardrails, save your changes, and test again.

Tip

Use "Choose a past trigger" to reproduce issues. It replays the exact variables from a previous run, making it easy to debug unexpected behavior.

About Manual Invocation:

  • Use built-in variables like {{now}} and {{today}}
  • Trigger-specific variables will be empty unless you enter values
  • Marked as "manual" trigger type in run history
  • Simulates the incoming trigger event, not the automation's actions. Use test destinations for external writes.

Enable and Monitor

To enable an automation for normal operation and monitor its runs:

  1. Set Enabled to true in the automation editor.
  2. Click Save.
  3. Monitor runs in the Runs tab. Filter by status, trigger kind, or date range.
  4. Provide feedback on runs to help improve future executions.

Automations run in the background. You'll see results in the run history, and Agent0 will take actions like posting to Slack as configured.

Common Patterns

These patterns demonstrate typical automation use cases. Use them as inspiration when designing your own automations.

  • Incident response: Trigger on failed checks or Slack mentions. Query Dash0 for metrics, logs, and traces related to the failing service. Post findings to a Slack channel.
  • PR review assistance: Trigger on GitHub pull requests. Analyze the changed services for historical performance issues. Post recommendations to Slack. For PR comments, use gh CLI via bash with Trusted hosts only or Full Network and repository write access.
  • Scheduled reports: Run on a cron schedule. Query Dash0 for service health, error rates, and SLO compliance. Post a summary to Slack or send via webhook to an external system.
  • Slack-driven queries: Trigger on Slack messages containing specific keywords. Parse the question, query Dash0, and respond in thread with the answer.

Troubleshooting

If automations don't behave as expected, see the Troubleshooting section for detailed solutions to common issues:

Further Reading