Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
Zapier Formatter is a built-in step for reshaping data between a trigger and a later action. Use its Text, Date/Time, Number, and Utilities transforms to clean fields, split values, convert dates, standardize numbers, or map internal IDs before sending data to the next app. The right transform depends on the input’s structure and the format the destination field expects.
Where Formatter fits in a Zap
A Zap usually receives data from a trigger and passes selected fields to one or more actions. Insert Formatter between the trigger and the action when the source value needs to be changed before it is mapped downstream. Formatter is Zapier’s built-in utility for transforming text, numbers, and other data into the format you need.
In the Zap editor, add a step between the trigger and the destination action, choose Formatter by Zapier, then select the relevant event or transform. Configure its input using data from the trigger, test the step, and map the Formatter result—often shown as an Output field—into the destination action. Test the later action too: a transform can produce a value that looks right but still have the wrong type or convention for the receiving field.
Free tools Windows power users keep installed
One-click scans. No signup required.
1. Clean and standardize text
Text transforms are useful when a source app supplies inconsistent casing, extra whitespace, markup, unwanted characters, or values that exceed a destination’s length limit. Depending on the input and desired output, Formatter can change letter case, trim whitespace, remove characters or HTML, replace text, truncate a value, or convert between plain text, HTML, Markdown, and ASCII.
#1 Best Overall
Choose the least destructive transform
- Use a case transform when the destination needs a consistent capitalization convention.
- Trim whitespace when a value contains accidental spaces at its beginning or end.
- Replace or remove characters when you know which characters are unwanted and their removal will not erase meaningful information.
- Use an HTML or text conversion when the source and destination expect different representations.
- Truncate only when the destination imposes a length limit; check that cutting off the value will not remove information the recipient needs.
Test with representative inputs, including values that are already clean and values with unusual punctuation or markup. A transformation that works on one sample may have a different effect on a blank field or a value containing unexpected characters.
2. Split or extract fields
Use Split Text when the input has a reliable delimiter and you need one portion or a list of portions. For example, a consistent full name such as “Alex Johnson” can be split at the space so the first and last names can be mapped separately. A slash-delimited URL can be split to isolate its final numeric ID. A comma-separated tag string can be divided into line items, and an email-thread value can be split to isolate the newest message when the source format is consistent.
Use a split only when the structure supports it
A delimiter-based split makes assumptions about the input. Splitting a name on a space, for instance, is not a universally reliable way to identify first and last names: names may contain multiple spaces, multiple given or family names, or no space at all. Check what the source actually supplies and test edge cases before relying on a fixed segment position.
If the text is irregular or the desired item is defined by its content rather than a stable position, use an extraction transform instead. Formatter offers Extract Email Address, Extract Phone Number, Extract URL, and Extract Pattern (regex). Pattern extraction can target a repeatable structure in otherwise variable text, but the pattern needs to match the formats your workflow receives.
Rank #2
- Book - powershell for sysadmins: workflow automation made easy
- Language: english
- Binding: paperback
Zapier describes Split Text as a way to break data into segments. After configuring it, inspect the tested output to confirm that the segment you intend to use is the one mapped in the next action.
3. Convert dates and times
Use Date/Time formatting when one app supplies a date in a convention another app cannot accept, or when the destination requires a particular display format or timezone. Configure the input format explicitly whenever possible, select the desired output format, and specify a timezone when local time matters.
Make the input interpretation explicit
Do not assume that a date such as 04/05/2026 has an obvious meaning: depending on the convention, it could mean April 5 or May 4. If the source format is known, tell Formatter what it is rather than relying on an ambiguous guess. Then choose an output convention the destination accepts.
Zapier’s custom date tokens include MMMM D, YYYY, which produces a month-name date, and X, which represents a Unix timestamp. Use the token format appropriate to the output field; a date intended for a human-readable message may need a different representation from a timestamp expected by an app.
Account for timezone requirements
A formatted date can be syntactically valid and still represent the wrong local time if the source and destination use different timezones. Specify the timezone when localization matters, and verify the result using a date near a day boundary as well as an ordinary daytime value. If the destination expects a timestamp or a timezone-specific value, confirm that its field accepts the representation you selected.
4. Normalize numbers and phone values
Number transforms can convert numeric strings into numbers, reformat currency values, and apply spreadsheet-style formulas. Use them when a downstream field expects a numeric value or when calculations or consistent presentation are required. A string that contains digits is not necessarily the same thing as a number to the receiving app.
Check the destination field type
Before mapping the result, determine whether the destination field expects a number or text. For example, a number field may be suitable for a quantity, while an identifier with leading zeroes may need to remain text so those zeroes are not lost. Currency formatting also needs care: changing how an amount is displayed is not the same as changing the amount itself or its currency.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Format phone numbers for the receiving app
Use Format Phone Number when an app requires a standardized phone representation, such as E.164. Test with phone values representative of the countries and formats your workflow receives, and verify that the receiving field expects the resulting representation. Do not treat a phone number as an ordinary number: it is an identifier, and numeric operations can damage its formatting.
5. Map IDs and reshape values with Utilities
Utilities help turn source data into structures a later action can use. Lookup Table can translate an internal value—such as a Stripe product ID—into a friendly product name. Line-item transforms can create or join lists, and CSV import can turn tabular text into data for downstream steps.
Translate internal values with a lookup table
Configure a lookup from the source ID to the label you want the next app to receive. After testing the Formatter step, map its Output field into the later action rather than mapping the original trigger’s ID field again. Otherwise, the lookup may run correctly while the destination still receives the unconverted value.
Consider what should happen when the input ID is absent or is not represented in the lookup. Test an unknown value as well as a known one, then confirm that the resulting output is safe for the destination. Missing or malformed values can prevent later steps from receiving the content they need.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Reshape lists and tabular text
Use line-item transforms when a downstream action needs a list rather than one long text string, or when values need to be joined into a representation the next app accepts. Use CSV import when the workflow receives tabular text and later steps need its rows or fields in a structured form. Check the tested output’s structure before mapping it; a list and a comma-separated string may look similar in a text preview but behave differently in an action.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Choose a transform by the destination’s needs
| Situation | Approach | Check before mapping |
|---|---|---|
| Input has a consistent delimiter | Split Text | Confirm which segment or segments the destination needs, and test values with extra or missing delimiters. |
| Input is irregular but contains a recognizable item | Extract Email Address, Extract Phone Number, Extract URL, or Extract Pattern | Test representative variations so the extraction matches the intended value. |
| Destination expects a different date convention | Date/Time formatting | Specify the input format, output format, and timezone where needed. |
| Destination expects a numeric value or formatted amount | Number transform | Confirm whether the field expects a number or text, and preserve identifiers that must retain leading zeroes. |
| Source supplies an internal code but destination needs a label | Utilities > Lookup Table | Map the Formatter Output field and test an unknown or missing code. |
| Destination expects list data or structured tabular data | Line-item transform or CSV import | Inspect the output structure and confirm it matches the action’s expected input. |
Test the workflow and handle failures
Formatter transforms affect the values that later steps receive, so test the Formatter step and then test the destination action with its output. Include a normal value and plausible edge cases: blank input, extra whitespace, unexpected delimiters, an unrecognized ID, an ambiguous date, or malformed text. The relevant cases depend on the source and destination.
Common problems and fixes
- The destination receives the original value. Check that its field is mapped from the Formatter step’s output rather than directly from the trigger.
- A split produces the wrong segment. Confirm the input’s delimiter and whether the data always appears in the same order. Use extraction rather than a fixed split when the content is irregular.
- A date shifts or is interpreted incorrectly. Set the known input format explicitly and check the timezone and output format.
- A numeric field rejects the result. Verify that the destination expects a number rather than text, then inspect the tested output for characters or formatting the field does not accept.
- A lookup returns no useful label. Check that the incoming key matches a configured lookup value and test what happens for missing or unknown keys.
- A later step cannot use a list. Inspect whether Formatter produced line items or plain text, then choose a transform that matches the destination’s expected structure.
Or skip the browser setup
Formatter changes values inside a Zap; it does not capture website screenshots. If a separate workflow needs a website image, ScreenshotNeo is an alternative to try first for that capture task: one GET request can return a PNG, JPEG, WebP, or PDF, and its clean-shot behavior removes consent banners, newsletter popups, and chat widgets before capture. It does not replace Formatter for text, dates, numbers, or lookups.
For example, cURL can save a screenshot of a page as WebP:
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorscurl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpSee the ScreenshotNeo API documentation for request details. Bot checks, blank pages, and failed loads are never billed; an MCP server lets AI agents take screenshots; and the Free plan includes 1,000 screenshots per month with no card, while paid plans start at $5 for 3,000. Learn about ScreenshotNeo, or sign up for 1,000 free screenshots a month with no card.
Build the Zap around the value the next app needs
Start with the destination field: determine whether it expects text, a number, a date in a specific convention, a list, or a friendly label. Then select the simplest Formatter transform that turns the trigger’s data into that shape. Test the output and the later action with representative edge cases, and map the Formatter result where the transformed value is needed.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
