Nimbus can tell you about important events through email, Slack, and Microsoft Teams. Notification preferences are a matrix — every alert type can be routed to every channel independently, per Business Unit.
| Alert type | Fires when |
|---|---|
| `automation.failed` | An automation errors. |
| `automation.retry` | A rerun is attempted. |
| `automation.success` | An automation completes successfully. |
| `rerun.triggered` | A recovery rerun has been queued. |
| `rerun.succeeded` | A rerun recovered the automation. |
| `rerun.failed` | A rerun did not recover the automation. |
| `de.stale` | A data extension passed the critical staleness threshold. |
| `de.aging` | A data extension passed the warning staleness threshold. |
| `secret.expiring` | Stored credentials or secrets are nearing expiry. |
| `billing` | Billing or subscription events. |
| `account` | Account and membership changes. |
Open Settings → Notifications. You will see the alert-type-by-channel grid. Toggle on the combinations you want — for example, automation.failed to Slack and email, but automation.success to nothing. Preferences are saved per Business Unit, so a noisy account and a quiet one can be tuned independently.
The webhook URL is masked after saving. Only tenant admins and owners can add, edit, or remove integrations.
The Teams setup mirrors Slack: create an incoming webhook in the target Teams channel, enable Teams under Settings → Integrations, paste the URL, and send a test message.
Email goes to the address on your profile (or a separate notification address if you set one under Settings → Profile). Recovery emails — rerun triggered, succeeded, failed — include the automation name, the outcome, and a link back to the incident.