Variables

Keep account-owned configuration separate from workflow definitions.

Variables are named JSON values owned by an account. A Flow stores a reference to the variable; the deployment resolves the value using the Flow owner’s identity.

Bind a variable

For nodes that support variable sources, bind it through the public input interface:

{
  "op": "input.set",
  "node": "NODE_REFERENCE",
  "input": "region",
  "source": { "kind": "variable", "name": "support_region" }
}

Create the variable in the same account that owns the Flow. Administrative access does not imply access to another account’s Variables.

Execution snapshots

The deployment fixes the resolved configuration for the accepted execution scope. Updating a Variable applies to later operations; it does not rewrite the inputs of an already accepted Run or an Agent continuation.

Variable values are separate from Revisions and ordinary public Run input events. Code can explicitly return, log, or send a value it receives, so check how downstream nodes use it.

Sharing a workflow

Workflow import and export remove structured Variable bindings. They do not scan code, prompts, or business JSON for embedded values. A literal token remains a literal token after export.

For external application credentials, use the relevant Connection or supported authentication binding instead of inserting secrets into Code text. See capabilities and permissions.