Custom file transforms

Custom file transforms let you write and maintain your own code to transform input files or lists. Unlike the AI agent transforms, nothing is generated for you — you own the logic from the start, which gives you full control over deterministic, repeatable behavior.

Availability: GA

What it does

• Input: files or lists.
• Output: one or more files, produced by the code you write.
• The code you write receives the input files or lists and returns transformed output files. You control parsing, restructuring, and formatting.

When to use it

• Your transformation logic is too specific or complex for built-in or AI-driven transforms.
• You need deterministic, version-controlled behavior rather than AI-generated code that might change between runs.
• You have engineering resources available to write and maintain the transformation code.

How to configure it

Add a Custom file transforms node after the node that produces the files or lists you want to transform, then write your code in the settings panel.

Settings

Example

Input

A batch of XML files exported from a legacy system.

Output

One JSON file per XML file, with fields restructured to match your internal schema, produced by your custom parsing code.

Troubleshooting

Code throws an error

• Check the run logs for the stack trace and line number.
• Confirm the code handles edge cases like empty files or missing fields.

Output is missing or in the wrong shape

• Verify your code returns the output type the downstream node expects (file vs. list).
• Add explicit logging in your code to inspect intermediate values during a test run.

See also

• File transforms agent
• Custom SQL transforms
• Sheet transforms