Hi @ardifa
Good question.
There are a few reasons why events might be created for the wrong time or date by a Zap.
Check the timezone setting of both the trigger and action apps, and in Zapier.
When the timezones don't match between apps, this can cause the event to not be created on the expected date and time.
To fix this:
- Change the Timezone settings for your Zapier account.
- Check your Google Calendar timezone settings.
- Refer to the help documentation of any other app in your Zap, to check the timezone on that app. You may also want to check that app's help pages on Zapier to see if there are any known limitations or restrictions for date/time fields.
If none of these steps addresses your problem, try to use Formatter by Zapier or date/time modifications to correct any date differences between apps.
All-day events in Google Calendar end at midnight on the last day, so they're exclusive of the end date. For example, an event created via Zapier for August 10 - August 15 will appear to span August 10 - August 14 in Google Calendar, because the event will end at 12:00:00 on August 15.
To fix this:
- Update your trigger data so that it lasts for an extra day.
- Or, modify the end date in your Zap directly by adjusting the date/time to include
+1d
. This will cause the event to last for an extra day.
Regardless of the settings in your Google Calendar, data sent through their API (as Zapier does) must be in MM/DD/YYYY
format. So, if you try to send an event for April 7, 2021 as 07/04/2021
, Google Calendar will interpret that as July 4, 2021. The dates need to be in MM/DD/YYYY
format to ensure Google Calendar adds the event to the correct date(s). If your trigger is sending the data in DD/MM
format, you can use a Formatter step to reformat the date.
If you're using the Quick Add Event action instead of the Create Detailed Event action, there are some specific guidelines that must be followed to make sure that Google Calendar can interpret the date and time correctly.
This may happen if the start and end time/date are invalid. Events created with an invalid start or end date will be created for the time your Zap runs.
Hey @ardifa are you able to post a screenshot of how the data is being read after testing the action? Looks like that one may not have come across. That might help us narrow down which of the approaches Troy mentioned are most applicable here. Just be sure to not include any PII in your screenshots, please!