The Transform node modifies data between steps. Open the node and click Select Transform to choose from the catalog — each type has its own configuration fields.
Full reference: Transform Catalog lists every transform type, its fields, and when to use it.
Quick start
- Connect an upstream node (HTTP, Action, AI, etc.).
- Open the Transform node → Select Transform.
- Pick a type (e.g. Edit Fields, Filter, Sheet to Rows).
- Fill in the fields shown for that type.
- Run the workflow and check Execution Data to verify the output shape.
Common transforms
| Transform | Use when |
|---|---|
| Edit Fields (Set) | Rename or add fields with a key-value list |
| Filter | Keep rows matching a condition |
| Sheet to Rows | Turn Google Sheets grid data into one object per row |
| Code | Short JavaScript expression on the input |
| AI Transform | Describe changes in plain English |
| Parse JSON | (via Code or downstream use) — when AI returns JSON as a string |
Code transform vs Function node
Both can run JavaScript, but they fit different jobs:
| Transform → Code | Function | |
|---|---|---|
| Purpose | Transform the previous node's output | General logic, branching prep, multi-step computation |
| Editor | Inline code field in the transform panel | Full editor with expand mode |
| Return | Must return transformed data | Must return any output shape |
| Best for | filter, map, quick reshapes | Complex pipelines, loops, custom state |
Use Edit Fields for simple renames — it's faster than code.
Sheet and email sequences
For Google Sheets + Gmail outreach without writing Function code:
| Step | Transform |
|---|---|
| Parse sheet | Sheet to Rows |
| Who is due today | Filter Sequence Due |
| Loop body | Scan Sequence Contact |
| After each send | Patch Sequence Scan (+ Restart from node) |
| Before follow-up | Check Thread Reply |
These use workflow variables contactList, scanIndex, sentEmails, and emailSequence. Configuration is mostly automatic — pick Contact list from in the scan/patch transforms. Details in the Transform Catalog.
Chaining transforms
HTTP Request → Transform (Sheet to Rows) → Transform (Filter) → Action
Split complex reshaping into multiple Transform nodes instead of one large Code block.
Restart from node
Patch Sequence Scan and some Function steps support Restart from node — after the step completes, execution jumps back to an earlier node (e.g. the scan loop) without a canvas back-edge. Enable it in the node panel below the transform config. See Execution.
Tips
- Inspect Execution Data after each transform — especially after Sheet to Rows and Filter.
- Use the Variables button on fields instead of typing
{{context...}}paths by hand. - When an AI node returns JSON as a string, add Code or Edit Fields to parse before Actions.
- Browse the full list: Transform Catalog.