Workflow executions can fail for several reasons, including API errors, network issues, and invalid data. When failures occur silently, they can lead to incorrect customer states, disrupt billing or entitlement flows or delay product access or provisioning.To make your workflows production-safe, we strongly recommend centralizing error handling using two mechanisms:
A dedicated Error Workflow
The Stop And Error node for conditional failure control
Use a dedicated workflow to act as a centralized error handler. This lets you respond to workflow failures by sending alerts (e.g. Slack/email), writing to logs, or notifying internal systems.
Instead of manually routing errors via nodes, you can automatically run an error handler workflow whenever a failure occurs.To set this up:
Open the main workflow that should be monitored for failures.
Click the Options (⋮) menu in the top-right corner.
Select Settings.
In the Error workflow field, choose the Error Handler workflow you created earlier.
Click Save.
This method ensures that any uncaught execution failure (e.g. a node error, network failure) will automatically trigger the error workflow — without needing to manually call it using an Execute Workflow node.
Workflows that use the Error Trigger do not need to be activated. They run automatically when a failure occurs.
If a workflow contains an Error Trigger, it uses itself as the default error workflow unless another is specified.
The Error Trigger does not run during manual executions. It only activates when the main workflow fails during automatic execution (e.g. via schedule, webhook, or other triggers).