Control flow, variables and parameters
Variables, run-time parameters, secrets, branching, loops, retries.
workbooksvariablesparametersbranchretry
Control flow, variables and parameters
Variables
Every node output is referenceable as {{nodeOrField}}. Use them to chain steps — e.g. extract orderId from an API response and use it in a DB query.
API Test: Extract orderId = body.id
DB Collector: SELECT status FROM orders WHERE id = {{orderId}}Run-time parameters
Define parameters so one Workbook runs against many targets/environments. Pass them from the UI, the API, or CI:
POST /api/workflow-executions/run
{ "workflowId": 45, "parameters": { "baseUrl": "https://staging.example.com" } }
# inside the workbook, reference {{baseUrl}}Secrets
Store credentials as secrets and reference them like variables — they are never printed in logs or outputs.
Branching and loops
- Branch on any condition to take remediation only when needed.
- For Each to fan a check across a list (regions, tenants, endpoints).
- Approval to require a human before an irreversible action.
Retries and error handling
Each node has a retry policy (count + delay) that applies only to transient errors — never to a semantic failure like a missed assertion (retrying that is pointless). This keeps flaky-network noise out of your results.