Configuration Levels
Configure notifications at two levels:- Workspace-Level: Default notifications for all workflows unless overridden
- Workflow-Level: Apply to a specific workflow and override workspace settings
Event Types
Events You Can Subscribe To
These same events can also start another workflow — see Triggers.
Workflow Health
Subscribing to Workflow health gives you failure and recovery notifications for your workflows.- Failure: When a run fails, you receive a
workflow_failedevent with the error reason and a suggested action. - Recovery: When the workflow succeeds after a failure, you receive a
workflow_recoveredevent.
workflow_finished event for scheduled workflows, so you won’t receive both for the same run.
For real-time monitors, workflow_recovered is always sent when the monitor comes back online, regardless of other subscriptions.
System Events
These events are automatic and can’t be configured:Notification Channels
Create a channel before subscribing to events. One channel can receive multiple event types.
Payload structure varies by channel. Please see each channel’s documentation for format details and examples.
Data Change Configuration
Forworkflow_data_change events, filter what triggers notifications:
- Fields: Select specific fields to track (all by default)
- Conditions: Filter notifications based on criteria
- Change Type: Select what type of change you want to track
- Updated: Additions, modifications, and removals. Classifying a modification as an update requires at least one schema key field; without a key, it is reported as one removal and one addition.
- Added: New records only
- Removed: Deleted records only
The
workflow_data_change is triggered after the data changes are detected according to Change Detection Rules.Notification Content
Choose what notifications contain. Set workspace defaults in Settings → Notifications and override them per workflow.
CSV files are attached to the email when small enough; larger exports are delivered as a download link. The link is always included.