Error Trigger

Fires when any node in the run fails unhandled — runs its downstream branch as a recovery phase of the same (still failed) run.

Finding it in the library

Search the builder's node library for Error Trigger (it lives under Error Handling). A single click opens the in-editor docs panel shown here — description, ports, and every property, without leaving the canvas. Double-click (or drag) to add it to the workflow.

Library capture pending — regenerate with npm run shots:nodes.

Wired up in the builder

Error Trigger in a real, runnable flow — captured live from the Studio editor, exactly as it looks on your canvas. This is the same workflow used for the example input & output below.

Canvas capture pending — regenerate with npm run shots:nodes.

How it’s configured

The node’s Configure panel as it opens in the builder when you select the step — every setting laid out with real values. Click any field to edit it.

Config capture pending — regenerate with npm run shots:nodes. See the full property reference below.

Ports

This is a trigger — it starts runs and takes no input wire.

Ports are the node’s contract with its neighbours. In the editor a port label renders bold when wired and italic when optional; ◈ ports accept attachment carriers rather than data wires.

How data flows through it

As a trigger, Error Trigger starts runs — it takes no input wire. What it emits is the request wrapper: the event’s body becomes the payload, and the wrapper carries the event metadata around it (for an HTTP-style trigger that’s headers.*, request.method, request.path and query). Downstream nodes consume the content — the wrapper is unwrapped at each node boundary, and expression roots like {{ headers.x }} still resolve against the wrapper when you need the metadata. See Runs & run data for the envelope model.

Expressions in the config

None of this node’s properties are string-typed, so {{ }} expressions don’t apply here — JSON- and code-typed fields are always taken literally.

Build it with AI

Every node in this reference is reachable through Flowdrome’s AI Copilot and the MCP tools — say what you want, and the graph surgery happens server-side. Node types resolve fuzzily, so the catalog label (Error Trigger) works as well as the exact type id (error-handling.error).

In the Copilot panel (or any connected AI):

create a workflow that starts with error trigger and logs the result

As a step in a create_chain_workflow call:

{"type":"Error Trigger","config":{}}

curl -s -X POST http://localhost:48170/mcp -H "content-type: application/json" -d '{ "jsonrpc": "2.0", "id": "1", "method": "tools/call", "params": { "name": "add_node", "arguments": { "workflowId": "<id>", "type": "Error Trigger" } } }'

Example input & output

Captured from a real test run of the workflow above — this is what you see in the run data panel after pressing Test workflow. This particular run fails by design (see the note below).

The Error Trigger fires in the run's RECOVERY phase after another node failed; its output is the captured failure.

{
  "workflowId": "wf_b8458465e87c",
  "workflowName": "docs-example · error-handling.error",
  "runId": "run_715db2ae07f9",
  "failedNode": {
    "id": "boom",
    "type": "error-handling.stop-and-error",
    "name": "Failing step"
  },
  "error": {
    "code": "SMOKE_STOP",
    "message": "smoke recovery boom"
  },
  "startedAt": "2026-07-17T04:29:26.6569454+00:00",
  "failedAt": "2026-07-17T04:29:26.6606390+00:00"
}

{
  "workflowId": "wf_b8458465e87c",
  "workflowName": "docs-example · error-handling.error",
  "runId": "run_715db2ae07f9",
  "failedNode": {
    "id": "boom",
    "type": "error-handling.stop-and-error",
    "name": "Failing step"
  },
  "error": {
    "code": "SMOKE_STOP",
    "message": "smoke recovery boom"
  },
  "startedAt": "2026-07-17T04:29:26.6569454+00:00",
  "failedAt": "2026-07-17T04:29:26.6606390+00:00"
}

Property reference

Every setting, with its type and default — the same fields shown configured in the panel above.

Related nodes

The rest of the Error Handling group — the same folder you’d scan in the editor’s library.

• Try Wrap nodes in an error-handling boundary: catch any failure, retry, and route success/error.
• Stop and Error Unconditionally fails the flow with a configured error code and message — catchable by an enclosing Try, other

This page is generated from the node registry by gen-node-docs.mjs on every site build — ports, properties, defaults and visibility rules cannot drift from the code. The screenshots and example data are captured from a live Flowdrome by npm run shots:nodes and npm run gen:examples.