Skip to main content
An integration connects an external service so agent tools can act on it — read a Drive folder, send an Outlook mail, list Teams chats.
This is not how users sign in. Signing in with an identity provider belongs to a commercial edition and is absent from the open-source build, which authenticates with email and password. See Editions.
Integrations screen showing GitHub, Outlook, Teams, OneDrive, SharePoint, Google Drive, Gmail and Google Calendar

The integrations screen — eleven services, none connected yet.

​
Connecting a workspace integration

1

Get the authorisation URL

GET /api/integrations/{provider}/{service}/connect
2

User consents

On the provider’s consent screen.
3

Provider redirects back

POST /api/integrations/{provider}/callback
4

Tokens are stored encrypted

In the integrations table, encrypted with ENCRYPT_KEY.
Agent tools then use those tokens transparently.

​
Supported services

Eleven services can be connected. Scopes are requested per service — gmail.readonly, drive.readonly, Mail.Read, Files.ReadWrite, repo, and so on — so an agent only ever receives what its service needs.

​
Endpoints

Related topics

IntegrationsList IntegrationsDisconnect IntegrationConfigurationOdoo Connect