Result

Routes by the LAST outcome on the envelope's result ledger — succeeded, failed, skipped, or canceled — so a flow can react to what just happened.

Finding it in the library

Search the builder's node library for Result (it lives under Logic). 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.

Wired up in the builder

Result 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.

How it’s configured

The node’s settings as the builder shows them — every field laid out with real values. In the Studio these are edited on the node: click the chevron on the divider under its ports to open them.

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

Ports

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

Result consumes the content of the incoming envelope — when it is fed directly by a trigger, the trigger’s wrapper is unwrapped at the node boundary so the node sees the actual data, not the metadata shell. Its output becomes the payload for the next node, while the envelope (trace ids, correlation, binary refs) rides along untouched. In the Runs view you always see the whole envelope for both sides of this node.

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 (Result) works as well as the exact type id (logic.result).

In the Copilot panel (or any connected AI):

add a result node after the trigger

As a step in a create_chain_workflow call:

{"type":"Result","config":{}}

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

Example input & output

Captured from a real test run of the workflow above — this is what the Runs view shows after pressing Test workflow.

On this run the node emitted on port succeeded.

Input — what the node received

Output — what the node produced

Property reference

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

Related nodes

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

• Filter / Condition Evaluates a condition against input and returns the pass/fail decision.
• IF Routes input to a true or false output based on a typed condition.
• Switch Routes input to one or more named outputs based on ordered conditions.
• Merge Combine the items of multiple inputs — append, combine by matching fields / position / all combinations, or ch
• Rate Limit Multi-tenant rate limiting: identifies the caller by a tenant GUID header, enforces per-second/minute/hour/day
• Loop Over Items Iterate a list: run the inside body once per batch of items, then emit everything on done.
• Thread Pool Queue-fed concurrency frame: consume from the input queue, run the inside body on a pool of threads, publish e
• Junction A point on a wire that flow can come back through: wire any node further down into its Return port and everyth

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.