Workflow Variables

Variables in Sim act as a global store for data that can be accessed and modified by any block in your workflow, allowing you to store and share data across your workflow with global variables. They provide a powerful way to share information between different parts of your workflow, maintain state, and create more dynamic applications.

Variables allow you to store and share data across your entire workflow, making it easy to maintain state and create complex, interconnected systems.

Overview

The Variables feature serves as a central data store for your workflow, enabling you to:

Store global data: Create variables that persist throughout workflow execution

Share information between blocks: Access the same data from any block in your workflow

Maintain workflow state: Keep track of important values as your workflow runs

Create dynamic workflows: Build more flexible systems that can adapt based on stored values

Creating Variables

To open the Variables panel, click ⋯ → Variables in the top-right of the workflow editor.

Opening the Variables panel from the toolbar menu

Each variable has:

  • Name: A unique identifier used to reference the variable
  • Type: The data type (Plain, Number, Boolean, Object, Array)
  • Value: The data stored in the variable
Variables panel with a number variable

Accessing Variables

Variables can be accessed from any block in your workflow using the variable dropdown. Simply:

  1. Type < in any text field within a block
  2. Browse the dropdown menu to select from available variables
  3. Select the variable you want to use

You can also drag the connection tag into a field to open the variable dropdown and access available variables.

Variable Types

Variables in Sim can store various types of data:

"Hello, World!"

Plain variables store strings of characters. They're useful for storing messages, names, and other text data.

42

Number variables store numeric values that can be used in calculations or comparisons.

true

Boolean variables store true/false values, perfect for flags and condition checks.

{
  "name": "John",
  "age": 30,
  "city": "New York"
}

Object variables store structured data with properties and values.

[1, 2, 3, "four", "five"]

Array variables store ordered collections of items.

Using Variables in Blocks

When you access a variable from a block, you can:

  • Read its value: Use the variable's current value in your block's logic
  • Modify it: Update the variable's value based on your block's processing
  • Use it in expressions: Include variables in expressions and calculations

Variable Scope

Variables in Sim have global scope, meaning:

  • They are accessible from any block in your workflow
  • Changes to variables persist throughout workflow execution
  • Variables start fresh from their defined values on each run. Changes during execution are visible within that run only

Best Practices

  • Use Descriptive Names: Choose variable names that clearly indicate what the variable represents. For example, use userPreferences instead of up.
  • Document Your Variables: Add descriptions to your variables to help other team members understand their purpose and usage.
  • Consider Variable Scope: Remember that variables are global and can be modified by any block. Design your workflow with this in mind to prevent unexpected behavior.
  • Initialize Variables Early: Set up and initialize your variables at the beginning of your workflow to ensure they're available when needed.
  • Handle Missing Variables: Always consider the case where a variable might not yet exist or might have an unexpected value. Add appropriate validation in your blocks.
  • Limit Variable Count: Keep the number of variables manageable. Too many variables can make your workflow difficult to understand and maintain.

Common Questions

Workflow variables are defined per workflow and store data like text, numbers, objects, or arrays that blocks can read and modify during execution. They are referenced with <variable.name> syntax. Environment variables (secrets) are workspace-level credentials referenced with {{KEY}} syntax, designed for sensitive values like API keys that should never appear in logs.
The execution engine uses a chain of resolvers that run in order: loop variables, parallel variables, workflow variables, environment variables, and then block references. When a block input contains a variable reference, the resolver matches it by normalized name (case-insensitive, spaces removed) or exact ID, then substitutes the resolved value before the block runs.
Yes. If your variable stores an object or array, you can use dot notation to access nested properties. For example, <variable.config.retryCount> will navigate into the config object and return the retryCount value.
Variables maintain their initial values as defined in the Variables panel. Each execution starts with those configured values. If a block modifies a variable during execution, that change is visible to subsequent blocks in the same run, but does not alter the saved initial value for future runs.
If the resolver cannot find a matching variable, the raw reference string is left in place without substitution. This typically causes downstream blocks to receive unexpected input, so make sure all referenced variables are defined before running the workflow.
Yes. Variables support text, numbers, booleans, JSON objects, and arrays. When the value is parsed for execution, the engine determines the type and resolves it accordingly, so downstream blocks receive the proper JavaScript object or array rather than a raw string.
PreviousVariables
NextIntegrations

On this page

Overview
Creating Variables
Accessing Variables
Variable Types
Using Variables in Blocks
Variable Scope
Best Practices