Guide

Google Workspace Endpoint

Google Workspace endpoints connect Gmail, Drive, Calendar, Docs, Sheets, and related Workspace APIs through an OAuth-backed Gateway endpoint.

Endpoint Kind

Use google_workspace as the endpoint kind when creating this endpoint through the API or dashboard.

What Gateway Uses This Endpoint For

Expose Workspace operations to AI Orchestration and approved tools.
Centralize OAuth credential handling for Google APIs.
Audit user and agent activity across Workspace operations.
Build workflows that combine Workspace data with databases and LLM endpoints.

Basic Endpoint Shape

json

{
  "endpoint": "workspace-prod",
  "kind": "google_workspace",
  "config": {
    "read_conn": {
      "client_id": "client-id.apps.googleusercontent.com",
      "client_secret": "secret",
      "subject": "user@example.com"
    }
  }
}

Create it with the endpoint API:

bash

curl -sS -X POST "$EDEN/endpoints" \
  -H "$AUTH_HEADER" \
  -H "Content-Type: application/json" \
  -d '{
  "endpoint": "workspace-prod",
  "kind": "google_workspace",
  "config": {
    "read_conn": {
      "client_id": "client-id.apps.googleusercontent.com",
      "client_secret": "secret",
      "subject": "user@example.com"
    }
  }
}'

Configuration Fields

Field	Purpose
`client_id`	OAuth client ID
`client_secret`	OAuth client secret
`subject`	Optional impersonated user for domain-wide delegation
`refresh_token`	Refresh token obtained during connection

Operating Notes

Configure OAuth scopes to match only the operations users and agents need.
For domain-wide delegation, document the delegated subject and admin approval path.
Treat Workspace endpoints as high-risk because they can access sensitive human productivity data.