Sign In

Triggers & Conditions

Define the situations under which your automation should run.

In Upstat, all automations begin with a trigger—an event or change that causes the system to evaluate your rule. Once triggered, the automation checks whether your defined conditions are met before executing any actions.

What Triggers an Automation?

An automation is evaluated when any of the following events occur on an incident:

  • The incident is created
  • The incident is updated
  • A label is added or removed
  • The severity or status changes
  • A participant is added
  • A catalog item is linked or removed

These triggers are not configured manually—they’re built into the system. You define what happens when those triggers occur and the conditions that must be true for the rule to activate.

What Are Conditions?

Conditions are checks that determine whether an automation should proceed.
If all conditions pass, the actions are executed (either immediately or after a delay).

Supported Conditions

You can build conditional logic based on:

  • Severity — e.g., only trigger if severity is High or Critical
  • Status — match incidents in a specific lifecycle stage
  • Labels — include or exclude incidents based on tags
  • Acknowledgment state — whether the incident has been acknowledged
  • Linked catalog items — match based on associated services or entities
  • Time since creation or update — used in delayed actions

Each condition can be configured to match specific values, and you can combine multiple conditions using AND logic.

Condition Matching

All conditions in a rule must be true for the automation to run.
If any condition fails, the rule is skipped.

There is currently no support for OR conditions or grouping, but this may be expanded in the future.

Condition Tips

  • Use labels to create conditional checkpoints (e.g., add escalated to prevent duplicate actions)
  • Use severity or catalog linkage to route incidents differently
  • Combine time-based delays with conditions like Not acknowledged for escalation logic

Summary

  • Automations are triggered automatically when incidents change
  • Conditions define when the automation should continue to run
  • All conditions must be true for actions to execute
  • You can match on severity, status, labels, catalog links, and more

Learn more