Sign In

Actions & Delays Reference

Reference for configuring automation actions and delays.

Actions

Actions define what happens when an automation’s trigger fires and conditions are met. Each automation must have at least one action.

Create Incident

Creates a new incident when the automation runs.

Field Description
Title Incident title (can include variables)
Description Incident description
Severity Incident priority level

Use cases:

  • Auto-create incidents when monitors go down
  • Create incidents from heartbeat failures

Send to Recipient

Sends a notification to specified recipients.

Field Description
Recipient User or notification channel
Message Notification content

Use cases:

  • Alert on-call engineers
  • Notify team channels
  • Send status updates

Set Delay

Pauses execution before the next action.

Field Description
Duration How long to wait
Unit Seconds, minutes, or hours

Use cases:

  • Wait before escalating
  • Space out notifications
  • Allow time for auto-recovery

Adding Actions

1. Click Add Step

In the automation builder, click the add button between steps or at the end of the workflow.

2. Select Action Type

Choose from the available action types.

3. Configure Action

Fill in the required fields for the selected action type.

Action Sequencing

Actions execute in order from top to bottom. Use delays between actions to control timing.

Example sequence:

  1. Create incident - Document the issue
  2. Set delay - Wait 5 minutes
  3. Send to recipient - Notify if not resolved

Conditions Between Actions

You can add conditions between actions to create branching logic. Conditions placed after a trigger filter all subsequent actions.

Configuration Examples

Auto-Create P1 Incident

Field Value
Action Create incident
Title Monitor Down: {monitor.name}
Severity P1

Notify After Delay

Field Value
Action 1 Set delay (5 minutes)
Action 2 Send to recipient
Recipient On-call team

Immediate Notification

Field Value
Action Send to recipient
Recipient #incidents channel
Message Alert: {monitor.name} is down

Limitations

Limitation Description
Action order Actions run sequentially, not in parallel
Maximum delay Delays have maximum duration limits
Required fields All action fields must be completed