Skip to main content
automate.onAccountUnhealthy fires when Automate.ax can’t refresh a connected account’s credential or the account fails a health check. Use it to send account failures to your own alerting, because triggers that depend on a broken account stop producing events without failing a run.
automations/alert-on-broken-account.automation.ts
The trigger watches every account linked to the deploying project’s organization. It fires once when an account goes from healthy to unhealthy. It won’t fire again for repeated failures until the account recovers, for example after you reconnect it. Revoking an account doesn’t fire this trigger. Provider outages, rate limits, timeouts, and network errors don’t fire it. Automate.ax records them with the PROVIDER_UNAVAILABLE code and checks the account again within 10 minutes. To watch another organization, pass a static Automate.ax binding with account. That organization API key needs account:read.

Trigger data

Organization admins also get an email that lists the affected automations and links to Connected Accounts. See Integration accounts for account status and how to reconnect.