Google Calendar
Google Calendar emits event changes to Mobius through Calendar push notifications and incremental sync.
A Google Calendar integration connects a user's primary calendar to Mobius with Google OAuth, creates a Calendar event watch, and emits source events when calendar events are created, updated, or deleted.
Use Google Calendar when Mobius should know about meeting lifecycle changes or when assistants need to read and manage calendar events.
For the shared Google credential model, see Google integrations.
Capability map
| Capability | Value |
|---|---|
| Provider ID | google_calendar |
| Auth kind | oauth2_user |
| Connect flow | Google OAuth user grant |
| Actions | Yes |
| Events | Yes |
| Webhook delivery | Yes |
| Event samples | Yes |
| Live status | Yes |
Connect Google Calendar
| Surface | Support |
|---|---|
| App | Open Build > Integrations, choose Google Calendar, then continue through Google OAuth. |
| CLI | The mobius CLI does not connect Google Calendar integrations yet. Use the app or API. |
| API | Call POST /v1/integrations/providers/google_calendar/connect with an empty JSON body, then redirect the user to the returned Google OAuth URL. |
The account choice defaults to My account. An organization administrator can choose Shared account before sign-in for a calendar the team shares. A team member's own account can only be connected as theirs. The selected Google account remains the acting identity either way. After connecting, open the account and grant it to selected assistants under Assistant access. A personal grant limits use of the calendar and retention of its tool results to the manager's Mobius audience; a team-managed grant can name the team or selected people. This audience does not restrict meeting attendees.
On connect, Mobius performs an initial Calendar sync, stores Google's
nextSyncToken, creates an events.watch channel for the primary calendar,
and stores the returned channel metadata. Google expires Calendar channels, so
Mobius renews the watch before expiration.
The webhook callback contains only Google channel headers. When a callback
arrives, Mobius validates the channel token, runs an incremental events.list
request with the stored sync token, emits events for the changed Calendar
events, and stores the new sync token.
Permissions
Mobius requests Calendar event, readonly, and free/busy scopes by default. Event
write actions need calendar.events; free/busy checks need calendar.freebusy;
the initial list and watch setup need read access to the calendars visible to
the connected account.
The integration watches the connected user's primary calendar. Actions can read and write other calendars visible to the account when the action input provides the calendar ID.
Events
google_calendar.event.created
google_calendar.event.updated
google_calendar.event.deletedDeleted or cancelled Google events are emitted as
google_calendar.event.deleted. Created events are detected when Google reports
matching created and updated timestamps; other non-cancelled deltas are emitted
as updates.
Actions
google_calendar.calendar.list
google_calendar.event.create
google_calendar.event.delete
google_calendar.event.get
google_calendar.event.list
google_calendar.event.patch_attendees
google_calendar.event.quick_add
google_calendar.event.respond
google_calendar.event.update
google_calendar.freebusy.queryUse google_calendar.event.patch_attendees for attendee-only edits. It reads
the existing event, merges attendees, and patches the attendee list without
replacing the full event.
Creating, changing, deleting, or responding to an event runs as soon as the assistant calls the action and the selected Google account still passes its live grant checks. Mobius does not add a confirmation step. Use an interaction when the instructions call for human review, and remember that the interaction does not enforce the later Calendar call.
Troubleshooting
The live status says the watch expired
Google Calendar push channels expire. Mobius renews them before expiration, but a deployment outage or missing callback URL can let a channel lapse. Reconnect Google Calendar, or wait for the renewal runner after the deployment is healthy.
A callback arrived but no event was recorded
Calendar callbacks contain channel metadata, not the event body. Mobius fetches changes with the stored sync token, then emits source events for created, updated, or cancelled events. If Google returns no relevant event delta, Mobius records nothing.
Deleted events appear as updates in Google
Mobius emits cancelled or deleted Google events as
google_calendar.event.deleted, so watch that event name for removed
meetings.
Next
- Inspect event payloads from the event catalog.
- Debug provider delivery with source events.
- Manage calendar access in Connect accounts.