Automate Google Calendar
HumDay reads Google Calendar’s own published API description and derives 37 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.
What Google Calendar is
Manipulates events and other calendar data.
API host: www.googleapis.com
Things people automate with Google Calendar
What HumDay can do in Google Calendar
26 documented operations change something in Google Calendar.
- POSTInserts an existing calendar into the user's calendar list.
/users/me/calendarList - DELETERemoves a calendar from the user's calendar list.
/users/me/calendarList/{calendarId} - PATCHUpdates an existing calendar on the user's calendar list.
/users/me/calendarList/{calendarId} - PUTUpdates an existing calendar on the user's calendar list.
/users/me/calendarList/{calendarId} - POSTImports an event. This operation is used to add a private copy of an existing event to a calendar.
/calendars/{calendarId}/events/import - POSTCreates a secondary calendar.
/calendars - POSTCreates an event.
/calendars/{calendarId}/events - POSTStop watching resources through this channel
/channels/stop - POSTCreates an event based on a simple text string.
/calendars/{calendarId}/events/quickAdd - POSTMoves an event to another calendar, i.e.
/calendars/{calendarId}/events/{eventId}/move - DELETEDeletes a secondary calendar.
/calendars/{calendarId} - PATCHUpdates metadata for a calendar.
/calendars/{calendarId} - PUTUpdates metadata for a calendar.
/calendars/{calendarId} - POSTReturns free/busy information for a set of calendars.
/freeBusy - DELETEDeletes an event.
/calendars/{calendarId}/events/{eventId} - PATCHUpdates an event. This method supports patch semantics.
/calendars/{calendarId}/events/{eventId} - PUTUpdates an event.
/calendars/{calendarId}/events/{eventId} - POSTClears a primary calendar.
/calendars/{calendarId}/clear - POSTWatch for changes to Settings resources.
/users/me/settings/watch - POSTWatch for changes to CalendarList resources.
/users/me/calendarList/watch - POSTWatch for changes to Events resources.
/calendars/{calendarId}/events/watch - POSTCreates an access control rule.
/calendars/{calendarId}/acl - POSTWatch for changes to ACL resources.
/calendars/{calendarId}/acl/watch - DELETEDeletes an access control rule.
/calendars/{calendarId}/acl/{ruleId} - PATCHUpdates an access control rule.
/calendars/{calendarId}/acl/{ruleId} - PUTUpdates an access control rule.
/calendars/{calendarId}/acl/{ruleId}
What HumDay can read from Google Calendar
These are the operations a schedule or a trigger can watch.
- GETReturns the calendars on the user's calendar list.
/users/me/calendarList - GETReturns a calendar from the user's calendar list.
/users/me/calendarList/{calendarId} - GETReturns all user settings for the authenticated user.
/users/me/settings - GETReturns the color definitions for calendars and events.
/colors - GETReturns an event based on its Google Calendar ID.
/calendars/{calendarId}/events/{eventId} - GETReturns events on the specified calendar.
/calendars/{calendarId}/events - GETReturns a single user setting.
/users/me/settings/{setting} - GETReturns metadata for a calendar.
/calendars/{calendarId} - GETReturns instances of the specified recurring event.
/calendars/{calendarId}/events/{eventId}/instances - GETReturns the rules in the access control list for the calendar.
/calendars/{calendarId}/acl - GETReturns an access control rule.
/calendars/{calendarId}/acl/{ruleId}
How automating Google Calendar works
- Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
- Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
- See it proven. The program runs and shows you the result before it is allowed near your live Google Calendar account.
- Grant access, then go live. You approve the specific Google Calendar operations it may use — and only those.
Popular Google Calendar integrations
Connect Google Calendar to the tools people pair it with most.
- Google Calendar and OData for namespace microsoft.graphintegration
- Google Calendar and Cloudflareintegration
- Google Calendar and NetBoxintegration
- Google Calendar and GitHubintegration
- Google Calendar and Mistintegration
- Google Calendar and Loket.nlintegration
- Google Calendar and Atlassian The Jira Cloud platformintegration
- Google Calendar and Magento B2Bintegration
- Google Calendar and Stripeintegration
- Google Calendar and Zuora Reference Billingintegration
- Google Calendar and bunqintegration
- Google Calendar and DocuSignintegration
Automate Google Calendar with these
- Gmail79 operations
- Google+9 operations
- Google Abusive Experience Report2 operations
- Google Accelerated Mobile Pages (AMP) URL1 operations
- Google Access Approval7 operations
- Google Access Context Manager9 operations
- Google ACME DNS2 operations
- Google Ad Exchange Buyer38 operations
- Google Ad Exchange Buyer II50 operations
- Google Ad Experience Report2 operations
- Google Admin SDK122 operations
- Google AdMob7 operations
Categories
Questions about Google Calendar automation
- Can HumDay connect to Google Calendar?
- Yes. HumDay reads Google Calendar's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 37 operations are documented.
- Do I need to write code to automate Google Calendar?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your Google Calendar account.
- What can HumDay do in Google Calendar?
- 26 of the 37 documented operations change something in Google Calendar, and 11 read from it. HumDay only ever uses the specific operations your approved contract needs.
- Is my Google Calendar account safe?
- Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to Google Calendar is held behind that approval.
Where this came from
The operations above are read from a published API description for Google Calendar at calendar-json.googleapis.com/$discovery/rest?version=v3. Descriptions are the provider’s own words, not ours. Last published 2023-04-21.