Sign In

Triggers & Conditions Reference

Reference for configuring automation triggers and conditions.

Triggers

Triggers define the event that starts an automation. Each automation has exactly one trigger.

Monitor Status Changed

Fires when a monitor’s status changes.

Property Description
Event Status transition (UP to DOWN, DOWN to UP)
Monitor The affected monitor

Available condition properties:

  • name - Monitor name
  • monitorType - Type of monitor (HTTP, TCP, etc.)
  • regions - Monitoring regions
  • createdTimestamp - When the monitor was created

Incident Created or Changed

Fires when an incident is created or updated.

Property Description
Event Incident created or status changed
Incident The affected incident

Heartbeat Status Changed

Fires when a heartbeat monitor’s status changes.

Property Description
Event Heartbeat received or missed
Heartbeat The affected heartbeat monitor

Conditions

Conditions filter which trigger events should execute the automation’s actions. Conditions are optional.

Condition Structure

Each condition consists of:

Component Description
Property The field to evaluate
Operator How to compare
Value What to compare against

Operators

Operator Description Example
== Equals name == "Production API"
!= Not equals monitorType != "TCP"
> Greater than createdTimestamp > "2024-01-01"
< Less than Use for date comparisons
>= Greater than or equal Numeric comparisons
<= Less than or equal Numeric comparisons
contains Value exists in list regions contains "us-east"

Combining Conditions

Multiple conditions can be combined using:

AND - All conditions must be true

name == "Production API" AND monitorType == "HTTP"

OR - Any condition must be true

name == "Production API" OR name == "Staging API"

Setting Up Triggers

1. Select Trigger Type

When creating an automation, choose the trigger from the available options.

2. Configure Trigger Condition

After selecting a trigger, you can add conditions to filter events.

3. Add Multiple Conditions

Click Add Condition to add additional filters. Select AND or OR to define how conditions relate.

Examples

Monitor Down with Specific Name

Trigger only when a specific monitor goes down:

Component Value
Trigger Monitor status changed
Property name
Operator ==
Value Production API

HTTP Monitors Only

Trigger only for HTTP type monitors:

Component Value
Trigger Monitor status changed
Property monitorType
Operator ==
Value HTTP

Multiple Regions

Trigger when monitor in specific regions:

Component Value
Trigger Monitor status changed
Property regions
Operator contains
Value us-east