{ success, output?, data?, error? }. output is a string that downstream templates can use. data carries structured values.
input
Exposes the run input.output is the input as JSON, and data is the input object. Templates can read the input directly as {{input.field}}, so this node is optional.
prompt
llm
One chat call through a named provider. There is no loop and no tool use.System prompt from a built-in preset.
system wins if both are set.decision
A typed decision. See decisions.Choices for
choice, ordered levels (at least two) for score. A single {{path}} pulls a list from the run input.http
A generic HTTP call.url, headers and body are templated. A response outside 200-299 fails the node.
The result’s data is { status, body }, where body is parsed JSON when possible.
mcp
Calls a tool on another MCP server. See MCP.output is the tool’s text. data is its structured content, or the text parsed as JSON. A tool error fails the node.
output
Marks the flow result.data is the upstream node’s data, or a map by node id when several nodes are live. The run result exposes this node’s result as output.
Add your own node
Register a node type on aRegistry. Nothing else changes.