Skip to main content
Data flow in Quixa is driven by a flexible expression engine that passes parameters, authentication credentials, and response payloads seamlessly down the execution graph.

1. Mustache Binding Syntax

Reference any predecessor node output using double-curly syntax:

Common Binding Patterns:

  • JSON Body Values: {{CreateUser.response.body.id}}
  • Nested Object Arrays: {{GetOrders.response.body.items[0].sku}}
  • Response Headers: {{Login.response.headers.x-auth-token}}
  • HTTP Status Code: {{PaymentStep.statusCode}}
  • Round-trip Latency: {{SearchApi.responseTimeMs}}
When editing URLs, Headers, or JSON Bodies, typing {{ opens the IntelliSense Autocomplete Picker, displaying all available upstream outputs with live schema previews.

2. Built-in Dynamic Generators

Inject synthetic data and dynamic timestamps directly into your payloads without writing code:

3. Scoped Variables

  • Environment Variables: {{env.BASE_URL}}, {{env.API_SECRET}} — scoped to active deployment environments (Dev, Staging, Prod).
  • Flow Variables: {{flowVars.batchId}} — centralized key-values defined at the root of the workflow.
  • Loop Context: {{forNode.item}}, {{forNode.index}} — dynamically populated during iteration cycles.

4. Script Nodes (JavaScript Transformations)

When complex transformations, hash calculations, or custom data restructuring is required, place a Script Node:
Outputs returned from a Script Node are immediately available to subsequent nodes via {{MyScript.response.body.totalAmount}}.