Skip to main content
Self-hosted instances connect OAuth apps with your own credentials: you create an OAuth app with each provider, and OneCLI uses its client ID and secret. There are two ways to supply them:
  • Dashboard: enter the credentials when connecting the app. Values saved in the dashboard take precedence.
  • Environment variables: set the variables below on the container, and the app is ready to connect the moment the instance starts. This is the way to bake app configuration into your deployment.
Whichever way you configure an app, register its OAuth callback URL with the provider:
For example, https://onecli.internal.example.com/v1/apps/dropbox/callback. Per-provider setup is covered in the integration guides.

Available in both editions

One Google OAuth app serves all the Google integrations, and one Atlassian app serves Jira and Confluence. The same GOOGLE_* and ATLASSIAN_* values apply across their rows.

Enterprise edition only

These apps ship with the Enterprise all-in-one image:
One Microsoft Entra app registration serves all four Microsoft integrations; the same MICROSOFT_* values apply across their rows.

Dashboard configuration only

These OAuth apps don’t read environment variables yet. Enter their credentials in the dashboard when connecting:
  • Google Docs, Google Sheets, Google Slides, Google Forms, Google Meet, Google Photos, Google Tasks, Google Admin, Google Analytics, Google Classroom, Google Chat, Google Contacts
  • GitLab
  • X (Twitter)

No deploy-time credentials

Apps that authenticate with per-connection API keys, tokens, or roles need no app-level configuration. Users supply their credential when connecting in the dashboard: AWS, Cloudflare, Datadog, Fly.io, MongoDB Atlas, Resend, Vertex AI, and on Enterprise also Affinity and Granola.

Example

A slim deployment with Dropbox and the Google apps pre-configured adds the variables to the compose environment:
docker-compose.yml