Best Practices for Managing Variables

A few conventions keep variables readable as an application grows, and prevent the changes that quietly break a running workflow.

Organize with groups

Grouping related variables makes the list easier to navigate, especially in complex workflows. Finding database credentials among dozens of unrelated variables is slow and error-prone; groups prevent that.

Use clear naming conventions

Descriptive names like orderStatus or isUserActive convey a variable's purpose immediately and reduce errors in workflow logic. Avoid vague names like var1 or flag.

Validate before deletion

Deleting a variable that a workflow still uses breaks that workflow. Check what reads a variable first — deleting an emailAddress variable, for example, can cause a customer notification workflow to fail.

Set default values

A default value ensures a variable has a defined state even when no explicit value is assigned during execution. This prevents errors when a workflow expects a value that turns out to be null or undefined. A retryCount variable might default to 3.

Use export and import to replicate configurations

Exporting a group and importing it elsewhere saves re-entering values when replicating variables across environments, and doubles as a backup. You might export a group of CRM connection variables to import into another environment.

Review imported values before relying on them — a file exported from one environment carries that environment's values.

Next steps

See Creating and Updating Variables and Variable Groups to apply these conventions.