Google Calendar API v3 changes starting March 11 2024

Questions & Answers
1

Regarding the Google Calendar API v3 announcement yesterday.

Questions:

  1. Will Make’s Google Calendar module be impacted?
  2. If so, is there a roadmap for API 3 compatibility?
  3. Will Make users be required to make changes to scenarios to ensure continuous uninterrupted scenario operation?
  4. If so, how and when will this be communicated to Make users?

Goal: A clear, concise and unambiguous answer to the questions above.
Steps I’ve taken: Read the announcement from Google.

Thanks.

Text of Google announcement email dated 7th February:

Hello Google Developer,

We are writing to inform you about upcoming changes to the Google Calendar API v3 that may impact your applications and notification handling, starting March 11, 2024.

What does this mean for your organization?

The Google Calendar API v3 will now include the eventType parameter to subscribe to specific event types when using Events.Watch. Additionally, starting March 11, 2024, the following changes will be introduced:

  • Default event type filters alignment for both Events.list and Events.watch.
  • Error handling for operations not supported for special event types, such as WorkingLocation, Out of Office, and FocusTime events.

What do you need to do?

To prevent any direct impact in your applications, we strongly encourage you to review your usage of the applications listed below and take the following actions:

  • Events.watch: Specify the event types you need for your application as a parameter to reduce your infrastructure costs. In case you want to request a quota increase, please make sure you have implemented event type filters appropriately. This factor will be considered when we are evaluating quota increase requests.
  • Events.list: Specify the event types you need for your application as a parameter. Without making this change, working location events will start to be returned.
  • Event type: If your code is performing operations on special events, it is important to review it to ensure that your code does not attempt to perform operations not supported for special event types.

We’re here to help

Explore the updated documentation and resources to learn more about Google Calendar API v3:

If you have additional questions, please refer to get help from Google and the developer community.

Thanks for choosing Google Workspace.

– The Google Developer Team

2

Hello @schoolreadinglist thank you very much for raising this here.

Given that this change was announced just yesterday and with a tight deadline, we don’t have specific information to share at the moment.

However, our dev team is currently investigating this with top priority to understand the impact and necessary adjustments as soon as possible.

I am monitoring this issue and will make sure to provide any updates as soon as we have them.

Thanks again for bringing this up. :pray:

1 Like
3

Hello @schoolreadinglist :wave:

Thanks once again for bringing this up in the community. I just wanted to give you a quick update on this matter.

We’ve already sent out an email to our Google Calendar users, clarifying the implications of the API changes. In summary, no action is needed on your end. The changes only involve additional functionality in the Search Events and Watch Events modules.

:email: Further details are available in the above-mentioned email. Additionally, I’ll share the information here for the benefit of the community:

If you are using the Search Events or Watch Events modules, there is now an additional Event Type - Working Location.

If you make no changes to your scenario, this event type will automatically be included in your returned results.

However, if you wish to customize your query, we’ve added a filter so you can choose which Event Types to include. Adding Working Location to your query could be helpful if you have multiple locations you wish to identify.

1 Like