Automation rules

What Are Automation Rules?

Automation rules let you define automatic responses to events. When a trigger fires and conditions match, actions execute automatically — no manual intervention needed.

Triggers

Trigger	When it fires
TEST_FAILED	A test run completed with FAILED status
TEST_RECOVERED	A previously failing test now passes
INCIDENT_CREATED	A new incident was opened
INCIDENT_RESOLVED	An incident was closed
TARGET_DOWN	Uptime confirms site is down
TARGET_RECOVERED	Site recovered from downtime

Conditions

Optional filters that must match for the rule to fire:

Test slugs — Only trigger for specific tests (e.g., only checkout-flow)
Severities — Only trigger for CRITICAL, WARNING, or specific levels
Recurrence count — Only after N recurrences of the same finding
Target IDs — Only for specific targets

Actions

Action	What it does
Escalate	Automatically change finding severity (e.g., WARNING → CRITICAL)
Suppress	Auto-mute the finding (prevent alerts and status impact)
Rerun	Schedule a retry after a configurable delay
Notify	Send notification to specific channels
Webhook	POST a JSON payload to an external URL
Add Note	Append a comment to the finding or incident

Example Rules

Tip: Auto-retry failed checkout:
Trigger: TEST_FAILED · Condition: test slug = "checkout-flow" · Action: Rerun after 5 minutes

Tip: Escalate recurring SEO issues:
Trigger: TEST_FAILED · Condition: recurrence ≥ 10, severity = WARNING · Action: Escalate to CRITICAL

Tip: Webhook on downtime:
Trigger: TARGET_DOWN · Action: Webhook to your PagerDuty endpoint

Managing Rules

Create and manage rules at a future dedicated automation page, or via the API:

automationRule.list — List all rules for your team
automationRule.create — Create a new rule
automationRule.update — Edit triggers, conditions, or actions
automationRule.delete — Remove a rule

Rules are evaluated in priority order. A rule can be disabled without deleting it.

Trigger

When it fires

TEST_FAILED

A test run completed with FAILED status

TEST_RECOVERED

A previously failing test now passes

INCIDENT_CREATED

A new incident was opened

INCIDENT_RESOLVED

An incident was closed

TARGET_DOWN

Uptime confirms site is down

TARGET_RECOVERED

Site recovered from downtime

Conditions

Optional filters that must match for the rule to fire:

Test slugs — Only trigger for specific tests (e.g., only checkout-flow)

Severities — Only trigger for CRITICAL, WARNING, or specific levels

Recurrence count — Only after N recurrences of the same finding

Target IDs — Only for specific targets

Actions

Action	What it does
Escalate	Automatically change finding severity (e.g., WARNING → CRITICAL)
Suppress	Auto-mute the finding (prevent alerts and status impact)
Rerun	Schedule a retry after a configurable delay
Notify	Send notification to specific channels
Webhook	POST a JSON payload to an external URL
Add Note	Append a comment to the finding or incident

Example Rules

Tip: Auto-retry failed checkout:
Trigger: TEST_FAILED · Condition: test slug = "checkout-flow" · Action: Rerun after 5 minutes

Tip: Escalate recurring SEO issues:
Trigger: TEST_FAILED · Condition: recurrence ≥ 10, severity = WARNING · Action: Escalate to CRITICAL

Tip: Webhook on downtime:
Trigger: TARGET_DOWN · Action: Webhook to your PagerDuty endpoint

Managing Rules

Create and manage rules at a future dedicated automation page, or via the API:

automationRule.list — List all rules for your team

automationRule.create — Create a new rule

automationRule.update — Edit triggers, conditions, or actions

automationRule.delete — Remove a rule

Rules are evaluated in priority order. A rule can be disabled without deleting it.