Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Asked & Answered Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

Question

How to ensure correct date output in Zapier Tables based on time zone

  • July 3, 2026
  • 1 reply
  • 6 views
L

Context:

I have a system setup where when a project reaches a certain status a series of tasks get added to my to do list. 

I’ve been messing around with Zapier tables partially to teach myself how they work but also to build a form that displays a kanban to do list.

I want the columns in the Kanban to be based on a Due Date field, in relation to today. (Overdue, Due today, Due in the next 7 days etc.)

In my Zaper Table I have field named “Due Date” set to the America/New York Time Zone. 

The Problem:

  • I update the Due Date field to trigger the zap. 
  • In the table, the date is displayed as: 07/02/26 09:30 PM
  • Now I go to the zap to set it up and the raw data for the for the new value is “2026-07-03T01:30:00.000Z”

If I change the TIME to 2:30 AM I get this set to the Zap: 2026-07-02T06:30:00.000Z

This screws up the results of my zap, as it sends the wrong date out.

How can I make sure the correct date for my time zone is output when the zap is triggered? 

I don’t actually need the time in this field at all but it seems to help keep the date sent to the zap accurate. 
 

1 reply

P
Forum|alt.badge.img
  • paul3331
  • New
  • July 3, 2026

The issue happens because Zapier Tables display dates in your local time zone but send raw trigger data in UTC time. For example, 9:30 PM in New York (EDT) shifts forward to 1:30 AM the next day in UTC. This causes the Zap to process the wrong calendar date. Since the time itself is not needed, the best fix is to create a Formula Field directly inside your Zapier Table using FORMAT_DATE(Due Date, "YYYY-MM-DD"). This converts the date into a plain text string before the Zap triggers, preventing UTC conversion from shifting the day.

Alternatively, you can fix this inside the Zap workflow using the Formatter by Zapier tool. Add a Date/Time "Format" step right after your trigger. Set the input to your raw table date, the "From Timezone" to UTC, and the "To Timezone" to America/New_York. Format it as YYYY-MM-DD and use this new, adjusted output for all your later Kanban logic steps. This keeps your dates perfectly aligned with your local time zone.

Image: Zappy Awards

The Zappy Awards are back

We're celebrating the Zapier builders making AI transformation happen. Winners get a published story on zapier.com, a trophy, $5,000 cash, and a feature at ZapConnect. Nominate yourself or a peer by July 24th, 2026.

Nominate now
Terms & ConditionsAccessibility statement