knoten / builtin / flow
Get Variable
Emit a previously-set run variable as the item itself
Dieser Inhalt ist noch nicht in deiner Sprache verfügbar.
Turn a value stored earlier in the run with Set Variable back into items for the next node.
What it does
Section titled “What it does”Get Variable reads a variable that a Set Variable node stored earlier in this run, and sends it out as the item itself. The incoming item is ignored.
- A list becomes one item per entry, so the next nodes handle each entry in turn.
- An object becomes the item as it is.
- Anything else (text, a number) is wrapped in a field named by Put Value In Field, for example
{ "value": 42 }.
If the variable was never set, the node fails with a clear message, unless you turn on Use A Fallback.
Most of the time you don’t need this node: {{ $run.name }} works in any field of any later node.
When to use it
Section titled “When to use it”- Feed a list you collected with Append to list into nodes that work on each item, such as an integration that creates one record per item.
- Hand a stored object to a node that reads its incoming item rather than a field.
- Read part of a stored value, such as
page.next, as its own item.
To use a variable inside a field, write {{ $run.name }} there instead.
Inputs and settings
Section titled “Inputs and settings”| Einstellung | Typ | Was es bewirkt |
|---|---|---|
| Name | Text | Name of the variable to read. |
| Path | Text | Optional dot path inside the value, for example page.next. |
| Use A Fallback | Toggle | Emit a fallback value instead of failing when the variable is not set. Standard: Off |
| Fallback | Value | Value emitted when the variable is not set. |
| Put Value In Field | Text | Field holding the value, when the value is not itself an object. Standard: value |
- Name is required in practice: the node fails without it. Type the name only,
results, not$run.results. - Path picks a part of the stored value with dots, for example
page.next. Leave it empty to emit the whole value.
Outputs
Section titled “Outputs”-
Output
The output is the stored value, shaped as described above. Text and numbers sit under the Put Value In Field name, so the next node reads them as {{ $input.value }}.
Dependencies and credentials
Section titled “Dependencies and credentials”None. This node needs no connection and has no slots for other nodes.
Example workflow
Section titled “Example workflow”Collect page titles in a loop, then save them all at once:
- Inside a Loop, Set Variable with Operation Append to list, Name
titles, Value{{ $input.title }}. - From the Loop’s Done port, Get Variable with Name
titlesand Put Value In Fieldtitle. It sends one item per collected title. - Google Sheets appends one row per item, with
{{ $input.title }}in a column.
Common issues
Section titled “Common issues”- “Variable “x” has not been set at this point in the run.“ The Set Variable node did not run before this one, often because it sits on a separate branch. Connect it upstream of Get Variable, or turn on Use A Fallback.
- “Path “x” does not exist inside variable “y”.“ The stored value has no such part. Check the spelling, or clear Path to see the whole value first.
- “A variable name is required.” Fill in Name.
- “Variables only exist while a workflow is running.” You ran the node on its own. Run the whole workflow.
Related nodes
Section titled “Related nodes”- Set Variable: store the value in the first place.
- Split Out: split a list field of an item into items.
- Data Store: read values saved by earlier runs.