OAuth Ready
← Guide library

OAuth launch guide

Google Calendar

Read customer event details for a meeting assistant

Researched draftChecked Oct 21, 2026Provider website ↗

At a glance

High difficulty

Event-content access is sensitive for external production and can require Google verification and public product assets.

Start hereDecide whether the assistant needs event details or only free/busy availability.
Hands-on effort
Not measured
External wait
Typically 3–5 business days when sensitive-scope verification applies
Main blocker
Missing verified domain, privacy policy, or scope justification.

01

Scenario this guide covers

AudienceExternal Google users in production

Registration pathDeveloper-owned web OAuth client

  • The assistant needs event details, not only free/busy availability
  • The product will move beyond a test-user-only experiment

02

Choose managed or custom

Available through ComposioOfficial source

Composio documents a managed Google Calendar OAuth2 toolkit. Confirm its exact supported scopes for this feature.

Choose custom when: Use a custom client when you need your own consent identity, scopes, or provider submission.

03

Before you start

01

Google Cloud project and appropriate project accessAlways

Developer
02

Product homepage, privacy policy, and verified domainExternal production verification

Developer
03

Named test usersWhile the app is in external testing

Developer
04

Scope explanation and demonstration videoWhen verification is required

Developer

04

Permissions in plain language

calendar.events.readonly

Read event detailsMatches the example assistant that needs titles, times, and other event content.

SensitiveSource ↗
calendar.freebusy

Read availability windowsA narrower alternative if the feature only schedules around busy times.

Narrower alternativeSource ↗

05

Your setup path

1
Developer + agent

Choose the narrowest feature

Avoid event-content access when free/busy is enough.

Write down the exact Calendar data the assistant must use and choose the corresponding scope.

Expected result: A justified minimal scope set.Open official page ↗Official source · Google
2
Developer

Prepare identity and audience

Configure a truthful consent experience and testing audience.

Configure branding, audience, data access, and test users in Google Auth Platform.

Expected result: A consent configuration ready for a test client.Open official page ↗Official source · Google
3
Developer

Create the web client

Create the correct client once with the exact callback.

Create a web OAuth client, decide the AI-powered agent designation, and add the exact redirect URI.

Expected result: A client ID; the AI-agent choice cannot be changed later according to the current guide.Open official page ↗Official source · Google
4
Developer

Test with an allowed user

Verify consent and the representative Calendar call.

Authorize a listed test user and exercise the intended Calendar operation.

Expected result: A recorded test outcome. This project has not observed it yet.Open official page ↗Official source · Google
5
Developer → Google

Submit verification

Provide the evidence Google requests for applicable external production access.

Submit domain, policy, scope justification, and demonstration evidence when the scenario requires verification.

Expected result: A review decision or a request for follow-up from Google.Open official page ↗Official source · Google

06

Review and waiting

RequirementConditional provider verification
Decision ownerGoogle
Published / known waitTypically 3–5 business days according to Google; not guaranteed

External production use requests sensitive Calendar event-content access and no exception applies.

Prepare this evidence

  • Verified domain and product identity
  • Public homepage and privacy policy
  • Scope justification
  • Demonstration video

07

When you get blocked

A test user cannot authorize.+

Likely cause: Audience or test-user configuration may not include that account.

Recovery: Check the app audience and test-user list.

Official help ↗
Verification cannot be submitted or is returned.+

Likely cause: Domain, policy page, or scope evidence may be incomplete.

Recovery: Work through Google’s policy compliance and sensitive-scope checklists.

Official help ↗

08

Who does what

Agent

Can prepare

  • Compare Calendar scopes
  • Draft consent copy, justification, and evidence checklist
You

Must complete

  • Own the Cloud project and domain
  • Configure credentials and test consent
  • Publish accurate policy pages and submit
Provider

Decides

  • Google decides verification
  • Each end user decides consent

09

Sources and limits

01

Choose Google Calendar API scopesGoogle · checked 2026-10-21

↗02

Configure OAuth consentGoogle · checked 2026-10-21

↗03

Create access credentialsGoogle · checked 2026-10-21

↗04

Sensitive scope verificationGoogle · checked 2026-10-21

↗
What we did not verify
  • No Google Cloud client, consent flow, or verification request was completed by this project.
  • The published review range is conditional and not a total launch estimate.