Know the moment something
needs your attention

A default failure alert fires the moment a workflow run ends in a failure state, meaning any step ran into an error that retries did not recover and the workflow stopped without reaching its end state. The alert includes the workflow name, the run identifier, the failing step, the error message, the inputs that produced it, and a link into the execution log. Default alerts are enabled out of the box for every workflow, so the team is never silently exposed to a failure.

Open the alert configuration panel of any workflow and add a new rule. For a success notification, pick the on success trigger and choose who is notified and through which channels. For a custom alert, pick the condition that fires it, duration over a threshold, failure rate over a threshold, specific error category, or custom field match, and define it using the same visual builder as triggers. Save it and it applies to every future run.

Email and in app notifications are available for every workspace out of the box, and more channels can be added through workspace integrations. Common channels include Slack and Microsoft Teams for messaging based teams, custom delivery destinations for teams with their own systems, and the WorksBuddy notification center. Routing rules send different alerts to different channels, so the on call engineer gets the urgent alert in the messaging tool while the ops lead gets the digest in email.

Per-workflow rules apply only to the workflow they belong to, while workspace-wide rules apply across every workflow. Use workspace-wide rules for the baseline: failure notifications, error rate thresholds, audit alerts on sensitive changes. Use per-workflow rules for what each needs: different recipients, tighter thresholds for critical workflows. Both layers compose, so per-workflow rules override the defaults.

The audit log captures three categories with full context. User actions cover sign ins and outs, permission changes, role assignments, and every operation a user performs. Workflow changes cover every edit, with a diff of what changed. System events cover integration installs and removals, scheduled runs, and automated retries. Every entry includes timestamp, identity, resource, and before and after state.

Audit data is retained for the lifetime of the workspace by default, so the record is always available for compliance reviews and incident investigations. Configurable retention policies let teams age out older data after a set window, with automatic export to long-term storage first. The full audit log can be exported as a document or data file anytime, with filters for date range, user, workflow, or event category.