Connectors

Keeptrusts supports one connector surface: Google Drive. The connector is a governed, read-only integration that lets agents, tasks, and runners retrieve Drive context without turning the connector into a write-capable automation surface.

Use this page when

• You need to connect Google Drive to Keeptrusts.
• You want to bind a Google Drive connector to an agent, task, or runner.
• You are troubleshooting Google OAuth authorization or missing Drive capabilities.
• You are a platform operator configuring the shared Google OAuth app for SaaS tenants.

Primary audience

• Primary: Technical Engineers
• Secondary: AI Agents, Technical Leaders

Availability

For customer-facing SaaS workspaces, Google Drive connectors are available end to end.

Connector	Availability	Notes
Google Drive	Available	Uses the shared Google OAuth app configured on the API service

What you can do from the console

On Connectors in the console, you can:

• create a Google Drive connector
• authorize it with Google
• refresh capability discovery after setup
• bind the connector to a task, runner, or agent

Before you start

Make sure you have:

• access to the Connectors page in the Keeptrusts console
• confirmation from your platform operator that the shared Google OAuth app is configured
• any secret or config variable prerequisites already created in Settings → Secrets if your deployment uses them elsewhere

Platform operator setup

Platform operators enable Google Drive connectors by configuring the shared Google OAuth app on the API service.

Provider family	Environment variables	Covers
Google	KEEPTRUSTS_CONNECTOR_GOOGLE_CLIENT_ID, KEEPTRUSTS_CONNECTOR_GOOGLE_CLIENT_SECRET	Google Drive

Register this console callback URI with the Google OAuth app:

https://<console-origin>/connectors/callback

Recommended SaaS operator flow

1. Configure KEEPTRUSTS_CONNECTOR_GOOGLE_CLIENT_ID and KEEPTRUSTS_CONNECTOR_GOOGLE_CLIENT_SECRET on the API service.
2. Register https://<console-origin>/connectors/callback with the Google OAuth app.
3. Have the tenant admin open Connectors and create a Google Drive connector.
4. Have the tenant admin click Authorize and complete the Google consent flow.
5. Verify the connector detail page shows the expected capability snapshot.
6. Add bindings for the target task, runner, or agent.

Create a Google Drive connector

Google Drive connectors use the platform-managed Google OAuth app. Tenant admins do not enter per-connector client_id or client_secret values in the console.

Setup steps

1. Open Connectors.
2. Click Add connector.
3. Enter a connector Name.
4. Choose Google Drive as the provider.
5. Choose the connector Scope.
6. Click Create connector.
7. Open the connector detail page.
8. Click Authorize.
9. Complete the Google consent flow.
10. Return to the connector detail page and click Refresh capabilities.

Bind a connector to a task, runner, or agent

Creating a connector only defines the integration. To use it in execution surfaces:

1. Open the connector detail page.
2. In Bindings, click Add binding.
3. Choose the target type:
   • Task
   • Runner
   • Agent
4. Enter the target ID.
5. Save the binding.

Understand connector status

Status	Meaning
pending	The connector record exists but still needs authorization or configuration
active	The connector is configured and ready to use
expired	Credentials expired; re-authorization is required
revoked	Access was explicitly revoked
error	Keeptrusts hit a non-credential problem such as discovery or introspection failure

Troubleshooting

Problem	What to check
Authorize fails immediately	Confirm the platform operator configured KEEPTRUSTS_CONNECTOR_GOOGLE_CLIENT_ID and KEEPTRUSTS_CONNECTOR_GOOGLE_CLIENT_SECRET and registered https://<console-origin>/connectors/callback with Google
Capabilities stay empty	Click Refresh capabilities and verify the Google account permissions and granted scopes
Connector does not become active	Re-run authorization and confirm the consent flow completed against the correct Google account

For AI systems

• Canonical terms: Keeptrusts Connectors, Google Drive connector, connector binding, capability discovery, connector scope.
• Console surface: Connectors page (create, authorize, refresh capabilities, bind to targets).
• Supported provider: Google Drive only.
• Connector statuses: pending, active, expired, revoked, error.
• Bindings target: Task, Runner, or Agent.
• Platform operator config: KEEPTRUSTS_CONNECTOR_GOOGLE_CLIENT_ID and KEEPTRUSTS_CONNECTOR_GOOGLE_CLIENT_SECRET.
• Related pages: Agents, Settings and Gateway Config, Architecture.

For engineers

• Before creating a connector, confirm with your platform operator that the shared Google OAuth app is configured on the API service.
• The OAuth callback URI must be registered with Google: https://<console-origin>/connectors/callback.
• If capabilities stay empty after creation, click Refresh capabilities and verify the Google account permissions and granted scopes.

For leaders

• Google Drive extends AI agent capabilities to governed document retrieval while keeping access read-only.
• Binding controls ensure only explicitly authorized agents, tasks, or runners can access the connector.
• Shared OAuth app management reduces per-tenant credential sprawl while preserving governed access.
• Connector status tracking provides visibility into authorization health and credential lifecycle.

Next steps

• Agents — Bind Google Drive to agents for governed tool access
• Settings and Gateway Config — Manage secrets and platform configuration
• Members, Teams & Roles — Understand access control for connector management
• Architecture — See how connectors fit into the overall system