{/* Generated by scripts/generate-integration-catalog.mjs. Do not edit by hand. */}
At a glance
- Availability: Enabled by default.
- Authentication: OAuth 2.0.
- Connection: A user authorizes the connection in the provider's consent screen.
- Scopes:
https://www.googleapis.com/auth/calendar.readonly,https://www.googleapis.com/auth/calendar.events.
Credentials
Set these per environment. See Connect an integration.
These variables are required only when you supply your own OAuth app. If a managed app is available, you can connect without setting them. Provider permissions and consent still apply.
Setup
- Choose who owns the Google OAuth app: On hosted Veryfront, Google Calendar uses the Veryfront-managed Google OAuth app: connect Google Calendar from the project's integrations and approve the Google consent screen, no environment variables needed. Set GOOGLE_CLIENT_ID and GOOGLE_CLIENT_SECRET only to use your own Google OAuth app, which is required for local and self-hosted runs.
- Enable the Google Calendar API: In the Google Cloud project that owns your OAuth app, enable the Google Calendar API.
- Configure the OAuth consent screen: Configure the consent screen and add the scopes this connector requests. While the app's publishing status is Testing, only the test users you list can authorize it, and Google expires their refresh tokens after 7 days, so they must reconnect weekly. Publishing the app to external users requires Google's OAuth app verification for these sensitive scopes.
- Create an OAuth client: Create an OAuth client ID of type Web application. Add the redirect URI of the environment that completes the flow: https://api.veryfront.com/oauth/callback/calendar for hosted Veryfront, or your app origin followed by /api/auth/calendar/callback for a local or self-hosted app. Set GOOGLE_CLIENT_ID and GOOGLE_CLIENT_SECRET from the app's credentials.
- Verify access: Run List Calendars (read-only). It returns the calendars of the connected Google account without changing them.
Provider notes
- The connection requests https://www.googleapis.com/auth/calendar.readonly and https://www.googleapis.com/auth/calendar.events. calendar.readonly covers the read tools; calendar.events lets the write tools create, update and delete events.
- Tools that create, update, send or delete data are marked as writes and need write authority; the other tools are read-only.
Tools
Verify the connection
Call a read tool such as calendar__list_calendars with arguments for your account. Confirm that the result comes from the intended account or workspace before enabling write tools.