Last updated July 24, 2026
Integrations Reference
Integrations are how you authorize the tools your team already uses — documentation, trackers, observability, your model provider — once, at the org level, so the rest of the platform can reach them.
You'll find all integration settings under Settings → Integrations in your organization.
A connector is not the same thing as a source. This page covers connectors — the credentials your org authorizes once in Settings. Whether you can then add that system as a source on a board is a separate question, and the answer isn't always yes. Some connectors feed other parts of the platform instead (OpenRouter powers chat; Sentry and LogRocket feed /monitor), and some are connectable while their source type is still on the way. The Adds sources? column below tells you which is which, and the Sources Overview is the authority on what you can bind to a board today.
Supported connectors
| Provider | Auth | Category | Adds sources? | What it provides |
|---|---|---|---|---|
| Confluence | OAuth 2.0 (user) | Documentation | Yes | Spaces, pages, content search |
| Jira | OAuth 2.0 (user) | Project Management | Yes | Projects, issues, issue search |
| Notion | OAuth 2.0 (org) | Documentation | Yes | Databases, pages, content search |
| GitHub | OAuth 2.0 (user) | Code Repository | Source type coming soon | Repos, files, code search, directory trees |
| Google Docs | OAuth 2.0 (user) | Documentation | Source type coming soon | Documents, document search via Google Drive |
| Slack | OAuth 2.0 (org) | Communication | Source type coming soon | Channels, message history, message search |
| Terraform | API Key (org) | Infrastructure | Source type coming soon | Workspaces, state files, runs, plan output |
| OpenRouter | OAuth 2.0 PKCE (org) | LLM Provider | No — powers Chat | Model routing, chat completions, streaming |
| Sentry | API Key (org) | Observability | No — feeds /monitor | Projects, issues, error events |
| LogRocket | API Key (org) | Observability | No — feeds /monitor | Sessions, session replay, error tracking |
| Intercom | OAuth 2.0 (org) | Customer Support | No | Conversations, contacts, support articles |
Planning to point the GitHub connector at a codebase to understand it? Use Cdx Code instead — it analyses the repo locally and pushes a real architecture graph. The GitHub connector reads repo content (READMEs, docs); it doesn't map architecture.
Auth methods
There are three authentication patterns used across providers:
Standard OAuth 2.0 redirects you to the provider to authorize access. You'll see a consent screen, approve the scopes, and get redirected back. The platform stores encrypted tokens on your behalf.
- User-scoped providers (GitHub, Confluence, Jira, Google Docs): each team member connects their own account, so everyone sees only the resources they personally have access to.
- Org-scoped providers (Slack, Notion, Intercom): a single org-wide token is shared across your organization. One person connects it and everyone benefits.
Token scope
| Scope | Meaning | Providers |
|---|---|---|
| User | Each user connects their own account | GitHub, Confluence, Jira, Google Docs |
| Org | One connection shared across the organization | Slack, Notion, Intercom, Sentry, LogRocket, OpenRouter, Terraform |
Org-scoped integrations only need to be set up once. User-scoped ones (like GitHub) need each team member to connect individually — this ensures everyone sees only the repos they have access to.
Connection status
Each integration can be in one of these states:
| Status | Meaning |
|---|---|
| Connected | Active and working |
| Disconnected | Not yet configured or manually disconnected |
| Expired | Token has expired — needs re-authorization |
| Needs re-auth | Provider revoked access or scopes changed |
| Error | Something went wrong — check logs |
Connect your first integration
Use this checklist to get your first provider wired up:
- Navigate to Settings → Integrations in your organization
- Choose a provider from the connector list above
- For OAuth providers: click Connect and complete the authorization flow
- For API Key providers: paste the token from the provider's dashboard
- Verify the status shows Connected in the integrations list
- Test by opening a board and referencing data from the connected source
Provider setup
GitHub setup
- Click Connect on the GitHub integration card.
- You'll be redirected to GitHub's OAuth consent screen.
- Approve the requested scopes (repo read access, code search).
- After redirect, your account is linked. Each team member repeats this for their own GitHub account.
- Once connected, chat can read repo content on your behalf. Adding a GitHub source to a board is still on the way — see the note above.
Confluence / Jira setup
- Click Connect on the Confluence or Jira card.
- Authorize via Atlassian's OAuth flow — both share the same Atlassian identity.
- Confluence provides: spaces, pages, and content search.
- Jira provides: projects, issues, and issue search.
- These are user-scoped — each team member connects their own Atlassian account.
Slack / Notion / Intercom setup
These are org-scoped OAuth providers. One team member connects the integration and it applies to the entire organization.
- Click Connect on the provider card.
- Authorize at the provider's consent screen.
- The org-wide token is stored and shared across all members.
- Slack gives you channels and message search. Notion gives you databases and pages. Intercom gives you conversations and support articles.
Sentry / LogRocket / Terraform setup (API key)
- Go to the provider's dashboard and generate an API key or auth token.
- Back in the portal, click Configure on the provider card.
- Paste the API key into the field and save.
- The key is encrypted at rest before storage.
- One key covers the whole organization.
OpenRouter setup (PKCE)
OpenRouter uses OAuth 2.0 with PKCE — no client secret required.
- Click Connect on the OpenRouter card.
- The platform generates a PKCE code verifier and challenge automatically.
- Authorize at OpenRouter's consent screen.
- After redirect, the token exchange completes using the code verifier.
- This gives your organization access to LLM model routing and chat completions.