Skip to main content
An automation rule runs an action automatically when something happens to an incident — “when a critical incident opens, post to #major-incidents and file a ticket”. Rules are declarative and human-configured: you define when → then, and scaling.cloud fires the action every time the condition matches. No AI is involved, and there is no approval step — that is the difference from a proposed action. Automation rules are available on every plan, including Free.

​
When → then

A rule has three parts:

​
Conditions

Conditions are simple equality checks, mirroring the attributes you already match on in routing selectors:
  • severity equals one of critical, high, medium, low.
  • component equals one of the incident’s affected components.
All conditions must hold for the rule to fire (logical AND). There are no ranges, OR, or negation — keeping rules flat and predictable, just like routing and escalation. Leave conditions empty to act on every incident for that event.
An action that an automation rule fires is attributed to the rule’s author, not to whoever happened to acknowledge or resolve the incident.

​
Managing rules

Create and manage rules in the dashboard under Automation Rules. Each rule has a name, an enabled toggle, its when event, its conditions, and its action. Disable a rule to stop it firing without deleting it. See Create an automation rule for a walkthrough.

​
API

Rules are also managed over the /v1 API: Authenticate with an API key as described in Authentication.

​
Rules vs. proposed actions

Both fire the same action types, but they are reached differently: