×

Fix Formatting Issues in Zapier

/ Zapier / By

Fix Formatting Issues in Zapier Steps

When you build automated workflows in Zapier, you may sometimes see that data looks correct in one action but appears incorrectly formatted in a later step. This guide explains why that happens and how to fix it so your Zapier automations run consistently.

This article focuses on troubleshooting formatting problems that appear after your Zap runs, such as numbers, dates, or text changing format between steps.

How formatted data works in Zapier

Every step in a Zap processes data independently. Zapier passes fields from one step to the next, but how that data is stored and displayed can change depending on the app, field type, and mapping method you use.

Common situations where you might see differences include:

  • Triggers that supply values in one format, while actions expect another.
  • Numbers that appear with or without commas or decimal places.
  • Dates and times that change time zone or format.
  • Text values that show full raw content instead of a shortened, user-friendly label.

Understanding how each step reads and outputs fields helps you diagnose formatting issues and avoid unexpected results in later parts of your automation.

Main causes of incorrect formatting in Zapier

Most incorrect formatting in Zapier is caused by one of three issues: field types, app behavior, or how data is mapped. Below are the most common causes.

1. Field types differ between Zapier steps

Apps often treat the same value differently depending on their field types. For example, a trigger may send a number as text, while the next action expects a numeric field. When this happens, the value can display in an unexpected way.

Watch for issues with:

  • Numbers: Currency symbols, commas, or decimal precision may be removed or changed.
  • Dates: Date-only values may turn into full date-time strings.
  • Booleans: “Yes/No” can become true/false or 1/0.

If Zapier must convert a value to match a different field type, it may change how the data looks, even though the underlying value is still usable.

2. App-specific formatting behavior

Some apps format data only within their own interface. When Zapier pulls that same data via the app’s API, the app may return a raw or unformatted version instead of the friendly view you see in the app.

Examples include:

  • A CRM that shows a nicely formatted phone number in the UI, but sends digits only to Zapier.
  • A spreadsheet app that displays a date in your local format but sends a standardized timestamp to your Zap.
  • A project tool that displays a calculated field but returns the underlying raw value to Zapier.

Because these behaviors come from the connected app, you may need to add a formatting step inside your Zap to recreate the look you want.

3. Mapping the wrong fields in Zapier

Another frequent cause is accidentally mapping an internal ID or raw value instead of the formatted or display field you intended to use in your Zapier action.

Typical signs include:

  • Receiving numerical IDs instead of clear labels or names.
  • Seeing values like status_open instead of “Open”.
  • Getting template variables or code-like text instead of human-readable text.

Many apps provide both a machine-friendly field and a display field for the same concept. Selecting the correct one in your Zapier action step often resolves the issue.

How to troubleshoot incorrect formatting in Zapier

Use the steps below to systematically find and fix incorrect formatting in your workflow.

Step 1: Test each Zapier step individually

  1. Open your Zap in the editor.
  2. Start with the trigger and click Test or Test trigger.
  3. Expand each field and note how the data is formatted.
  4. Move to the next action and test it, again reviewing each field.

Comparing input and output at every step helps you identify exactly where the formatting first changes in Zapier.

Step 2: Compare the app UI with Zapier data

  1. Open the record in the connected app itself.
  2. Check how the app displays the relevant fields (number, date, text, status, etc.).
  3. Compare that with what you see in your Zap test results for the same record.

If the app already sends raw or unformatted data to Zapier, you will likely need to format it within your Zap rather than expecting it to match the app’s screen view.

Step 3: Confirm the correct fields are mapped

  1. Edit the Zapier action step where the format looks wrong.
  2. In the field mapping panel, click into each field that uses data from a previous step.
  3. Review the dropdown list of available fields and look for:
  • A label or display field, such as “Name” or “Display value”.
  • A raw field, such as “ID”, “Internal value”, or similar technical names.

Make sure you are selecting the display-style field when you want human-readable output. After updating the mapping, retest the step to confirm the fix.

Step 4: Use Formatter by Zapier to standardize data

If the source app does not provide the format you need, add a Formatter by Zapier step before the action that requires clean or specific formatting. Common use cases include:

  • Numbers: Add or remove decimal places, strip symbols, or convert text to a numeric value.
  • Dates/Times: Convert between formats, adjust time zones, or extract only the date or time.
  • Text: Capitalize, trim extra characters, split or join values, or replace certain segments.

After the Formatter step, map its output fields into your next Zapier action to keep formatting consistent.

Advanced Zapier formatting tips

Use test data that matches real usage

Always test Zapier steps with records that represent real-world data. Formatting issues often appear only when fields contain special characters, large numbers, or unusual date formats.

Check for hidden or optional fields

Some apps expose additional fields to Zapier that are not visible in the standard user interface. Review all available fields in the mapping dropdown: sometimes a better formatted version of the same data is available but easy to miss.

Handle locale and time zone differences

Formatting differences between your app’s locale and Zapier settings can lead to unexpected date or number formats. If you work across regions, use Formatter steps to normalize values into a consistent standard, then reformat if needed in the receiving app.

When to contact support about Zapier formatting

If you have verified field mapping, tested each step, and tried Formatter but your data still looks wrong, you may be encountering an app-specific limitation or bug.

In that case:

  • Document the problem with screenshots of the app UI, Zapier test data, and any error messages.
  • Confirm which step first shows the incorrect format.
  • Share the full Zap configuration (trigger, actions, and Formatter steps) with support.

Then review the official Zapier help article on this topic at this support page and contact support if your scenario matches their escalation criteria.

Learn more about building reliable Zapier workflows

Optimizing formatting is just one part of building stable automations. For broader workflow and integration strategy, you can explore additional resources like Consultevo, which covers automation design, API integrations, and process optimization beyond the basics of Zapier.

By understanding how each app structures its data, carefully mapping the correct fields, and using Formatter by Zapier when needed, you can prevent most formatting surprises and keep your automations running smoothly from start to finish.

Need Help With Zapier?

Work with ConsultEvo — a

Zapier Certified Solution Partner

helping teams build reliable, scalable automations that actually move the business forward.


Get Zapier Help