Connect Google Calendar, and let the booking happen on the call
Yes. SAGARIS connects a Google Calendar over OAuth, reads your free and busy time so a meeting is only ever offered in a slot that is genuinely open, and creates, moves and cancels real events on the calendar. This is what the booking flow and the AI receptionist write against when a caller agrees to a time on the phone.
Connected. You can connect a Google Calendar over OAuth today. SAGARIS reads free and busy time and creates, moves and cancels real events on it.
Last verified October 5, 2026. All integrations
What moves, and which way
OAuth, per calendar. Refused rather than half-made if Google returns no refresh token.
- Into SAGARIS
- Free and busy time is read, which is the fact that makes the rest of it safe: an AI receptionist that offers a slot without checking the calendar books meetings on top of your existing ones. Existing events are read so a proposal can be made around them rather than over them.
- Back into Google Calendar
- Events are created, moved and cancelled on the real calendar, not held in a SAGARIS-only shadow copy. A created event carries a Google Meet link, because the create call requests conferencing. When a caller agrees to a time while still on the phone, the invitation is on their calendar before the call ends.
- The boundary
- The connection is refused rather than half-made when Google returns no refresh token, because a connection that cannot renew itself fails silently about a week later and takes a booking with it when it does. That refusal is deliberate and the reconnect instruction says to revoke third-party access in your Google account first, so the next consent issues a fresh token. SAGARIS does not integrate with Google Meet as a product: the Meet link is a property of the event the calendar API creates, and there is no Meet client in the product.
Connecting a calendar
- 01
Start the calendar connection
The connect step sits with the rest of the meeting setup. Connect the calendar the meetings should actually land on, which for most reps is their own primary calendar.
- 02
Authorize with Google, and accept the calendar scopes
The grant covers reading free and busy time and creating and modifying events. If Google hands back no refresh token, the connection is refused and you are told to revoke third-party access for the app and connect again, rather than being left with something that works today and stops next week.
- 03
Check the first proposed slot
Book one meeting through SAGARIS and look at the result in Google. The event, the invitee and the Meet link should all be there. If the slot offered was one you were busy in, the read half is not working and we want to hear about it before a customer does.
How we checked
Probed on the production service at app.sagaris.ai. GET /api/calendar/google/connect answered 401 Unauthorized, which is past the 503 not-configured guard, so the OAuth credentials are set on the serving revision. The paired control was the identically shaped GET /api/calendar/microsoft/connect in the same process on the same day, which answered 503 with the message that Microsoft 365 Calendar OAuth is not configured. The refresh-token refusal is read from the callback route rather than from documentation. This status was first measured on September 18, 2026 and re-probed on October 5, 2026 with the same result.
Verified October 5, 2026. If this is out of date or wrong, email founders@sagaris.ai and we will correct it and move the date.
Google Calendar and SAGARIS, the questions people actually ask
- MOST ASKED
Yes. Events are created, moved and cancelled on the Google Calendar you connected, and a created event carries a Meet link. There is no separate SAGARIS calendar that your colleagues cannot see.
It reads free and busy time before it offers anything, so a slot you are busy in is not offered. That read is the reason the booking half is safe to automate at all.
Not as a product, and we would be overstating it to say so. The Meet link on an event exists because the Google Calendar create call requests conferencing. There is no Meet client in SAGARIS, so nothing reads or acts on the meeting itself.
Most often because Google returned no refresh token, which happens on a re-consent where the previous grant is still in place. The connection is refused rather than completed with a token that cannot renew. Remove third-party access for the app in your Google account security settings, then connect again.
It is the same Google OAuth client by default, and a separate grant. Connecting a calendar does not connect a mailbox, and connecting a mailbox does not connect a calendar.
Next door