Skip to main content
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.

​
Overview

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.

​
What you will set up

  • A Google Calendar connection through Google OAuth, in one click on OneCLI Cloud or with your own client
  • Automatic token injection on Calendar API requests
  • Per-agent, per-tool access, such as approval before creating events

​
Connect on OneCLI Cloud (one click)

1

Go to Connections

Open the OneCLI dashboard and navigate to Connections > Google Calendar.
2

Authorize

Click Connect Google Calendar. You’ll go straight to Google: pick your account, review the permissions, and click Allow. No Google Cloud setup needed.
On self-hosted OneCLI, or to use your own Google client on Cloud, see Use your own Google client.

​
Use your own Google client

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:
OneCLI Custom credentials card for Google Calendar with the setup guide link, the Redirect URI and its copy button, and the Client ID and Client Secret fields.

Custom credentials for Google Calendar in OneCLI.

Open Connections > Google Calendar, select Connect Google Calendar, pick your Google account, and click Allow.
OneCLI connect window for Google Calendar showing Configuration required and the Configure credentials button.

The Google Calendar connect window before a Google client is set up.

​
What agents can do

  • List events on any of your calendars within a date range
  • Get details for a specific event (attendees, location, video link, description)
  • Create new events with attendees, location, and conferencing
  • Update existing events (reschedule, change attendees, modify description)
  • Delete or cancel events
  • Check free/busy availability for one or more people
  • Respond to event invitations (accept, decline, tentative)
  • List all calendars on the account
  • Create and manage secondary calendars

​
Controlling access

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.

​
FAQ

Yes. When you grant the connection, allow read tools and block or require approval for writes.
No. The token stays in OneCLI, and the gateway adds it at the proxy. See How it works.
Open Connections > Google Calendar and connect again with the account you want. Agents with access use the new connection automatically.