Notifications

!

Cloud feature — Notifications are available on superglue Cloud and are not available in the open-source version.

Notifications send real-time failure alerts or scheduled run summaries to Slack and email. Organization admins configure them under Settings.

Configure a channel

1. Choose Slack or email

   Add either channel independently. Each channel has its own connection, rules, and delivery state.

2. Configure delivery

   Enter the Slack credentials or email recipients, then save the channel.

3. Send a test

   Use the test action to confirm that the destination can receive notifications.

4. Create rules

   Choose real-time failure alerts, daily summaries, weekly summaries, or a custom combination of trigger sources and tool filters.

Slack

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.

Email

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

Rules are configured separately for each channel.

Delivery modes

Mode	Behavior
On failure	Sends a real-time alert when a matching run fails
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 and are skipped when the period has no runs.

Filters

Real-time rules can filter by:

• Trigger source
• Exact tool ID or a glob pattern such as finance-* or *-sync

Runtime notifications are sent for API, scheduler, incoming-webhook, CLI, and tool-chain runs. Manual dashboard, agent, and MCP runs are excluded from automatic failure notifications.

Delivery failures

Each channel tracks consecutive delivery failures. After three failures, superglue disables that channel to prevent repeated failed deliveries. Correct the connection details, send another test, and re-enable the channel.