Overview
Inline Transformations allow you to modify or derive values directly inside workflow fields, without adding extra steps or using a Code Runner.
They provide a safe, readable way to transform step responses and variables right where the value is used, keeping workflows concise and easy to understand.
Why Inline Transformations?
To avoid the usage of Code Runners for even small changes such as trimming text or converting a string to uppercase letters.
Inline transformations solve this by enabling:
- Fewer workflow steps
- Reduced dependency on Code Runners
- Faster workflow creation
- Cleaner, more readable workflows
How Inline Transformations Work
Transformations are written inside {{ }} using a dot-based function syntax like toUpper()
Syntax Rules
- Dots without () → Data access
{{ 1.response.email }}- Dots with () → Transformation or operation
{{ 1.response.email.toUpper() }}
Transformation functions are applied to the respective field values. You can refer to the list of supported functions to transform your data.
Examples
Basic Transformations
{{ 1.response.email.toUpper() }}
{{ 2.response.users.0.name.trim() }}
Working with Variables
{{ variables.counter.add(5).increment() }}
{{ variables.settings.merge({"theme":"dark"}) }}
Navigate to below page for more examples.
Error Handling & Fallbacks
Inline transformations are designed to fail safely.
When an Error Occurs
- A non-blocking warning is logged
- The workflow continues execution
- No data is mutated
Using Fallback Values
You can define fallback values if a transformation fails:
{{ 2.response.count.add(10).increment().fallback(0) }}
{{ 3.response.items.5.fallback("N/A") }}
Security & Safety
Inline transformations are secure by design:
- Only approved, type-safe functions are allowed
- No eval, no runtime access, no system calls
- Transformations are strictly read-only