Google Calendar

This document provides instructions for setting up the Google Calendar authentication integration for NocoDB.

Environment Variables

To enable OAuth2 authentication with Google Calendar, you need to set up the following environment variables:

Step 1: Create a Google OAuth Client

1. Log in to the Google Cloud Console
2. Create a new project or select an existing one
3. Navigate to APIs & Services > Library, search for "Google Calendar API" and click "Enable"
4. Navigate to APIs & Services > OAuth consent screen and configure it:

• App name: Your application name (e.g., "NocoDB")
• User support email and Developer contact information: Your contact email
• Add the scopes https://www.googleapis.com/auth/calendar.readonly and https://www.googleapis.com/auth/userinfo.email

5. Navigate to APIs & Services > Credentials
6. Click "Create Credentials" > "OAuth client ID"
7. Fill out the form:

• Application type: Web application
• Name: Your application name (e.g., "NocoDB")
• Authorized redirect URIs: The URL where Google will redirect users after authorization (e.g., https://your-nocodb-instance.com/)

8. Click "Create"

Step 2: Get Client ID and Client Secret

After creating the OAuth client, you'll be provided with:

• Client ID
• Client Secret

Step 3: Set Environment Variables

Configure your NocoDB instance with the following environment variables:

INTEGRATION_AUTH_GOOGLE_CALENDAR_CLIENT_ID=your_google_client_id
INTEGRATION_AUTH_GOOGLE_CALENDAR_CLIENT_SECRET=your_google_client_secret
INTEGRATION_AUTH_GOOGLE_CALENDAR_REDIRECT_URI=your_redirect_uri

Where:

• your_google_client_id: The Client ID from your Google OAuth client
• your_google_client_secret: The Client Secret from your Google OAuth client
• your_redirect_uri: The redirect URI you specified when creating the OAuth client (e.g., https://your-nocodb-instance.com/api/v1/integrations/auth/google-calendar/callback)

OAuth Scopes

This integration requests the following Google scopes:

• https://www.googleapis.com/auth/calendar.readonly: Read-only access to calendars and events
• https://www.googleapis.com/auth/userinfo.email: Read the email address of the connected account

The integration requests offline access so that calendar sync can refresh its access token between sync runs. Access is read-only; NocoDB never modifies your calendar.