Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.docpipe.ai/llms.txt

Use this file to discover all available pages before exploring further.

The Variable action node assigns one or more named values from template expressions. Each entry becomes a field on the node’s payload that downstream nodes can reference as {{varNode.payload.varName}}.

​
When to use Variable

  • You want to name a derived value once and reuse it in multiple downstream nodes (e.g., a normalized customer email or an amount threshold).
  • You need a constant that several branches depend on, so you can edit it in one place.
  • A Transform script or a Condition edge needs a value that is easier to read with a short name than as a long path expression.
For one-off math or reshape work, use Transform. For per-item iteration, use Loop.

​
Configuration

FieldTypeRequiredDescription
VariableslistYesOne or more name/expression pairs
Each row has two fields:
  • Name: the field name on the variable node’s payload. Use a JS-style identifier (customerEmail, amountLimit).
  • Expression: a template expression like {{extract.payload.email}}, {{today | addDays: 30 | formatDate: 'yyyy-MM-dd'}}, or a literal string.

​
Output

The node’s payload is an object with one key per variable assignment. 
{
  "customerEmail": "alice@example.com",
  "amountLimit": 5000
}
Reference downstream as:
  • {{vars.payload.customerEmail}} from a template field
  • vars.payload.amountLimit from a Transform script
(vars here is the node name; pick whatever name the variable node has in your pipeline.)

​
Inputs and outputs

Allowed inputs: Any upstream node. Output: A flat object whose keys are the configured variable names.

​
Credits

Variable nodes are free. They consume 0 credits per execution.

Expressions and filters

Template syntax for variable expressions

Transform

Use named variables inside a transform script

Conditional routing

Branch on a variable’s value