OAuth Credentials
Trinity exposes a small OAuth2 helper API for four providers — Google, Slack, GitHub, and Notion — that builds a provider authorization URL from client credentials configured on the backend. It does not complete the OAuth exchange for you: the practical way to give an agent a provider token today is to obtain it yourself and inject it as a credential.
How It Works
An admin sets the provider's client credentials as backend environment variables: GOOGLE_CLIENT_ID / GOOGLE_CLIENT_SECRET, SLACK_CLIENT_ID / SLACK_CLIENT_SECRET, GITHUB_CLIENT_ID / GITHUB_CLIENT_SECRET, NOTION_CLIENT_ID / NOTION_CLIENT_SECRET. A provider with no client ID is reported as not configured.
POST /api/oauth/{provider}/init returns the provider's authorization URL (with a state value) for the scopes Trinity requests: Google openid email profile plus Drive, GitHub repo user, Slack chat:write channels:read, Notion none.
Open that URL and approve access. The URL names /api/oauth/{provider}/callback on your backend as its redirect target.
That callback route does not exist — the redirect lands on a 404 — and there is no OAuth button in an agent's Settings › Credentials pane, so approving access is not turned into a stored token. Once you hold a provider token, add it to the agent through Settings › Credentials — as KEY=VALUE in .env, where the agent's .mcp.json.template picks it up through ${VAR} placeholders.
Google sign-in links from inside an agent
Some tools an agent runs sign in to Google with a desktop-style flow: they print a Google consent link and listen on a local 127.0.0.1port for the redirect. Trinity's credential sanitizer, which scrubs secrets out of chat replies, logs and execution records, leaves such a link intact so you can open it and approve access.
Only a strictly shaped link is kept: an https://accounts.google.com/o/oauth2/... authorization URL with response_type=code, a *.apps.googleusercontent.com client ID, Google scopes, and a redirect_uri of http://127.0.0.1:<port>/oauth2/callback. Any link carrying a known secret pattern or one of the agent's own credential values is still redacted, as is an OAuth callback or token. Treat the link like any sign-in link: its statevalue belongs to your consent flow, so don't paste it into a public channel.
Platform-level Slack installation is a separate, complete OAuth flow: Install to Workspace on the Slack Integration settings section — see Slack Integration.
For Agents
| Endpoint | Method | Description |
|---|---|---|
| /api/oauth/providers | GET | The four providers, whether each is configured, and the scopes Trinity would request |
| /api/oauth/{provider}/init | POST | Build the provider's authorization URL; 400 for an unknown provider, 500 when its client ID is not set |
Agents do not call these endpoints. Provider tokens reach an agent as injected credentials, resolved into .mcp.json at runtime.