Path: /docs/integrations

How Orchestrator connects to GitHub and related services.

GitHub sign-in (OAuth App)

Primary browser login.

1. Continue with GitHub on /login.
2. Callback URL (production):

text
https://getorchestrator.app/api/auth/callback/github

1. Env (Auth.js aliases preferred):

Variable	Role
AUTH_GITHUB_ID / AUTH_GITHUB_SECRET	Canonical Auth.js keys
GITHUB_CLIENT_ID / GITHUB_CLIENT_SECRET	Legacy aliases (still supported)
AUTH_URL	https://getorchestrator.app
AUTH_SECRET	Session signing secret

Scopes: read:user, user:email.

Google OAuth stays off unless AUTH_ENABLE_GOOGLE=true.

GitHub App (repos and webhooks)

Separate from login. Used for repository install, webhooks, and API access to linked repos.

Variable family	Role
GITHUB_APP_ID	App id
GITHUB_APP_CLIENT_ID / GITHUB_APP_CLIENT_SECRET	App OAuth (not login)
GITHUB_APP_WEBHOOK_SECRET	Webhook verification
GITHUB_APP_PRIVATE_KEY or key path	JWT for installation tokens

Do not point the login OAuth App and the GitHub App at conflicting callback settings without checking both consoles.

Typical webhook path:

text
https://getorchestrator.app/api/github/webhook

Slack / Jira / others

Product routes exist for selected integrations. Prefer MCP tools and project settings for day-to-day automation. Contact support if you need a connector enabled for your plan.

Related

• Getting Started (GitHub sign-in)
• MCP Server
• Repo engineering notes: docs/integrations/github-app.md, docs/auth-setup.md