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 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.

I am using {{zap_meta_human_now}} to update a date field in Airtable. I have my Profile Settings to America/New York for Eastern time. 

 

When I test the action, the date and time “12/8/2022 2:30pm” is updated in Airtable. 

When the Zap runs from an actual trigger, it instead puts “12/8/2022 9:30am,” a 5 hour difference. 

 

Any ideas why it works in the test function, but not in the live Zap?

@CarlL 

That is peculiar. Have you checked your Zapier Run History to see if that gives any insight and double checked the field settings in Airtable?

 

Hi @CarlL 

Good question.

Check your Zap specific Timezone Settings found here: Zap Editor > right rail > Setting > Timezone field

 

@CarlL 

That is peculiar. Have you checked your Zapier Run History to see if that gives any insight and double checked the field settings in Airtable?

 

 

@Troy Tessalone The Zap specific settings are correct, so that wasn’t the problem. 

@GetUWired Thanks, that showed me the problem. Zapier was giving the time in the correct time zone, but Airtable was reading it as being in UTC time. I don’t understand why that does not affect testing the action and I’ve not had the problem in other Zaps using Airtable. But for this one, I changed the use to {{zap_meta_utc_iso}} and now it is accurate in Airtable.

@CarlL 

I’ve had other clients experience this issue as well in Airtable.

Airtable recently made changes to how Date fields handle timezones, so that may be the root of the issue.

Check your Airtable Date field settings related to timezone.

 

Thanks for swinging back around to share your solution with the community, @CarlL! 

Appreciate you sharing the Airtable insight too, @Troy Tessalone! Super handy to know. 🤗

 

Terms & Conditions