Zapier dates coming through wrong? How to fix UK date formats in your Zaps

An incoming 03/11/2026 may mean 3 November in a UK form, but a later Zap step can read it as 11 March or reject it. A timestamp can also cross midnight when converted between time zones. I build, fix and improve systems for businesses. First find where the value changes.

1. Find the value that went wrong

Open Zap History and select the run for that record. In the Zap editor, click the Zap runs icon in the left sidebar, then choose the run. Select a step to compare its data. Zapier's run details guide describes the Data In and Data Out tabs.

Record the trigger's raw value and intended date. Compare them with Formatter output and destination input. If Formatter is right but the final action receives the original date, remap the action to Formatter's output. Zapier explains this common mistake in its guide to incorrect formatted data.

2. Separate format, field type and time zone

03/11/2026 is ambiguous: DD/MM/YYYY means 3 November, while MM/DD/YYYY means 11 March. Plain text does not specify which. Check if the destination expects a date or date-time field, and that the Zap maps that field rather than a text label.

In Google Sheets, File, Settings, General contains Locale and Time zone. These settings change the spreadsheet's default date format for everyone. Format, Number sets a cell's display format. Compare the date value with what the cell shows. Google's settings guide and date formatting guide show both menus.

An Airtable Date field can display Local, US, European or ISO formats. Automations and API values use ISO 8601 in UTC regardless of display. For date-time fields, check Use the same time zone for all collaborators. A timestamp near midnight can show as another day elsewhere; keep calendar-only values as dates. Airtable's Date field guide covers these settings.

3. Parse it in Formatter by Zapier

Add an action after the trigger and choose Formatter by Zapier. Set the Action event to Date / Time, continue, then set Transform to Format. Map the source value into Input. Set From Format to the source order, such as DD/MM/YYYY, then set To Format to YYYY-MM-DD. If needed, choose Custom and enter the format.

With 03/11/2026 and From Format DD/MM/YYYY, the output should be 2026-11-03. ISO 8601 puts year, month and day in a fixed order. Map Formatter's output into the destination action. Use my UK date to ISO converter to check a sample first.

Click Continue and Test step, then inspect Data out. Zapier recommends setting From Format when order is ambiguous. An unparseable date can return now, so test blank and invalid inputs. Do not send an unexpected current date downstream.

4. Check time zones for timestamps

Zapier's account time zone defaults to UTC. In profile settings, choose your location from Timezone and save changes. This can correct a consistent hour offset, but it cannot disambiguate date order.

For a timestamp, set Formatter's From Timezone to the source zone and To Timezone to the destination zone. A blank From Timezone and the default To Timezone both mean UTC. Check the destination setting too. In Google Sheets, locale and time zone apply across the file. In Airtable, the shared zone option requires Include time. Avoid timezone conversion on date-only values.

5. Test a safe record before switching the Zap on

If a wrong value could affect customers, leave the live Zap off while editing. Use a marked test submission or destination. Test ambiguous 03/11/2026 and clear 25/11/2026. Check Formatter output and the resulting destination value and display, including blank and invalid inputs. Turn it on after normal and exception cases match expectations.

6. Repair records that already went through

Separate errored runs from successful runs with a wrong date. After fixing the format, replay one errored run from Zap History and check its result.

Do not replay a successful run blindly. An entire Zap replay reruns every step using the current published version, which can create records or resend messages. Export affected rows first. Correct destination records directly, or use a controlled update matched by a stable record ID. Test one, confirm it, then update only verified records. Avoid repeating other actions. Zapier's replay guide explains both replay options.

For a wider handoff between forms and connected apps, see my integrations service. It covers scoped connections, tests and handover.