Google Calendar
Askel connects to your customer's Google Calendar, letting your product schedule events, read availability, and react to meeting changes in the calendars your customers actually use.
What you can do
Create events with attendees
Insert events into a calendar with a summary, description, start and end time, timezone, location, and a list of attendee email addresses. Google sends invites automatically.
Read free/busy availability
Use the freebusy query endpoint to check availability across multiple calendars at once without reading the full event details, useful for scheduling without over-privileging access.
List and filter events by date range
Fetch events between two timestamps from a specific calendar. Filter by updated time to pull only events that have changed since the last sync.
Update and cancel events
Patch an existing event to change the time, description, or attendee list. Delete or cancel events and notify attendees automatically via the sendUpdates parameter.
Create recurring events
Set RRULE strings to create daily, weekly, or monthly recurring events in the customer's calendar, suitable for recurring training sessions or check-ins.
Watch for event changes via webhooks
Register a push notification channel on a calendar. Google sends a webhook to Askel when events are created, modified, or deleted, triggering downstream workflow steps.
Automatically scheduling onboarding training sessions for new customers
You sell a SaaS tool for construction teams. Harborview Labs signs a contract and expects their first three training sessions to be on their calendar by the time they log in for the first time. Each session should include a video-call link and a description of what will be covered.
- 1
Connect once
Harborview's admin completes Google OAuth in your product, approving Calendar read and write scopes. Askel stores the refresh token.
- 2
Read available calendars
Askel calls calendarList.list to enumerate the user's calendars. Your product picks the primary calendar as the default target.
- 3
Check free/busy before scheduling
Askel queries the freebusy endpoint for each proposed session slot to avoid double-booking. If a slot is busy, your product selects the next available window.
- 4
Create the three training events
Askel inserts three events spread over the first two weeks, each with the correct timezone, a description of the session content, the CS contact as organiser, and a video-call link in the location field.
- 5
Write back confirmation
Askel returns the event IDs and links to your product. The customer's welcome email includes direct links to add the events to their calendar if they use a different client.
OAuth 2.0
The customer's Google user completes a standard OAuth consent flow approving the https://www.googleapis.com/auth/calendar scope. For read-only workflows, Askel can request the narrower calendar.readonly scope instead. Askel stores the refresh token and handles silent renewal so your team never sees raw tokens.
How Askel sits between your product and the customer's system
FAQ for Google Calendar
Can we read multiple calendars from the same account?+
How are timezones handled?+
What happens if the customer deletes an event we created?+
Does this work with Google Workspace calendars that have sharing restrictions?+
catching drift before it breaks, and hitting go-live dates.
© 2025 Askel.ai. All rights reserved.