Node reference

Every built-in node, grouped by category. Reference a node by its class constant (LogNode::type()) in code, or by its type string in a stored definition.

Category	Nodes
Logic	Condition, Switch, For each (loop)
Actions	Log, HTTP request, Wait, Call workflow, Set output, Stop, Scope, Do nothing
Variables	Set, Get, Increment, Append, Remove
Collections	Filter, Map, Reduce, Sort, Contains, Count
Data	Parse JSON, Stringify JSON, Select, Merge, Flatten
Text	Concat, Format, Replace, Split, Trim, Uppercase, Lowercase
Math	Add, Subtract, Multiply, Divide, Round, Min, Max
Date & time	Now, Add, Subtract, Difference, Format
Files	Read, Write, Delete
Model	Create, Update, Delete, List records

How to read these pages

Each node lists:

• Type — the string returned by Type::type().
• Config — the fields in the node's config. String values support {{ expressions }} unless noted. Fields marked when only apply when another field has a given value.
• Output — the shape written to {{ nodes.<id>.* }}. Most compute nodes put their result under a result key.
• Branches — for branching nodes, the outgoing branch names.

Configuring nodes

In a stored definition, config is a flat map:

['id' => 'notify', 'type' => LogNode::type(), 'config' => [
    'level'   => 'warning',
    'message' => 'Low stock on {{ nodes.check.result }}',
]]

Fields not set fall back to the defaults listed on each node's page. A field's default in the schema seeds the interactive builder's prompt; a node's handle() applies its own fallback when a key is absent at run time.