## Google Meet integration Integrating Google Meet with Frontegg allows your application to create and manage meeting spaces, access conference records, retrieve participant data, and work with recordings and transcripts — all through Frontegg's integration layer using OAuth 2.0. Prerequisites - A Google account with access to [Google Cloud Console](https://console.cloud.google.com/) - A Google Cloud project (you can create one during setup) ### Enable the Google Meet API #### Step 1: Open the Google Meet API in the API library Go to the [Google Meet REST API](https://console.cloud.google.com/apis/library/meet.googleapis.com) page in the Google Cloud Console. Select your project from the top navigation, then click **Enable** if the API is not yet enabled. If you see **Manage** and **API Enabled**, the API is already active. ![Google Meet REST API page](/assets/google-meet-1.272f49150174cb4aa5a4c7b457e0edcc4bb065797e496a0dca414a340ad7f912.1ce25488.png) ### Create an OAuth client #### Step 2: Go to the Credentials page In the left sidebar, navigate to **APIs & Services** → **Credentials**. Click **Create credentials**. ![Credentials page with Create credentials button highlighted](/assets/google-meet-2.ded5ceaee2411123052fffc7c71cdc967ddaf5841e03d3b29f374173f1a2333d.1ce25488.png) #### Step 3: Select OAuth client ID From the dropdown, select **OAuth client ID**. ![Create credentials dropdown with OAuth client ID highlighted](/assets/google-meet-3.7fb4c0f15ea5a021fa434609bf98b81de09162cb2f229320733e0069a0696eef.1ce25488.png) #### Step 4: Configure the OAuth client On the **Create OAuth client ID** page: 1. Set **Application type** to **Web application**. 2. Enter a name for the client (for example, `Frontegg Google Meet Integration`). 3. Under **Authorized redirect URIs**, click **Add URI** and add both of the following: - `https://YOUR_MCP_GATEWAY_URL/integration-callback` ![OAuth client form with redirect URIs filled in](/assets/google-meet-4.0e9c6d90f44ec581c85053dc105da42ea1d7db8a32890e58507a3f6ff22703ca.1ce25488.png) #### Step 5: Create the client Click **Create** to save the OAuth client. ![OAuth client form with Create button highlighted](/assets/google-meet-5.8cf2836ee7602b0b3d416805283f68aceef388fd6b82797e3ef3c0bb46b01dd1.1ce25488.png) ### Copy your credentials #### Step 6: Copy the Client ID and Client Secret After clicking **Create**, a dialog displays your **Client ID** and **Client Secret**. Copy both values and store them securely. Save your Client Secret now The Client Secret is only shown once in this dialog. After you close it, you cannot retrieve it again — you can only create a new secret. ![OAuth client created dialog showing Client ID and blurred Client Secret](/assets/google-meet-6.e41cff058b9734d6b4f2c5d6d4e282f1948ae7f4a17135d70aa7d37b09d6aefe.1ce25488.png) You can also view your Client ID at any time by clicking the client name in the **Clients** list. ![OAuth client detail page showing Client ID](/assets/google-meet-7.cfe265bfdcaa1199ff81cb1e961adf14b17fb36abb8f8b73c5917997f29cc783.1ce25488.png) ### Configure the Frontegg portal Once you have your **Client ID** and **Client Secret**, enter them in the Frontegg portal: 1. Open the **Frontegg portal** and navigate to [ENVIRONMENT] → Integrations → Google Meet. 2. Enter the **Client ID** and **Client Secret** in the corresponding fields. 3. Select the required **scopes**: | Scope | Description | | --- | --- | | `https://www.googleapis.com/auth/meetings.space.readonly` | Read access to meeting spaces and conference records | | `https://www.googleapis.com/auth/meetings.space.created` | Create and manage app-created meeting spaces | 1. Click **Save**. Keep your credentials secure Never share or commit your Client Secret to version control. ### Additional resources - [Google Meet REST API documentation](https://developers.google.com/meet/api/reference/rest) - [Google Cloud Console](https://console.cloud.google.com/) - [Setting up OAuth 2.0](https://developers.google.com/identity/protocols/oauth2/) - [How to get your Redirect URL](/agen-for-work/connectors/redirect-url)