Global Context

Global Context is a persistent key-value store scoped to each workspace. It allows you to store configuration values, counters, API endpoints, and other data that workflows can read and write at runtime.

Setting Values

Via Settings UI

1. Navigate to Settings > Global Context.
2. Click Add Entry.
3. Enter a key name and value.
4. Optionally mark the entry as a secret.
5. Save.

Via Workflow Transforms

Workflows can set global context values during execution using transform actions. This is useful for storing computed results, incrementing counters, or caching data between runs.

Accessing Values in Workflows

Use the template syntax to reference global context values in any node field:

{{global.key}}

For example, if you have a global context entry with key api_base_url and value https://api.example.com, you can use it in an HTTP Action node URL field:

{{global.api_base_url}}/v1/data

Secrets

Entries marked as secrets have their keys prefixed with __secret. Secret values are hidden in the Settings UI after saving, showing only a masked placeholder. This is intended for sensitive configuration such as API tokens or credentials that should not be casually visible.

Secret values are still accessible to workflows at runtime via {{global.__secret_keyname}} and are resolved in plain text during execution.

Workspace Scoping

Global Context entries are scoped to the workspace they are created in. Each workspace has its own independent set of key-value pairs. Switching workspaces changes which entries are visible and accessible.

Common Use Cases

• API endpoints: Store base URLs so workflows can reference them without hardcoding.
• Configuration values: Feature flags, thresholds, or environment-specific settings.
• Counters: Track how many times a workflow has run or how many items have been processed.
• Shared state: Pass data between separate workflow executions within the same workspace.