Apply a saved transform template to whatever file entered the workflow, so every run reshapes data the same way-no manual cleanup step required.
The Transform Template node sits between a data source and an export or sync step. It doesn't build a new transformation from scratch-it applies a template you've already saved in the transformation workspace to whatever file the workflow passes in. That keeps the workflow itself simple: one node, one saved recipe, applied consistently every time the workflow runs.
The node lives in its own Transform section of the Node Palette, right below Data Sources.
Node Palette
Drag a node onto the canvas (or click to add)
Transform
Transform Template
Apply a saved transform template to the selected file
Typical position in a workflow chain
The node applies whichever template you point it at from your Template Manager-it doesn't build one for you.
If no template matches the incoming file's column structure, the run will fail at this step-check Execution History for details on what didn't map.
Once the template runs, its output is a transformed file ready to hand off to a sync, export, or utility node.
A Transform Template node can feed more than one downstream node-branch its output to sync to Odoo and export to Google Drive at the same time.
A Transform Template node always references the live version of the template-not a snapshot from when you added it.
If a template isn't applying the way you expect, or a workflow node shows as unconfigured, our support team is here to help.
Contact Support