Variables, extraction and secrets

Variables, extraction and secrets (deep dive)

Referencing outputs

Any node output is referenceable as {{name}}. Outputs are merged into one shared context as the run progresses, so a value an early node produced is available everywhere after it.

API Test:      Extract  orderId = body.id        -> {{orderId}}
DB Collector:  SELECT status FROM orders WHERE id = {{orderId}}
Assertion:     {{firstRow.status}} EQUALS 'confirmed'

Dot-paths into structured outputs

When an output is an object/array (a captured JSON response, a DB row), reach into it with a dot/array path: {{body.items.0.sku}}, {{firstRow.status}}, {{tokenUsage.total_tokens}}.

Variable extraction config

Every node has a Variable Extraction panel: name a variable and bind it to a path in that node's output, so you control exactly what flows downstream (and keep names stable).

Run-time parameters

Define parameters so one Workbook runs against many targets/environments. Pass them from the UI, the API, or CI; reference them as {{param}}.

POST /api/workflow-executions/run
{ "workflowId": 45, "triggeredBy": "ci",
  "parameters": { "baseUrl": "https://staging.example.com", "region": "eu" } }
// inside the workbook: {{baseUrl}} / {{region}}

Secrets

Store credentials as secrets and reference them like variables ({{DB_PASSWORD}}). Secrets are redacted — never printed in logs, outputs or the run report.

System variables (always available)

Variable	Is
{{_executionId}}	This run's id.
{{_workflowId}}	The workbook's id.
{{_nodeId}} / {{_nodeName}}	The current node.
{{_orgId}}	Your organization's id (rarely needed — useful when a workbook calls VerOps APIs).