Email Alerts for Failed Automation Runs

Get one clear email when an automation run has failed, sent only to the people who asked for it and can act on it.

Failure emails could arrive for every failed attempt with no grouping, reach people who couldn't fix the automation, and say little about what went wrong. Runs that got stuck waiting never ended, so a late run looked the same as a lost one.

What's new

• One email per failed run — the email names the automation, gives a plain-language reason and the time, and includes a View run button that opens the run in Automation logs.

• One summary instead of a flood — further failures of the same automation within the hour arrive as a single summary with the most frequent reason.

• Only people who opted in and can act — each person turns on Automation failures in their notification settings. Only people who can both manage automations and view logs see the switch and receive the email.

• Choose which automations alert you — receive alerts for all automations or only selected ones.

• Company webhook — send every alert to your own endpoint as signed JSON, for use with your incident tools.

• Timed out status — runs that wait too long now end as Timed out, with the reason shown in Automation logs, and retrying a run that timed out waiting on Pool warns that the action may already have happened.

Why it matters

Admins hear about a broken automation before their workers do, and alerts stay meaningful because they are grouped and sent to the right people.

What to expect

Automation failure alerts are off by default, so nobody receives them until they turn Automation failures on in their notification settings.

Availability

Coming soon to an initial group of customers — contact your Customer Success representative to learn more.