Global Context

Global variables are a key-value store scoped to each workspace. Use them for configuration values that workflows reference at runtime - API base URLs, identifiers, tokens - without hardcoding them into node fields.

Managing Variables

1. Open the workspace's settings (/workspaces/<workspace>/settings).
2. Go to the Globals tab.
3. Click Add, enter a key and a value.
4. Optionally mark the variable as Secret.
5. Save.

Values can be plain strings or JSON (objects and arrays are preserved as structured data).

Accessing Values in Workflows

Use the template syntax to reference a global variable in any node field:

{{global.key}}

For example, with a variable api_base_url = https://api.example.com, an HTTP Action node URL field can use:

{{global.api_base_url}}/v1/data

Deleting a variable breaks any workflow that still references it, so the delete confirmation warns you which key you are removing.

Secrets

Variables marked as Secret are masked in the UI and in execution logs - after saving, only a placeholder is shown. Use this for API tokens and credentials that should not be casually visible.

Secret variables are referenced exactly like regular ones - {{global.key}} - and resolve to their real value during execution.

Workspace Scoping

Global variables belong to the workspace they are created in. Each workspace has its own independent set of key-value pairs; workflows only see the variables of their own workspace.

Common Use Cases

• API endpoints: store base URLs so workflows can reference them without hardcoding.
• Credentials: tokens or keys used by HTTP Action nodes (mark them as Secret).
• Configuration values: feature flags, thresholds, or environment-specific settings shared by all workflows in a workspace.