Skip to main content
Integrations · Google Calendar
Guild agents can read, create, update, and delete Google Calendar events and schedules on behalf of your team. Guild stores the OAuth token server-side and refreshes it automatically, so agent code never sees the credential. Credential policies let you restrict which operations each agent can perform, and every request is enforced through Guild’s credential proxy before it reaches Google.

Book a demo

See how teams govern agents that use Google Calendar.

Talk to sales

Get access to Guild, then connect Google Calendar to your first agent.

What the Google Calendar integration exposes

The tools cover calendar events, calendar list management, access control rules (ACL), free/busy queries, color definitions, and user settings. Agents can list and move recurring event instances, import events, and create events from plain text. Tools also include watch endpoints for monitoring changes to events, calendars, ACLs, and settings resources.

How it works

1

Open Credentials in Guild

Go to Credentials in Guild under Access and setup. The page lists integrations you can connect.
2

Authorize with Google

Click Google Calendar and complete the OAuth authorization with your Google account. Guild stores the token and refreshes it automatically.
3

Add tools to your agent

Import GoogleCalendarOauthTools and spread it into your agent’s tools object. Use pick() with the google_calendar_oauth_ prefix to include only the tools your agent needs.

Why Google Calendar access needs governing

Google Calendar tools can create, update, delete, and move events, clear primary calendars, and modify access control rules that govern who sees a calendar. Guild’s credential policies let you write ALLOW and DENY rules that Guild’s credential proxy enforces before any request reaches Google. Rules can target specific operations by name or glob pattern, scope access to particular agents or workspaces, and restrict HTTP methods so an agent can read events without being able to delete them. Credentials are stored and injected server-side through Guild’s credential proxy, so agent code, prompts, and containers never see the OAuth token. You can scope a credential to a single agent, a single workspace, or an individual member, and you can grant an existing credential to one installed agent without affecting others. Unscoped credentials fall back to the account default; a workspace can be restricted to its own credentials to prevent that fallback.

About the Google Calendar integration

The @guildai-services/guildlabs~google-calendar-oauth package gives your agents access to Google Calendar events and schedules through Guild’s Google Calendar integration.

Authentication

  • Type: OAuth 2.0
  • Token management: Refreshed automatically

Setup

1

Open Credentials

Go to Credentials in Guild.
2

Connect Google Calendar

Click Google Calendar and authorize with your Google account.

OAuth scopes

Scopes Guild requests in the latest published version of guildlabs~google-calendar-oauth:

Usage

Selecting specific tools

Tools are named with the google_calendar_oauth_ prefix. Use pick() to include only what your agent needs.

Tools

Tools in the latest published version of guildlabs~google-calendar-oauth:

Frequently asked questions

No. The catalog entry for guildlabs~google-calendar-oauth lists no webhook events. Agents can poll for changes using the watch tools included in the integration, but Guild does not deliver inbound webhook pushes from Google Calendar.
Guild refreshes the token automatically. The page lists token management as refreshed automatically, and the token is held server-side so agents never handle it directly.
Yes. Credential policies support DENY rules scoped to specific operations and HTTP methods. You can deny operations such as google_calendar_oauth_events_delete and google_calendar_oauth_calendars_clear while allowing read-only operations, and scope those rules to a specific agent or workspace.
Yes. A credential connected at the account level serves every workspace the account owns by default. You can also scope a credential to one workspace, one member, or one agent if you need different Google accounts in different contexts. See Service credentials for the full scoping options.

Put a governed agent on Google Calendar this week

Book a demo

See how teams govern agents that use Google Calendar.

Talk to sales

Get access to Guild, then connect Google Calendar to your first agent.
Also runs on Guild: Jira Read: Docs: Credential policies · Credentials · Tools in agents
Last modified on November 4, 2026