This node is in preview. Its behavior may change in future releases.
When to use transform
- You need the output in a specific format: CSV for a data warehouse, Excel for a finance team, XML for a legacy integration. Use Format mode.
- The downstream system expects a different field shape than extract produced. Use Schema transform mode to remap names and nesting.
- You need to compute derived values (totals, normalized currencies, days overdue) that shouldn’t have come from the AI. Use Script mode to do the math deterministically.
- Skip transform when the extract output already matches the downstream schema. A pass-through transform adds runtime without value.
Mode
Select the top-level Mode to switch between transform behaviors:Configuration
Format mode
Schema transform mode
Use
> as the separator for nested field paths. For example, invoice > total refers to the total property inside the invoice object. The editor validates field references against the upstream node’s output schema and provides autocomplete suggestions as you type.
You can use template expressions inside mapping values to concatenate fields, apply transformations, or insert literal text.
Script mode
The script runs in an isolated environment. Each upstream node is exposed as a JS global with the same shape as
{{nodeName}} in templates (success, payload, metadata, error). Return a value from the script to pass it to the next node.
Inputs and outputs
Allowed inputs: Extract, merge, HTTP, loop, variable, store, prompt. Output: Data converted, mapped, or transformed according to the configured mode.Related
Extract action
Extract structured data before transforming
Callback output
Deliver transformed data via webhook
Email output
Send transformed data via email
Review action
Review data before transforming