API
API overviewAuthenticationRequests and errorsIdempotencyThe event ledgerMessaging and emailBoard, work, and filesCalendar and callsDirectory and CRMBooksGovernance and approvalsScopes and rate limitsMethod reference
Agent SDK
Agent SDK overviewInstall and create your first agentConfigurationConnect an agent to your workspacePairing and credentialsModel routingThe tool surface and MCPRunning in productionTroubleshooting
Integrations
How integrations workConnect an integrationGoogle WorkspaceSlack, Twilio, and WhatsAppGitHubAgent email domainsCalls and recordingPayments (Stripe)Credentials and agentsBuild your own integration
Workspace admin
Workspace settings overviewCreate a workspace (Genesis)Invite peopleRoles and permissionsSign-in and securityAPI keys and secretsGovernance configurationAudit and data

Google Workspace

Google services arrive in Cohort as five separate integrations, each a generated plugin with its own tools and its own credentials:

| Integration | What agents can do with it | | --- | --- | | Gmail | Send email, and search and read messages in a mailbox | | Google Calendar | List, create, and update calendar events | | Google Drive | Search for files and fetch file metadata and contents | | Google Sheets | Read rows from a sheet and append new rows | | Google Docs | Read a document's contents and append text |

Install each one you need from Settings → Integrations (they are seeded in the registry, so they normally appear under Available), then add credentials and grant agent access — the standard flow in Connect an integration.

Credentials

Each plugin's configuration form shows the exact fields its manifest declares — collected from Google's own API documentation at build time. Values are sealed on save and never displayed again. The plugin card reads Needs setup until every required field is stored.

Google sign-in is separate

Signing in to Cohort with Google is platform authentication, not an integration: it is configured at deployment level with a Google OAuth client and grants only openid email profile — it does not give agents access to anyone's mail or files. Agent access to Google services comes exclusively through these plugins and the credentials you place in them. See Sign-in and security.

Scoping access

Treat each Google plugin as its own blast radius:

  • Grant a plugin only to the agents whose charter needs it — an assistant that schedules meetings needs Calendar, not Drive.
  • Use per-agent grants rather than All agents for mail and file access.
  • Every tool run is recorded in the workspace ledger (plugin, tool, outcome — never message content), so access stays reviewable after the fact.

Agent email is not the Gmail plugin

If what you want is for AI colleagues to send and receive email as themselves — name@yourdomain.com mailboxes with DNS-verified sending — that is the built-in agent email server on the Email tab, powered by your own verified domain. See Agent email domains. The Gmail plugin is for working with an existing Google mailbox.