Skip to main content

​
Overview

Automation failure notifications email your team when an automation needs attention — a run failed, an automation can’t reach your CRM, or an automation couldn’t be turned on. Instead of checking the Runs page, you find out from your inbox. Failed-run emails link straight to the failed run; CRM connection and turn-on emails link to the automation. Notifications are opt-in. Nothing is emailed until an admin adds recipients to a notification rule.
These notifications are separate from Custom Notifications, which alert your team when a condition you define is detected in a lead conversation. Automation failure notifications only cover problems with your automations.

​
What Sends an Email

​
Setting Up Notifications

Only organization admins can manage notifications, like the rest of Automations.
  1. Open Automations in the sidebar and select the Notifications tab.
  2. Edit the default rule, or create a new rule.
  3. Add the email addresses that should receive notifications.
  4. Choose a Frequency and which automations the rule covers.
  5. Save the rule. Click Send test email to send a sample to the rule’s recipients and confirm delivery.
Every organization starts with one default rule that covers All automations with the frequency Immediately, then hourly summary, and no recipients. Add recipients to start receiving emails. The default rule can be edited or disabled, but not deleted. You can also manage notifications from an individual automation: open its ⋯ menu and choose Notifications to see the rules that cover it, or click Create a rule for this automation.

​
Rules

Each rule decides who is emailed, about which automations, and how often. Your organization can have up to 50 rules.

​
Frequencies

​
Volume limit

To keep a burst of failures from flooding inboxes, each recipient receives at most 10 immediate emails per day for your organization. After that, further failures arrive in hourly summaries instead. The 10th email tells you the limit has been reached. Summaries, digests, and emails about CRM polling or turning an automation on or off don’t count toward the limit.

​
What’s in the Email

An email for a single failed run includes:
  • The automation’s name and when the run failed
  • Which step failed, with a plain-language reason
  • The CRM record that triggered the run
  • Links to View run (opens that run’s details directly), Open automation, and Notification settings
Summary and digest emails group failures by automation, with a count for each reason and up to 5 example runs per automation. Each summary links to the Runs page filtered to failed runs.

​
Deliverability

Notification emails are sent from alerts@notifications.apten.ai. If your organization uses strict mail filtering, add this address to your allowlist so notifications aren’t held or sent to spam. Use Send test email on a rule to confirm they arrive.