Configure Globals

Globals are configuration values loaded at the start of a run. Read them with {{global.name}}.

Choose a scope#

Workspace Globals supply settings shared by workflows in that workspace. A workflow can also contain its own Globals. If the same name appears in both, the workflow value takes precedence for that run.

For example, set a workflow Global named minimumBalance to a number, then use {{global.minimumBalance}} in an If condition. The graph stays readable and the threshold is easy to change.

Match the expected type#

Keep numbers as numbers and lists as arrays when the downstream node expects those types. Use a complete expression to preserve the type. Text containing an expression produces a string.

Globals are a snapshot of configuration for a run. Use a Variable node for values produced during that run, and State for memory written by a run and read later.

Prepare configuration for sharing#

Workflow Globals travel with the exported workflow. Workspace Globals do not become part of that portable definition automatically. A workflow that depends on a workspace value therefore needs setup instructions or a workflow value supplied by its reader.

Do not store API tokens, private keys, passwords, or other private material in Globals. They are ordinary workflow data. Use connections or the wallet vault, and review all literal values before sharing a file.

The iterate a checklist example uses an array Global to show how configuration can drive several executions.