Token system
The token system lets you reference data from triggers, previous nodes, variables, site info, and execution context inside node configuration fields. Tokens are resolved at execution time using {{ }} syntax.
Token syntax
{{ expression }}— resolve a token path{{ node_id.field }}— access a specific node's output{{ trigger.data.order_id }}— access trigger payload data{{ variable.my_var }}— read a flow-scoped variable{{ site.title }}— read site info
Token catalog
| Namespace | Prefix | Example | Description |
|---|---|---|---|
| Trigger | trigger.data.* | {{trigger.data.order_total}} | Payload from the workflow trigger |
| Event | event.* | {{event.total}} | Trigger event metadata |
| Node output | node_id.* | {{ai_gen_1.content}} | Output from a specific node by ID |
| Variables | variable.* | {{variable.customer_email}} | Flow-scoped variable |
| Site | site.* | {{site.name}}, {{site.url}}, {{site.admin_email}} | WordPress site info |
| Execution | execution.* | {{execution.id}}, {{execution.started_at}} | Current execution metadata |
| Workflow | workflow.* | {{workflow.id}}, {{workflow.name}} | Current workflow metadata |
| Error | error.* | {{error.message}}, {{error.node_id}} | Error context in catch branches |
| Approval | approval.* | {{approval.decision}}, {{approval.by_user}} | Approval gate result |
| Loop | loop.* | {{loop.item}}, {{loop.index}}, {{loop.total}} | Current iteration context |
Type preservation
When a configuration field contains a single token expression (and nothing else), the resolved value keeps its original JSON type. Example:
{{trigger.data.amount}} → 150.00 (number, not string)When mixed with literal text, everything becomes a string:
Total: {{trigger.data.amount}} EUR → "Total: 150.00 EUR" (string)Autocomplete in the editor
The visual editor provides autocomplete for tokens. After typing {{, a dropdown shows available token paths filtered by what you type. The autocomplete understands:
- Which nodes are connected upstream of the current node
- The output schema of each upstream node
- All system tokens (
site.,execution.,workflow.*) - All declared flow variables
Token references in node config
Any configuration field that accepts a token is marked with a {{ }} icon in the node inspector. Fields that accept tokens include:
- Condition values (left/right operands)
- Email to/subject/body fields
- HTTP request URL, headers, body
- Delay duration values
- Loop item source arrays
- Text compose templates