Scheduling & Booking · Integration
Google Calendar
Add Google Calendar to your product for your customers, and give your AI agents governed access to it.
A Google Calendar integration is mostly plain sailing until recurrence appears. Calendars, events, attendees, reminders and a free/busy query are all ordinary work, but a recurring event is one series plus a set of exceptions: an instance moved, an instance cancelled, an instance edited on its own, each with its own id and its own relationship to the parent. Reading the series and assuming every occurrence follows it is the classic source of double bookings. Push notification channels are the other trap, because a channel carries an expiry and stops delivering once it lapses, so renewal has to be scheduled rather than assumed. fastn owns the per-user authorisation, those channel renewals and Google's API upkeep.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each user connect their own calendar so your product books time without anybody sharing a password.
Expand a recurring series into occurrences, and handle a moved or cancelled one as its own record.
Query free/busy across the attendees a meeting needs before your product offers a time.
Subscribe to push notifications for a calendar and renew the channel before it expires, so changes keep arriving.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent finds a slot that suits everyone invited and proposes it before anything is booked.
An agent creates or moves an event within the permissions granted, and the calendar it wrote to is logged.
An agent makes clear that a single occurrence changed rather than the whole series.
Example prompt
Was tomorrow's standup moved for that day only, or has the whole recurring series shifted?
Set up Google Calendar in 4 steps
- 01Enable the Google Calendar connector from your fastn dashboard.
- 02Have each customer authorise their own Google Calendar account, so calls run under their credentials rather than a shared key.
- 03Decide which calendars, events, attendees and free/busy windows your product needs, and plan for recurrence exceptions and for push notification channels expiring.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the Google Calendar integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Google Calendar integration without building it. Your customers connect their own Google Calendar account inside your product and work their bookings, events and availability there, with no per-customer code on your side.
- Handle the part that actually costs time: availability is only true at the moment you read it, so a stale free/busy picture becomes a double booking somebody has to apologise for. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Google Calendar update is not your on-call problem.
- One integration serves your product and your agents. The same governed Google Calendar connection powers in-product features and gives AI agents scoped, audited access, so you let people book and reschedule without leaving your product without wiring it twice.
Used by these teams
Compare with
Zoho Calendar
YouCanBook.meWorks well with
Microsoft OutlookOften used alongside
Tools the same teams tend to run next to Google Calendar, across other categories.
Slack
Twilio
AircallGoogle Calendar integration FAQ
How do I add a Google Calendar integration to my product?
Enable the Google Calendar connector in your fastn dashboard, then let each customer authenticate their own Google Calendar account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Google Calendar client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Google Calendar account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Google Calendar account and only ever sees their own bookings, events and availability. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Google Calendar integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent finds a slot that suits everyone invited and proposes it before anything is booked.
Who maintains the Google Calendar integration?
fastn does. When Google Calendar changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Can my product create, reschedule or cancel bookings in Google Calendar automatically?
Yes, in each customer's own account. Your product reads live availability, places a booking, moves it or cancels it, and reacts when someone books or cancels on the other side.
Does it respect each team's own availability rules in Google Calendar?
Yes. Working hours, buffers, lead times, resource capacity and routing rules are configured per customer and mapped rather than hard-coded, so an unusual setup works without code from you.
What can I build with the Google Calendar integration?
A common starting point: let each user connect their own calendar so your product books time without anybody sharing a password. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Google Calendar integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Google Calendar does not change your per-connector cost. You can start free with 3 connected accounts.
Add Google Calendar to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.