Skip to content
Verbatik

Integrations

Google Calendar

Connect Google Calendar, obtain the required access and configure permitted actions.

Use the existing workspace OAuth connection. You do not need to create a second native token connection.

Before you start

Connect the account belonging to this business and workspace. Vendor subscriptions, API limits and role permissions still apply.

API: Google Calendar API v3

Authentication: Existing Verbatik workspace OAuth connection, with server-side token refresh

Get access and connect

  1. Open Integrations → Google Calendar and select Connect.
  2. Authorize the Google account that owns or has access to the intended business calendar. Ask your Google Workspace administrator to approve Verbatik if the organization restricts third-party apps.
  3. Choose the calendar and enable write access only if your agent should create, reschedule or cancel appointments. Set the timezone and appointment duration.
  4. Test the connection, add the allowed calendar actions to the agent, then publish a new version. Confirm a sandbox booking appears on the correct calendar.

Account requirements

  • Your Google account must have access to the chosen business calendar. Calendar writes require permission to change events. Public OAuth availability depends on Verbatik’s connector configuration.

Permissions

  • https://www.googleapis.com/auth/calendar.calendarlist.readonly
  • https://www.googleapis.com/auth/calendar.calendars.readonly
  • https://www.googleapis.com/auth/calendar.events.freebusy
  • https://www.googleapis.com/auth/calendar.events (or calendar.events.readonly for read-only connections)

Grant the subset needed for the actions you enable. API scopes do not override the connected user’s record permissions or vendor validation rules.

Available actions

Check availability; book, reschedule or cancel appointments through the workspace calendar connection. See Booking setup and receipts.

Verify before going live

Run Test connection and one read action against a known permitted record. Then test each intended write in an authorized sandbox. Check the provider’s own record and the Verbatik receipt. Publish the agent after assigning its tools. If a write has an unknown outcome, reconcile it with the vendor before trying again.

Vendor documentation

Verbatik documentation · Updated November 5, 2026