Make the Data Better on the Way Through

Why this matters

Moving data from A to B is the beginner's view of automation; the professional's view is that data should arrive better than it left. Real form submissions are messy — 'jAKE mORRISON' with caps lock damage, full names jammed into one field when the CRM wants first and last separately, no company field even though the sales team needs one. A flow that fixes these in transit is worth visibly more than one that just copies, and it is often the difference a client actually notices in a demo: 'wait, how did it know the company?' The mental shift this lesson teaches is that the middle of a flow is a workshop, not a pipe — and every transform step you learn (formatting, splitting, deriving) is a reusable part you will drop into dozens of future builds.

Demo

Take the messy-but-realistic submission 'jAKE mORRISON / jake@acmedental.com / need a booking bot' and upgrade your flow to clean it. In Zapier, add a step between trigger and action using the built-in Formatter by Zapier app (Formatter steps count as tasks like any other). First transform: event Text, transform Capitalize, input the Full name field — 'jAKE mORRISON' becomes 'Jake Morrison'. Second transform: event Text, transform Split Text, input the capitalized name, separator: one space — the output gives you segments you can map as First name 'Jake' and Last name 'Morrison'. Third transform, the crowd-pleaser: Split Text on the Email field with separator @, take the last segment — 'jake@acmedental.com' yields 'acmedental.com', a free company guess that is right surprisingly often for business leads. In Make the same three transforms need no extra modules at all: you type functions directly into the mapping fields of the Sheets module, wrapping the form values in its built-in text functions (capitalize, split, and so on) from the functions panel.

Be honest about the enrichment's limits, because clients will ask. Splitting on a single space mangles 'Mary Jane Watson' (First: 'Mary', rest: 'Jane Watson') — acceptable for a leads sheet, worth flagging in a handover note. And the domain trick only works on business addresses: gmail.com, yahoo.com, or outlook.com tell you nothing about an employer. Update your sheet headers to First Name, Last Name, Email, Company Guess, Message, Submitted At, remap the action step to the formatter's outputs, and run Jake through. The row should read: Jake, Morrison, jake@acmedental.com, acmedental.com, need a booking bot, plus the timestamp. Same submission, visibly better data.

Try it yourself

1. Add the capitalize transform and push the test submission 'jAKE mORRISON' through — confirm the sheet shows 'Jake Morrison', not the caps-lock original.
2. Add the split-name transform, change your sheet headers to include First Name and Last Name columns, and remap the action so the two segments land in the right columns.
3. Add the email-domain split and a Company Guess column, then submit two test leads — one with a business-looking address you invent and one with a gmail.com address — and compare what lands in Company Guess for each.
4. Submit 'Mary Jane Watson' through the flow and write down exactly how your split handled the three-word name — you now know a limitation to disclose, not discover, in client work.
5. Count the tasks or operations one submission now consumes (trigger + transforms + row) and recompute how many submissions your free plan can handle this month.

References

• Zapier Help — Formatter by Zapier
• Make Help — Functions