The Variable by UnifyApps node lets you create runtime variables within an automation to store and reuse data in further nodes.
Overview
The Variable by UnifyApps node lets you create runtime variables within an automation to store and reuse data in further nodes. Variable values exist only during a single execution and can be dynamically updated for each run.
Supported data types: String, Integer, Number, Boolean, Date, Object, Array, Single Select Dropdown, Multi Select Dropdown.
Actions Supported
Action | Description |
|---|---|
Create Variables | Create typed variables |
Create List | Create a list and specify the schema for list items |
Update Variables | Update the value of existing variables |
Add Item to List | Appends a new item to an existing list |
Add Items to List | Appends multiple items to an existing list |
Find and update variables with names | Update values of variables matching a provided name |
Remove all items from list | Removes all entries in an existing list |
Use Cases
A practical example involves bucketizing Zendesk tickets by priority and notifying via Slack about high and low priority tickets. This involves:
Creating a variable list ticketStatus to store ticket IDs based on priority.
Running a "For each item in the list" action to check priority.
Adding items to the list where priority equals "High."
Create Variables
This action creates variables to transiently store and re-use information within an automation run.
Variable creation interface
Input Fields:
Field Name — Unique ID for the variable
Label — Name of the variable
Field Type — Data type of the variable
Exclude field in runs — Omits sensitive information from run logs
Description — Brief variable description
Use "Add field" to create multiple variables, or click the bin icon / "Clear All" to delete variables.
Create List
This action creates a list to store multiple data points in a specific format. The list schema must be defined to map data in subsequent nodes.
Input Fields: List Name; Create List of (Object, String, Integer, Number, Boolean); List Schema; Setup using JSON.
When you have a predefined JSON Schema, select "Setup using JSON" to enter it directly. The schema is appended within the List's output data pill.
Update Variables
This action updates existing variables created with "Create Variables." Variables must already exist before this action can be used.
Input Fields: Select variable(s) to update; new value for each selected variable.
Note: This action does not generate a data pill. Use the variable data pill from the Create Variables node instead.
Add Item to List
Inserts a new record into an existing list. Input Fields: List name; Insert location (position for the new entry); List item fields (values for the new entry).
Note: This action does not generate a data pill.
Add Items to List
Adds multiple records to an existing list simultaneously. Input Fields: List name; Insert location; List item source (source array for data mapping); List item fields.
Note: This action does not generate a data pill.
Find and Update Variables
Updates the value of variables matching the provided name. The first variable found receives the new value. Input Fields: Variable List source; Item source; Item value.
Note: This action does not generate a data pill.
Remove All Items from List
Removes all items from an existing list. Should be used after Create List. Input Fields: List Name (name of the list to clear).
FAQ
Can Variables be used to set up custom logic-based checks? Yes — store values, compare them, and control workflow behavior or validate data entry.
What is the difference between "Add Item to List" and "Add Items to List"? "Add Item to List" adds a single item at a time; "Add Items to List" enables bulk addition of multiple items.
Can I update variables after they're created? Yes — use the "Update Variables" action to modify variable values dynamically during execution.
When should I use variables instead of objects? Variables are ideal for temporary, workflow-specific information that exists only during a single execution cycle. Unlike objects designed for permanent storage, variables suit transient data relevant only within the current workflow.
Notes
Keep the following in mind when using Variable by UnifyApps:
Variable values persist only for the duration of the current run; they reset on each new execution and cannot carry state between runs.
Initialize all variables at the start of the automation before any branching logic reads them; reading an uninitialized variable returns null.
Use Create List and Add Item to List to build result collections inside a loop, then reference the completed list after the loop ends.
Find and Update Variables requires an exact match on the variable name; check spelling and casing to avoid creating a new variable instead of updating the existing one.
Check the FAQ section for type-specific edge cases, such as what happens when you add an item to a variable that was not originally created as a list.