Skip to main content

Turn Messy Inbound Files Into Clean Data

Files TransformScript is a transformation language built into Files.com that reshapes data, normalizes partner formats, makes routing decisions, and applies AI — right inside your Automations and Webhooks, the moment a file lands. Stop building format-conversion pipelines on Lambda and Step Functions, or paying a separate tool to clean up files that are already in Files.com. The work happens where the files already are.

Start My Free TrialCompare Plans

Fix The Data Where It Arrives

Files.com sits right where files cross from a supplier, a partner, a subsidiary, or a system of record into your systems. That’s where the problems start: broken data, wrong formats, documents nobody can read cleanly, and files that show up late. The fix belongs right there, the moment a file lands, not in a tool three steps downstream.

The job is simple: read a file in one format, clean it up, reshape it, write it out in another format, and take the next step. TransformScript handles reading the file, parsing it, and writing the output, so you write the logic, not the plumbing. And it runs inside the same Automations that already move your files.

What You Do With It

Reshape, clean up, route, and apply AI to a file the moment it arrives, in the platform that already moves and governs your files.

Reshape Partner Formats

Convert a partner’s payload into the exact structure your next system expects — JSON, XML, EDI, and the other formats businesses trade in. One partner’s odd layout becomes your clean, canonical schema.

Normalize And Enrich Data

Put dates, currencies, and IDs into one standard form, look up a partner ID, and add the details the next step needs. A messy file becomes a clean, predictable record.

Make Routing Decisions

Decide where a file goes based on what’s actually inside it, not just its name — send one partner’s orders one way and another’s another way, in the same script.

Apply AI To Messy Inputs

Summarize content, pull fields out of unstructured files, sort documents by type, and fill in missing values — turning files that used to break a pipeline into clean data you can act on.

Two Ways AI Runs Inside It

AI either writes the transformation logic up front, or runs inside the workflow when the input is too messy for a fixed rule.

Design-Time AI Writes The Logic

Describe the transformation and AI generates the TransformScript for it. Once the script is generated and checked, every future run produces the same governed, deterministic output. AI speeds up the build; the workflow then runs reliably at scale.

Run-Time AI Handles The Mess

When the file itself is messy — a PDF, an email, a scanned doc, a spreadsheet that never looks the same twice — AI runs inside the workflow to pull out fields, sort the file by type, flag anomalies, and fix broken content. Instead of detecting a bad file and failing, the workflow detects it and recovers.

From File Received To Data Ready

TransformScript is the transform engine, but it rarely works alone. It pairs with file extraction, which reads field values out of structured files into metadata you can route and filter on, and with the broader extract, transform, and verify story that turns “file received” into “data ready” automatically.

The payoff is fewer custom pipelines, fewer downstream failures, faster partner onboarding, and less operational firefighting. See what each plan includes on the pricing page.

See Extract And Transform

TransformScript Questions

What teams ask about supported formats, the DataWeave connection, where scripts run, iPaaS scope, and how usage is billed.

Files TransformScript (FTS) is a transformation language built into Files.com that reshapes data, normalizes partner formats, makes routing decisions, and applies AI — right inside Automations and outbound Webhooks. It runs at the moment a file arrives, in the same platform that already moves your files, so you don’t build a separate format-conversion pipeline on Lambda, Step Functions, and EventBridge or pay a separate tool to do it.

TransformScript reads and writes JSON, NDJSON, CSV, XML, X12, EDIFACT, HL7 v2, and YAML. That covers the formats used across APIs, business documents, and regulated industries like healthcare and finance.

TransformScript is inspired by DataWeave, the transformation language MuleSoft made popular, adapted for Files.com’s file orchestration platform. Most transformation scripts written in DataWeave-style syntax work unmodified in Files.com. TransformScript is built and maintained by Files.com independently, and some language features behave differently, so treat it as DataWeave-compatible rather than identical.

TransformScript runs as a first-class step inside Automations and outbound Webhooks — not a separate engine you wire up. A file arriving via SFTP, an Inbox, or the API can fire an automation that transforms the file before routing it onward.

No. TransformScript handles the integration work that belongs at the file-intake layer — extract, normalize, transform, and route the moment a file lands. Downstream ETL like data-warehouse loading and multi-system orchestration still lives where it lives. The point is to stop building intake-layer glue in custom code, not to replace your whole integration stack.

TransformScript usage is metered as Transformation and AI Credits, included in a monthly allowance that scales by plan, with overage billed per million credits. Different operations — text transformation, GPG, document conversion, image and video work, and AI tokens — each have their own credit cost. See the pricing page for current allowances and rates.

Reshape Files The Moment They Arrive

Start a free trial and write a TransformScript step inside an Automation. Convert a partner’s format, normalize the fields, and route the result — without a separate pipeline to build or babysit.

Start My Free TrialCompare Plans

No credit card required • Free for 7 days • Live in minutes

Keep Exploring