Google-Drive authentication
This page documents the authentication and configuration options for the Google-Drive agent connector.
Authentication
Open source execution
In open source mode, you provide API credentials directly to the connector.
OAuth
credentials fields you need:
| Field Name | Type | Required | Description |
|---|---|---|---|
access_token | str | No | Your Google OAuth2 Access Token (optional, will be obtained via refresh) |
refresh_token | str | Yes | Your Google OAuth2 Refresh Token |
client_id | str | No | Your Google OAuth2 Client ID |
client_secret | str | No | Your Google OAuth2 Client Secret |
Example request:
from airbyte_agent_google_drive import GoogleDriveConnector
from airbyte_agent_google_drive.models import GoogleDriveAuthConfig
connector = GoogleDriveConnector(
auth_config=GoogleDriveAuthConfig(
access_token="<Your Google OAuth2 Access Token (optional, will be obtained via refresh)>",
refresh_token="<Your Google OAuth2 Refresh Token>",
client_id="<Your Google OAuth2 Client ID>",
client_secret="<Your Google OAuth2 Client Secret>"
)
)
Token
This authentication method isn't available for this connector.
Hosted execution
In hosted mode, you first create a connector via the Airbyte API (providing your OAuth or Token credentials), then execute operations using either the Python SDK or API. If you need a step-by-step guide, see the hosted execution tutorial.
OAuth
Create a connector with OAuth credentials.
credentials fields you need:
| Field Name | Type | Required | Description |
|---|---|---|---|
access_token | str | No | Your Google OAuth2 Access Token (optional, will be obtained via refresh) |
refresh_token | str | Yes | Your Google OAuth2 Refresh Token |
client_id | str | No | Your Google OAuth2 Client ID |
client_secret | str | No | Your Google OAuth2 Client Secret |
replication_config fields you need:
| Field Name | Type | Required | Description |
|---|---|---|---|
folder_url | str | Yes | URL for the Google Drive folder you want to sync (e.g., https://drive.google.com/drive/folders/YOUR-FOLDER-ID) |
streams | str | Yes | Configuration for file streams to sync from Google Drive |
Example request:
curl -X POST "https://api.airbyte.ai/api/v1/integrations/connectors" \
-H "Authorization: Bearer <YOUR_BEARER_TOKEN>" \
-H "Content-Type: application/json" \
-d '{
"customer_name": "<CUSTOMER_NAME>",
"connector_type": "Google-Drive",
"name": "My Google-Drive Connector",
"credentials": {
"access_token": "<Your Google OAuth2 Access Token (optional, will be obtained via refresh)>",
"refresh_token": "<Your Google OAuth2 Refresh Token>",
"client_id": "<Your Google OAuth2 Client ID>",
"client_secret": "<Your Google OAuth2 Client Secret>"
},
"replication_config": {
"folder_url": "<URL for the Google Drive folder you want to sync (e.g., https://drive.google.com/drive/folders/YOUR-FOLDER-ID)>",
"streams": "<Configuration for file streams to sync from Google Drive>"
}
}'
Bring your own OAuth flow
To implement your own OAuth flow, use Airbyte's server-side OAuth API endpoints. For a complete guide, see Implement your own OAuth flow.
Step 1: Initiate the OAuth flow
Request a consent URL for your user.
| Field Name | Type | Required | Description |
|---|---|---|---|
customer_name | string | Yes | Your unique identifier for the customer |
connector_type | string | Yes | The connector type (e.g., "Google-Drive") |
redirect_url | string | Yes | URL to redirect to after OAuth authorization |
Example request:
curl -X POST "https://api.airbyte.ai/api/v1/integrations/connectors/oauth/initiate" \
-H "Authorization: Bearer <YOUR_BEARER_TOKEN>" \
-H "Content-Type: application/json" \
-d '{
"customer_name": "<CUSTOMER_NAME>",
"connector_type": "Google-Drive",
"redirect_url": "https://yourapp.com/oauth/callback"
}'
Redirect your user to the consent_url from the response. After they authorize, they'll be redirected back to your app with a secret_id query parameter.
Step 2: Create a connector with the secret ID
| Field Name | Type | Required | Description |
|---|---|---|---|
customer_name | string | Yes | Your unique identifier for the customer |
connector_type | string | Yes | The connector type (e.g., "Google-Drive") |
name | string | Yes | A name for this connector instance |
server_side_oauth_secret_id | string | Yes | The secret_id from the OAuth callback |
replication_config.folder_url | str | Yes | URL for the Google Drive folder you want to sync (e.g., https://drive.google.com/drive/folders/YOUR-FOLDER-ID) |
replication_config.streams | str | Yes | Configuration for file streams to sync from Google Drive |
Example request:
curl -X POST "https://api.airbyte.ai/api/v1/integrations/connectors" \
-H "Authorization: Bearer <YOUR_BEARER_TOKEN>" \
-H "Content-Type: application/json" \
-d '{
"customer_name": "<CUSTOMER_NAME>",
"connector_type": "Google-Drive",
"name": "My Google-Drive Connector",
"server_side_oauth_secret_id": "<secret_id_from_callback>",
"replication_config": {
"folder_url": "<URL for the Google Drive folder you want to sync (e.g., https://drive.google.com/drive/folders/YOUR-FOLDER-ID)>",
"streams": "<Configuration for file streams to sync from Google Drive>"
}
}'
Token
This authentication method isn't available for this connector.
Execution
After creating the connector, execute operations using either the Python SDK or API.
If your Airbyte client can access multiple organizations, include organization_id in AirbyteAuthConfig and X-Organization-Id in raw API calls.
Python SDK
from airbyte_agent_google_drive import GoogleDriveConnector, AirbyteAuthConfig
connector = GoogleDriveConnector(
auth_config=AirbyteAuthConfig(
customer_name="<your_customer_name>",
organization_id="<your_organization_id>", # Optional for multi-org clients
airbyte_client_id="<your-client-id>",
airbyte_client_secret="<your-client-secret>"
)
)
@agent.tool_plain # assumes you're using Pydantic AI
@GoogleDriveConnector.tool_utils
async def google_drive_execute(entity: str, action: str, params: dict | None = None):
return await connector.execute(entity, action, params or {})
API
curl -X POST 'https://api.airbyte.ai/api/v1/integrations/connectors/<connector_id>/execute' \
-H 'Authorization: Bearer <YOUR_BEARER_TOKEN>' \
-H 'X-Organization-Id: <YOUR_ORGANIZATION_ID>' \
-H 'Content-Type: application/json' \
-d '{"entity": "<entity>", "action": "<action>", "params": {}}'