Skip to main content

On Error node

The On Error node handles workflow errors: it triggers when a node fails and executes the branch connected to it (alert, fallback, log) instead of letting the execution fail without control. It allows capturing execution errors, implementing a fallback or alert logic and continuing the workflow after a controlled error.

It is a starting point, like the Trigger node: it has no input handle and cannot be connected to directly. It triggers automatically when an error occurs in the workflow.

Parameters​

The On Error node triggers as soon as a node of the workflow fails. The only parameter is the tracing mode:

ParameterTypeRequiredDefaultDescription
Tracing modeComplete / Standard / Performance❌—Level of detail recorded for this node in the trace — see Tracing modes.

Input​

The On Error node receives the information of the error that occurred:

{
  "error": {
    "message": "Error message",
    "code": "ERROR_CODE",
    "details": {}
  },
  "node": "nodeName",
  "lastResponse": {}
}

Output​

The On Error node executes the branch connected to it (alert email, fallback call, log, etc.). The error information remains available in the following nodes via {{error.message}}, {{error.code}}, {{error.details}}, {{node}} and {{lastResponse}}.

Errors​

The On Error node produces no error of its own: it triggers on the failure of another node of the workflow (HTTP, SQL, code error, etc.).

When is the error handled?

A node fails (HTTP, SQL, code error, etc.). According to its Stop the workflow execution on failure configuration:

  • Enabled (true, default): the workflow stops, unless an On Error node is present in the workflow — in this case the error triggers the On Error node.
  • Disabled (false): the workflow continues and the error is available in lastResponse.

Without an On Error node, a node that fails with Stop the workflow execution on failure enabled stops the workflow.

Example​

Email alert:

  1. Add an On Error node to the workflow.
  2. Connect its handling branch to it: On Error node → Send an email node with the content of {{error.message}}.
  3. When a node of the workflow fails, the team receives an alert without the workflow being blocked.

Fallback to a backup API:

  1. Add an On Error node to the workflow.
  2. Connect its handling branch to it: On Error node → HTTP(S) Request node to the backup API.
  3. The processing continues with the backup API data.

See also​