Sign In

Automations

Create rules that automatically take action when specific events occur. For example, create an incident when a monitor fails or send notifications based on severity.

What are Automations?

Automations run actions when specific events happen. For example, create an incident when a monitor goes down or send a Slack message for P1 alerts.

Components

Triggers - What starts the automation

  • Monitor status changes
  • Incident creation
  • Scheduled times

Conditions - When to run

  • Severity levels
  • Monitor tags
  • Time of day

Actions - What to do

  • Create incidents
  • Send notifications
  • Add comments

![Placeholder: Automation Builder Interface Showing Trigger, Conditions, and Actions]

Common Uses

Automations help reduce manual work and ensure consistent responses:

Auto-create incidents - When a production monitor goes down, automatically create a P1 incident

Severity-based notifications - Send SMS for P1 issues, Slack for P2, and email for lower priorities

Maintenance windows - Suppress alerts during scheduled maintenance to avoid noise

Escalation - If a P1 incident isn’t acknowledged in 5 minutes, page the backup on-call

Features

  • Toggle on/off - Enable or disable automations without deleting them
  • Execution history - See when automations ran and what actions they took

Best Practices

  • Start simple - Begin with basic “if monitor down, create incident” rules
  • Clear naming - “Create P1 for Production API Down” not “Automation 1”
  • Specific conditions - Use tags and severity to avoid false triggers

Getting Started

  1. Go to Automations
  2. Click Create
  3. Set trigger, conditions, and actions
  4. Save and enable

![Placeholder: Automations List Page with Create Button]

Learn more