Sign In

Automations

Create rules that automatically take action when specific events occur.

What Are Automations?

Automations run actions when specific events happen in your system. They follow a simple pattern: when something happens (trigger), check if certain criteria are met (conditions), then do something (actions).

Components

Triggers - What starts the automation

Triggers define the event that initiates the automation:

Trigger Description
Monitor status changed When a monitor goes up or down
Incident created or changed When an incident is created or updated
Heartbeat status changed When a heartbeat check succeeds or fails

Conditions - When to run

Conditions filter which events should proceed. Based on the trigger type, you can check properties like:

  • Monitor name or type
  • Regions
  • Created timestamp

Conditions support operators like equals, not equals, greater than, less than, and contains.

Actions - What to do

Actions define what happens when conditions are met:

Action Description
Create incident Create a new incident with specified details
Send to recipient Send a notification to a user or channel
Set delay Wait before executing the next action

Common Uses

Auto-create incidents When a monitor goes down, automatically create an incident to track the issue.

Notifications Send notifications to specific recipients when incidents are created.

Delayed actions Add delays between actions for sequenced responses.

Automation Status

Automations have two statuses:

Status Description
Draft Being developed, not active
Published Active and running

Getting Started

  1. Go to Automations in your project
  2. Click Create
  3. Set a trigger to define when the automation runs
  4. Add conditions to filter events (optional)
  5. Add actions to define what happens
  6. Save as draft or publish when ready