List events, create meetings, check availability, and manage RSVPs in Google Calendar. OAuth credentials are injected automatically.
Per-app Google setup is deprecated. All Google apps now share one Google OAuth client and one Redirect URI. To use your own client, follow the Google setup guide. Credentials saved for one Google app apply to all of them.
OneCLI connects AI agents to Google Calendar through Google’s OAuth flow. Agents can list upcoming events, create new meetings, check availability, and manage RSVPs. The gateway injects OAuth credentials into requests to the Google Calendar API automatically.This is useful for scheduling agents, meeting coordinators, or any agent that needs awareness of your calendar.
This is for self-hosted OneCLI, and for OneCLI Cloud when you choose Custom credentials instead of one-click. One Google client serves every Google app in OneCLI, so you set it up once. If you already did it for another Google app, skip to step 2.
1. Set up your Google client
Follow the Google setup guide. It enables the Google APIs, sets up the consent screen, creates the OAuth client, and adds the Redirect URI.You paste the client into Connections > Google Calendar > Custom credentials, under the Redirect URI the guide asks you to register:
Custom credentials for Google Calendar in OneCLI.
2. Connect Google Calendar
Open Connections > Google Calendar, select Connect Google Calendar, pick your Google account, and click Allow.
The Google Calendar connect window before a Google client is set up.
Access is per agent: grant the connection to each agent that needs it, choosing per tool what runs freely, what needs human approval, and what stays blocked — a read-only agent is a single grant. Organization rules add guardrails on top, like rate limits and blanket blocks. Everything is checked before credential injection, so a blocked request never reaches Google Calendar.