Transform step

​

What it does

• Evaluates the expression in each field against ctx
• Type-casts each value to the field’s declared type
• Records the resulting object under the step’s name
• Continues to the next step (it does not set the workflow’s return value)

​

Transform vs Output

​

Fields

• Name — the key on the produced object
• Type — string, number, boolean, array, or object
• Value — a literal or expression resolved against ctx

​

What lands in ctx

{
  "n5": {
    "customer_name": "Alice Chen",
    "tier": "gold",
    "is_vip": true
  }
}

{{ n5.customer_name }}
{{ n5.is_vip }}

​

When to use it

• Reshape and rename — turn a verbose API response into a small, clearly-named object for the rest of the workflow.
• Consolidate — combine fields from several upstream steps into one payload you reference in one place.
• Normalize types — coerce a stringy value into a real number or boolean before a Condition step.

​

Example: clean up an API response

{
  "name":  { "value": "{{ n4.body.first_name & ' ' & n4.body.last_name }}", "type": "string" },
  "tier":  { "value": "{{ n4.body.subscription.tier }}", "type": "string" },
  "is_vip":{ "value": "{{ n4.body.subscription.tier = 'gold' }}", "type": "boolean" }
}

​

Considerations

• Pure expressions preserve types. {{ n4.body.balance }} in a number field stays a number. A number field whose expression resolves to non-numeric text will fail the type-cast — keep the declared type and the value in sync.
• It doesn’t terminate. Remember to connect a Transform to a following step; on its own it produces data but returns nothing to the caller.