Skip to main content
RCB Automation can notify you and your team whenever something noteworthy happens — a workflow fails, a trigger stops firing, or an integration loses its connection. Configuring the right notifications means you catch problems quickly without drowning in alerts for routine activity. You can route notifications to email, Slack, or Microsoft Teams, and tune the frequency to match how your team works.

​
Types of notifications

RCB Automation generates notifications for the following events:
  • Workflow run success — fired each time a workflow completes without errors. Useful as an audit trail for high-value processes; noisy for high-frequency workflows.
  • Workflow run failure — fired when a workflow stops due to an error in any step. This is the most important notification type for operational health.
  • Trigger errors — fired when a trigger (webhook, schedule, or app event) fails to evaluate or fire correctly. Often indicates a misconfigured trigger or an upstream service problem.
  • Integration disconnections — fired when a connected app loses authorization, typically because credentials expired or were revoked. Workflows that depend on the integration will start failing until you reconnect.
  • Daily digest — a once-a-day summary of all workflow activity: runs completed, errors, and any open disconnections.
  • Weekly summary — a Monday overview of the previous week’s automation health, including trends in run volume and failure rate.

​
Configuring notifications by channel

Email notifications are enabled by default for workflow run failures and integration disconnections. You can adjust which events trigger emails and who receives them.

​
Configure email notifications

1

Open Notification settings

Go to Settings > Notifications in your workspace.
2

Select events

Under Email notifications, toggle the events you want to receive emails for. Options include run success, run failure, trigger errors, integration disconnections, daily digest, and weekly summary.
3

Set recipients

By default, notifications go to workspace Owners and Admins. Click Manage recipients to add or remove email addresses. You can add any workspace member or an external email address (useful for on-call inboxes or shared team accounts).
4

Save

Click Save notification settings.
Each workspace member can also control their personal email preferences independently from Account Settings > Notifications. Workspace-level settings define the defaults; individual preferences override them for that person only.

​
Notification frequency for email

For run success and run failure events, you can choose how email is batched:
FrequencyBehavior
InstantAn email is sent for each individual event as it occurs.
Daily digestAll events from the past 24 hours are combined into one email sent at 07:00 in your workspace timezone.
Weekly summaryAll events from the previous week are combined into one email sent every Monday at 07:00 in your workspace timezone.
Select the frequency from the dropdown next to each event toggle. Integration disconnection alerts are always sent instantly, regardless of this setting.

​
Muting notifications for a specific workflow

Sometimes a workflow is noisy during development or testing, or you want to silence alerts for a low-priority process without changing your workspace-wide settings. You can mute notifications at the workflow level.
1

Open the workflow

Navigate to the workflow in your dashboard and click Settings inside the workflow editor.
2

Open the Notifications tab

Select the Notifications tab in workflow settings.
3

Mute notifications

Toggle Mute notifications for this workflow to on. You can choose to mute all notification types or only specific ones (for example, mute run success but keep failure alerts active).
4

Optionally set an expiry

If you want notifications to resume automatically — for example, once testing is complete — set a Mute until date. After this date, notifications resume with your workspace defaults.
5

Save

Click Save to apply the mute setting.
Muting a workflow affects all notification channels — email, Slack, and Teams. If you only want to stop Slack pings without disabling email alerts, adjust the channel-level event toggles in Settings > Notifications instead.

​
Notification history and audit log

RCB Automation keeps a record of every notification sent, which is useful for confirming that alerts were dispatched and for diagnosing delivery issues. To view notification history, go to Settings > Notifications and click the History tab. The log shows:
  • Timestamp — when the notification was generated.
  • Event type — the event that triggered the notification (run failure, disconnection, etc.).
  • Workflow — the workflow associated with the event, with a link to the run detail.
  • Channel — where the notification was sent (email address, Slack channel, or Teams webhook).
  • Status — whether delivery succeeded or failed. Common failure reasons include a deauthorized Slack connection or an invalid Teams webhook URL.
Notification history is retained for 90 days. For a longer-running audit trail of workflow activity, use the run logs in the workflow detail view, which are retained according to your plan’s log retention policy.
If a notification shows a Delivery failed status, click the row to see the error detail and a Retry button that attempts to redeliver the notification.