What's new in the mapping wizard: friendlier to read, far more capable

The field-mapping wizard is the part of intake people fall in love with — so we kept sharpening it. This round had two goals: make every row readable by a businessperson, not just an engineer, and let it map the messy shapes real systems actually return. Here is what changed.

Names you can actually read

Every field now leads with a plain-English name. "First carrier terminal — city" sits front and center; the technical path (carrierTerminals[0].city) drops to a quiet second line for whoever needs it. We stripped the namespace noise and special characters out of those paths, and hovering any field explains in one sentence what it is — no DataWeave or JSONPath required to follow along.

One clean sample, not a wall of data

Each field shows a single example value right under its name, so you can see at a glance that "Amount" is a number and "Close date" is a date. Want to check a specific value? Open the row and type one into the test box. And you can now upload your own sample data — drop in a real record and the previews show your actual values instead of placeholders.

Transforms tucked away until you want them

The transform chips used to crowd every row. Now they live behind a per-row expand toggle, so the grid stays calm and scannable. Open a row to add rules, defaults, if/then conditions, constants, find-and-replace, or to combine fields (first + last into a full name) — all in plain language.

Built for real-world data shapes

Real records are rarely flat. The wizard now maps collections / line items (one-to-many — every order line, not just the header) and nested object sub-fields (address.city → shipping_city). Defaults are first-class, and a record-level filter lets you move only the records you mean to.

One-click AI fix — and undo

The Fix with AI button now actually walks the mapping, corrects the flagged issues — duplicates, type mismatches, unmapped fields — and shows an overlay of exactly what it changed, field by field. Changed your mind? Undo rolls back the last change in a click. And any field with a problem floats to the top of the list so you never go hunting for it.

Why it matters

The mapping is the hardest, most error-prone part of any integration. Making it readable means a businessperson can confirm it is right; making it handle collections and nested objects means it matches what your systems really send. Same two-minute, self-serve step — now clearer, and far harder to get wrong.

Try the mapping wizard — or tell us what to connect and we'll take it from there.