The Zapier Formatter is a built-in tool that cleans and reshapes data in the middle of a Zap. You add it as an action step, pick what kind of data you are changing (text, numbers, dates or lists), choose a transform such as “Split Text” or “Format Date”, and the next step receives the cleaned value instead of the raw one. It is the fix for messy form entries, dates in the wrong format and names in all caps.
Most broken or embarrassing automations come down to formatting: a welcome email that says “Hi JOHN SMITH”, a CRM that rejects a phone number, a spreadsheet full of timestamps nobody can read. This guide shows how to add Formatter, which transforms solve which problems, and how to avoid the mistakes that make Formatter steps fail.
How to add a Zapier Formatter step
Formatter works the same way in every Zap:
- In the Zap editor, add a step between the step that produces the data and the step that uses it.
- Search for and select Formatter by Zapier. There is no account to connect.
- Choose the action event, which is the type of data: Text, Numbers, Date/Time or Utilities.
- Choose the transform, the specific change you want, such as Capitalize or Split Text.
- In the Input field, map the value you want to change from an earlier step.
- Fill in any options the transform needs, such as the separator or the output format.
- Test the step and check the output.
- In the next action, map the Formatter step’s output instead of the original field.
That last step is the one people forget. If you leave the original field mapped in your action, the Formatter step runs but its result is never used.
Zapier also offers AI help in the editor that can suggest formatting as you map fields. It can be a useful starting point, but always check the transform it picked and test it with real data.
Text transforms: fixing names, emails and messages
Text is where you will use Formatter most. These are the transforms that solve everyday problems.
Fix capitalization
People type names in every possible style. The Capitalize or Titlecase transforms turn “jane DOE” into a readable “Jane Doe”. Lowercase is useful for email addresses before you search for or match them, so “Jane@Example.com” and “jane@example.com” are treated as the same person.
Be careful with names that have unusual capitalization, such as “McDonald” or “van der Berg”. Titlecase may get them wrong. For customer-facing emails, many teams use the first name only and accept the occasional imperfection.
Split a full name into first and last
Many forms collect one “Full name” field while your CRM wants two. Use Split Text with a space as the separator, and choose to return the first segment for the first name. For the last name, use a second Split Text step and return the last segment. This handles middle names reasonably well, though no rule is perfect for every name.
Remove extra spaces and set a default value
Trim Whitespace removes stray spaces that cause failed matches and lookups. Default Value fills in something sensible when a field is empty, such as “there” so an email reads “Hi there” instead of “Hi ,”.
Pull out an email, URL or number
The extract transforms find a specific kind of value inside a longer block of text. This is useful when the data arrives as a message body, such as a notification email: extract the email address or a URL and pass only that to the next step.
Find and replace
Replace swaps one piece of text for another. Common uses are removing a prefix your form adds, swapping line breaks for commas, or turning internal codes into readable labels.
Number transforms: math, currency and phone numbers
The Numbers event handles values that need to be calculated or presented consistently:
- Format Number: control decimal places and separators, so “1234.5” becomes a consistent number your accounting tool accepts.
- Format Currency: present a value with the right currency formatting for an invoice line or a team notification.
- Format Phone Number: convert phone numbers into a standard pattern. Many CRMs and SMS tools require an international format, so pick the format your destination app documents.
- Perform Math Operation: add, subtract, multiply or divide values, for example adding tax or shipping to a subtotal.
- Spreadsheet-Style Formula: write a formula similar to a spreadsheet when one operation is not enough, such as rounding the result of a calculation.
When numbers come from forms, they often arrive as text with commas or currency symbols. Clean them with a text Replace step first, then run the number transform.
Date and time transforms
Every app seems to store dates differently. The Date/Time event fixes that:
- Format: convert a date from one format to another, and set the time zone so the output matches where your team works.
- Add/Subtract Time: create a follow-up date, such as three days after a booking, or a due date for an onboarding task.
- Compare Dates: work out the time between two dates, which is useful for “days since signup” style values.
Time zones cause most date bugs. If a deadline lands a day early or late, check both the time zone of the input and the time zone you set in the Formatter step. Your Zapier account also has a time zone setting that affects how dates are read, so check it in your settings.
Utilities: lookup tables and line items
The Utilities event contains the most powerful Formatter features.
Lookup tables
A lookup table maps one value to another. You enter a list of keys and the values they should become, plus a fallback for anything not listed. Examples:
- A form answer like “Option 2” becomes the CRM pipeline stage “Qualified”.
- A country name becomes the email address of the regional sales rep.
- A product name becomes the ID your accounting tool needs.
Lookup tables are often a cleaner alternative to branching logic when you only need to change one value based on another. Keep the fallback value meaningful, such as “Unassigned”, so missing matches are easy to spot.
Line items
Orders, invoices and some forms contain lists, such as several products in one order. Formatter can turn text into line items, combine several fields into line items, or convert line items back into a single text value. Use these when the destination app accepts line items, such as an invoicing or accounting action that supports multiple products per invoice.
Pick from a list and split into separate values
Other utilities let you pick a specific item from a list, or count and split values. These help when an app sends several values in one field and you only need one of them.
A worked example: cleaning a lead before it reaches your CRM
Here is a common chain for a website contact form:
- Trigger: new form submission.
- Formatter, Text, Trim Whitespace on the email field.
- Formatter, Text, Lowercase on the trimmed email.
- Formatter, Text, Split Text on the full name to get the first name.
- Formatter, Text, Titlecase on the first name.
- Formatter, Utilities, Lookup Table to turn the “How did you hear about us?” answer into your CRM’s lead source values.
- Formatter, Numbers, Format Phone Number on the phone field.
- Action: create or update the CRM contact, mapping every cleaned value.
It looks like a lot of steps, but each one is simple, readable and easy to change. If you are building this kind of Zap for the first time, our walkthrough on how to set up Zapier and build your first Zap covers the trigger, testing and publishing steps around it.
Common Zapier Formatter mistakes
- Mapping the wrong output: the action still uses the raw field instead of the Formatter result.
- Testing with clean sample data: the Formatter step looks perfect on a tidy record and fails on real input. Test with a messy entry.
- Ignoring empty inputs: some transforms behave unexpectedly when the input is blank. Add a Default Value step or a filter.
- Wrong separator in Split Text: a comma separator on a value that uses semicolons returns the whole string.
- Time zone mismatches: dates shift because input, Formatter and account time zones disagree.
- Too many chained steps for one value: if one value needs six Formatter steps, a single code step may be easier to maintain.
When Formatter is not enough
Formatter covers most clean-up work, but it has edges. If you need several conditions at once, need to parse complex nested data, or need logic that depends on many fields together, a code step or a different design is usually better. The same is true when the data problem actually starts in the source app, where fixing the form or the field type removes the need for Formatter entirely.
If your Zaps have grown into long chains of Formatter, Filter and Path steps and nobody is sure what each one does, it may be time to get help from a Zapier specialist who can simplify and document the setup. You can also send a description of the workflow to support@growthscribe.com.
FAQ
What is Formatter by Zapier used for?
Formatter is a built-in Zapier tool that changes data between steps of a Zap. It can fix capitalization, split or combine text, reformat dates, do simple math, look up values in a table and turn lists into line items, so the next app receives data in the format it expects.
Do I need a separate account for Formatter?
No. Formatter is a built-in Zapier app, so there is nothing to connect. You add it as an action step inside any Zap and choose the type of change you want.
Can one Formatter step do several changes at once?
Each Formatter step performs one transform. If a value needs several changes, such as trimming spaces and then changing capitalization, add a Formatter step for each change and feed the output of one into the next.
When should I use Code by Zapier instead of Formatter?
Use Formatter when one of its transforms does exactly what you need, because it is easier for others to read and maintain. Switch to a code step when you need logic Formatter can’t express, such as several conditions at once or parsing a complicated structure.
