Article

How to create a Google Meet Connector

•

June 4, 2025

•

10 min read

Summarize this article with:

One of the most powerful features of Airbyte is the ability to create connectors to any source or destination. You have a number of options on how to achieve this: no code with the AI Assistant, low code with Connector Builder, or custom code when you have an extremely complex use case. I was recently working with a customer who required access to transcripts from Google Meet. After a quick search of the Connector marketplace, I found a Google Calendar connector, but no Google Meet.

No problem, let me show you how you can use the Connector Builder to create it.

Google Calendar API vs. Google Meet API

Google provides APIs for both Calendar and Meet. If you need conference information such as meeting link and invitees, you can use the Google Calendar API and include a record filter to only return meetings that have conference data. I extended the existing Google Calendar Connector to this:

If you need transcripts, recordings, and meeting attendees, these are available via the Google Meet APIs. Keep in mind, that transcripts and recordings are only available in Google Workspaces. In other words, if you are using gmail, you will not have access to transcripts.

Google Calendar and Google Meet work within different authentication scopes. If you need both, meeting information such as conference link and invitees, AND transcripts, you will need two different connectors defined in Airbyte with the appropriately scoped refresh token. I’ll cover how to set this up for Google Meet below. Google Calendar works the same way, just with a different scope. If you would like a tutorial on this, leave a comment below and I will create one.

Google App Authentication

Before we jump into creating the connector, we need to set up your Google Cloud project. Here are the steps:

Create a Project, if you don’t have one already. I called mine AirbyteConnector
From the left hand menu, or Google Cloud home, select API & Services and add the Google Meet API

Tap on OAuth Content Screen and follow the configuration steps. Keep in mind that this app will be in test mode for now.
Add users who can access your test app
Add Google Meet API perms

Now that you app is set up, you will need a few values that we will input into the Google Meet Connector shortly: Client ID, Client Secret, Refresh Token. Within Google Cloud console, navigate to API & Services > Credentials, tap Create Credentials and choose OAuth Client ID, using the following values:

Application Type: Web Application
Name: Google Meet Connector
Authorized redirect URIs: http://localhost

You will then be presented with a dialog box with your Client ID and Secret. Copy these to a secure location.

Next, you need to use your client id and secret to retrieve the refresh token. Refresh tokens are scoped to APIs in Google Cloud. In this instance, we want the scope to be for Google Meet. Looking at the docs, this scope should be https://www.googleapis.com/auth/meetings.space.readonly

To save some time, I created a shell script to assist with the refresh token. Save the code locally to a file, get-meet-refresh-token.sh, changing the values of client id and secret to those retrieve above.



# === CONFIGURATION ===
CLIENT_ID="your-client-id-here"
CLIENT_SECRET="your-client-secret-here"
REDIRECT_URI="http://localhost"
SCOPE="https://www.googleapis.com/auth/meetings.space.readonly"

# === STEP 1: Show Auth URL ===
AUTH_URL="https://accounts.google.com/o/oauth2/v2/auth?response_type=code&client_id=$CLIENT_ID&redirect_uri=$REDIRECT_URI&scope=$SCOPE&access_type=offline&prompt=consent"

echo "👉 Open this URL in your browser and authorize access:"
echo "$AUTH_URL"
echo ""
read -p "📥 Paste the authorization code (from the ?code=... part of the URL): " AUTH_CODE

# === STEP 2: Exchange Code for Tokens ===
echo ""
echo "🔄 Requesting access and refresh token..."

RESPONSE=$(curl -s \
  --request POST \
  --url https://oauth2.googleapis.com/token \
  --header "Content-Type: application/x-www-form-urlencoded" \
  --data "code=$AUTH_CODE" \
  --data "client_id=$CLIENT_ID" \
  --data "client_secret=$CLIENT_SECRET" \
  --data "redirect_uri=$REDIRECT_URI" \
  --data "grant_type=authorization_code")

echo ""
echo "🎉 Response:"
echo "$RESPONSE" | jq .
~

Once you have changed the CLIENT_ID and CLIENT_SECRET, execute it via the command line:



$ ./get-meet-refresh-token.sh

Google Meet Connector

Now that the authentication is set up, it’s time to create the custom connector in Airbyte using the Connector Builder.

Navigate to Builder and tap New Custom Connector, then choose start from scratch, calling it Google Meet. If you want to save some time, you can paste in my yaml definition rather than following each step.

Add the following Inputs. You can add the values obtained earlier.

Client ID
Client Secret
Refresh Token
Conference Record (optional)

Add the following Global Configuration:

API Base URL: https://meet.googleapis.com/v2/
Authentication
- OAuth (legacy)
- Token Refresh Endpoint: https://oauth2.googleapis.com/token
- Grant Type: refresh_token

Set up your streams:

Recordings:
- URL Path: conferenceRecords
- HTTP Method: GET
- HTTP Response Format: JSON
- Primary Key: id
Transcripts
- URL Path: conferenceRecords/{{ config['conferencerecord'] }}/transcripts
- HTTP Method: GET
- HTTP Response Format: JSON
- Primary Key: id

That’s it. You can now easily retrieve transcripts and recordings via Airbyte for Google Meet conferences. Grab the yaml manifest if you want to try it out yourself.

‍

Limitless data movement with free Alpha and Beta connectors

Introducing: our Free Connector Program ->