Skip to main content
In enterprise API workflows, hardcoded static payloads lead to brittle, flaky tests and high maintenance overhead. Quixa eliminates this problem through its unified Dynamic Token & Interpolation Engine. When configuring any node’s Body, Headers, Query Parameters, or URL Path, clicking the + button or typing {{ opens the token selection popover with four core sources:

​
1. Response Binding (Inter-Node Plumbing)

Response Binding dynamically extracts data from the response of any preceding node in the flow and pipes it into downstream request URLs, headers, or payloads.

​
Syntax

​
Supported Sections

  • Body Fields: {{ResponseBinding.createUser.body.data.id}}
  • Headers: {{ResponseBinding.authService.headers['x-correlation-id']}} or {{ResponseBinding.authService.headers.Authorization}}
  • Status Code: {{ResponseBinding.paymentGateway.statusCode}}
  • Array Indexing: {{ResponseBinding.listAccounts.body.items[0].accountNumber}}

​
Example Workflow

  1. Node 1 (CreateCustomer): Dispatches POST /api/v1/customers →\to Returns { "customerId": "cust_98214" }.
  2. Node 2 (OpenAccount): Dispatches POST /api/v1/accounts with payload:
  3. At runtime, Quixa automatically resolves the token into "cust_98214".

​
2. QMock Engine (Synthetic Data Generation)

The QMock Engine provides built-in, on-demand synthetic mock data generation powered by standard faker algorithms. Every execution generates fresh, realistic data at runtime.

​
Common Categories & Fields

​
Critical Rule: Type-Aware Interpolation

JSON requires strict type fidelity. Quixa’s serializer uses Type-Aware Interpolation to preserve raw numbers, booleans, and objects versus strings:
Resolved JSON Output:
Result: Values remain raw integer and boolean data types without quotes.

​
3. QPlugin Tokens (Custom Algorithmic Generators)

When workflows require specialized algorithmic formats (e.g., checksum algorithms, government tax identifiers, or token signers), teams publish extensions to the Plugin Store.

​
Syntax

​
Examples

  • {{QPlugin.tax-id-generator}}: Produces algorithmically valid registration numbers.
  • {{QPlugin.hmac-signer}}: Computes dynamic HMAC-SHA256 request signatures based on payload contents.
  • {{QPlugin.iban-validator}}: Generates checksum-compliant International Bank Account Numbers.

​
4. Hierarchical Variables (Variables)

Quixa supports a 3-tier variable hierarchy to configure and parameterize workflows across environments:

​
1. Environment Variables ({{env.<key>}})

  • Configured centrally under the Environments manager.
  • Provides environment-specific values such as {{env.baseUrl}}, {{env.apiGatewayKey}}, or {{env.channelCode}}.
  • Switching the active environment dropdown (e.g. from Dev to Staging) immediately remaps all references across the canvas.

​
2. Flow Variables ({{flow.<key>}})

  • Defined at the flow settings level.
  • Holds workflow defaults such as {{flow.retryCount}} or {{flow.defaultCurrency}}.

​
3. Variable Extracts (Response Extractions)

  • Configured in any node’s Variables tab.
  • Saves dynamic values extracted from responses directly into flow-scoped variables for subsequent node consumption.