By default, when a step in your flow fails, that failure is recorded in the flow’s execution log — useful if you’re actively watching, easy to miss if you’re not. The Custom Error Handler feature lets you attach an actual action to a flow’s errors, so instead of just being logged, they get sent somewhere: an email to your team, a row in a tracking spreadsheet, a message in Slack, or anything else a component’s action can do.
Any component that has an action can be attached as a flow’s error handler — there’s no separate “error handling” component to learn. From a flow’s draft, you add error handling and pick which component and action should run when something in the flow fails; that action then receives the error’s details (its name and message, at minimum) as its input, the same way any other action receives input from a previous step.
Two examples cover most use cases:
A few things are worth knowing before you configure one: