# Google Calendar

> Part of the NocoDB documentation (Product docs > Sync > App Sync > On Premise Auth Integration). Index of all pages: https://nocodb.com/llms.txt. Any docs page is available as Markdown by adding `.md` to its URL.

URL: https://nocodb.com/docs/product/sync/app-sync/on-premise-oauth/google-calendar
Last updated: 2026-10-03

Set up the Google Calendar OAuth2 authentication integration for a self-hosted NocoDB instance.

This document tells you how to set up the Google Calendar authentication integration for NocoDB.

## Environment Variables

To enable OAuth2 authentication with Google Calendar, set up these environment variables:

### Step 1: Create a Google OAuth Client

1. Log in to the [Google Cloud Console](https://console.cloud.google.com/).
2. Create a new project, or select an existing one.
3. Go to APIs & Services > Library.
4. Search for "Google Calendar API" and click "Enable".
5. Go to APIs & Services > OAuth consent screen and configure it:

* **App name**: Your application name (for example, "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`

6. Go to APIs & Services > Credentials.
7. Click "Create Credentials" > "OAuth client ID".
8. Fill in the form:

* **Application type**: Web application
* **Name**: Your application name (for example, "NocoDB")
* **Authorized redirect URIs**: The URL where Google sends users after authorization (for example, `https://your-nocodb-instance.com/`)

9. Click "Create".

### Step 2: Get Client ID and Client Secret

After you create the OAuth client, Google gives you:

* Client ID
* Client Secret

### Step 3: Set Environment Variables

Configure your NocoDB instance with these 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 that you specified when you created the OAuth client (for example, `https://your-nocodb-instance.com/api/v1/integrations/auth/google-calendar/callback`)

## OAuth Scopes

The Google Calendar integration requests these 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. Thus, calendar sync can refresh its access token between sync runs. Access is read-only. NocoDB never changes your calendar.

## Availability

* App Sync is available on **NocoDB Cloud** (Plus plan and above) and licensed self-hosted deployments (Business plan and above). This page covers OAuth app setup for **self-hosted** deployments. On NocoDB Cloud, these OAuth apps are preconfigured.

---

## Related pages

- [Bitbucket](https://nocodb.com/docs/product/sync/app-sync/on-premise-oauth/bitbucket.md): Set up the Bitbucket OAuth2 authentication integration for a self-hosted NocoDB instance.
- [GitHub](https://nocodb.com/docs/product/sync/app-sync/on-premise-oauth/github.md): Set up the GitHub OAuth2 or GitHub App authentication integration for a self-hosted NocoDB instance.
- [GitLab](https://nocodb.com/docs/product/sync/app-sync/on-premise-oauth/gitlab.md): Set up the GitLab OAuth2 authentication integration for a self-hosted NocoDB instance.
- [Linear](https://nocodb.com/docs/product/sync/app-sync/on-premise-oauth/linear.md): Set up the Linear OAuth2 authentication integration for a self-hosted NocoDB instance.
- [Outlook Calendar](https://nocodb.com/docs/product/sync/app-sync/on-premise-oauth/outlook-calendar.md): Set up the Outlook Calendar OAuth2 authentication integration for a self-hosted NocoDB instance.