Notifications
Notifications send real-time failure alerts or scheduled run summaries to Slack and email. Organization admins configure them under Settings.
Configure a channel
Section titled “Configure a channel”Add Slack and email independently. Each channel has its own connection, rules, and delivery state.
- Choose Slack or email.
- Enter the Slack credentials or email recipients.
- Save the channel.
- Use the test action to confirm that the destination can receive notifications.
- Create rules for real-time failure alerts, daily summaries, weekly summaries, or a custom combination of trigger sources and tool filters.
Slack supports two authentication methods:
| Method | Use when |
|---|---|
| Incoming webhook | A single fixed Slack channel is enough |
| Bot token | You need to select channels or post to multiple public channels |
Bot-token setup requires a token beginning with xoxb- and a channel ID. Private channels must invite the bot before it can post.
Slack messages include View Details and Investigate Failure actions when an app URL is available.
Add one or more recipients and, optionally, a custom from address.
Email alerts contain the tool, run status, run ID, trigger source, timestamp, error, and failed step. They also link back to the run when an app URL is available.
Notification rules
Section titled “Notification rules”Rules are configured separately for each channel.
Delivery modes
Section titled “Delivery modes”| Mode | Behavior |
|---|---|
| On failure | Sends a real-time alert when a matching run fails |
| On success | Sends a real-time alert when a matching run succeeds |
| On completion | Sends a real-time alert when a matching run finishes |
| Daily summary | Sends the previous day’s results at 09:00 UTC |
| Weekly summary | Sends the previous week’s results on Monday at 09:00 UTC |
Summaries include successful and failed run counts by tool.
Filters
Section titled “Filters”Real-time and summary rules can filter by:
- Trigger source
- Exact tool ID or a glob pattern such as
finance-*or*-sync
Recover from delivery failures
Section titled “Recover from delivery failures”Each channel tracks consecutive delivery failures. After three failures, superglue disables that channel to prevent repeated failed deliveries.
To restore the channel:
- Correct the connection details.
- Send another test.
- Re-enable the channel.
Which runs send automatic failure notifications?
Section titled “Which runs send automatic failure notifications?”Real-time notifications are sent for API, scheduler, incoming-webhook, CLI, and tool-chain runs. Manual, agent, and MCP runs are excluded from real-time notifications. Summaries count them.
Is a summary sent when there are no runs?
Section titled “Is a summary sent when there are no runs?”No. Summaries are skipped when the period has no runs.