Integrations
Align connects to your existing tools in two ways: hosted apps that capture decisions as they happen (Growth and Self-Hosted), and the free, open-source CLI that imports decision history from the tools you already use.
There is no per-integration add-on price, no "Slack costs extra", and no limit on how many you connect, on any plan.
The paid line is drawn at the mechanism, not at the integration. The CLI is free and imports history into a personal graph from every source below. Enabling a hosted, org-level connector - the real-time capture that writes to your shared graph - requires Growth or Enterprise. So "no integration is paywalled" means no integration is singled out; it does not mean hosted connectors are free.
Capture sources vs. the validation gate
Two roles, and mixing them up is the most common misreading of this product.
Two roles. GitHub does both, which is the most common misreading of this product - so the useful question is not "which side is GitHub on" but "where in the life of a decision does each tool sit".
| Stage | Tools | What happens |
|---|---|---|
| Stated - where a decision gets made | Slack, Teams, Jira, Confluence, and meeting transcripts (Teams, Zoom) | A human flags a decision, or an opted-in ambient signal suggests one. Align synthesises it into a Decision Snapshot. |
| Enacted - where the decision turns into code | GitHub | A merged pull request is captured as a decision, on by default. |
| Validation - where code meets the decision | GitHub | A pull request is checked against decisions already in the graph. Align posts an Align Report comment and an Align Decision Check status. See GitHub. |
A decision usually starts as talk and ends as code, so GitHub tends to arrive last in a
decision's timeline rather than alongside Slack and Jira. It is a real capture source at that
point, and the highest-volume one: merged-PR capture is on by default (auto_capture_merged,
opt out per repository), which is why a mature graph is usually GitHub-heavy.
What Align does not do is read your commit history to reconstruct your reasoning. A commit is an artefact of a decision - it shows what was built, never why, and never what was rejected. A merged pull request is a different artefact, carrying a description, a review and an outcome, and that is what gets captured.
Align records which tool a decision came from, and you can see it on the decision. It does not currently rank or weight decisions by how far through this lifecycle they are - a merged PR and a Slack message are treated as peers when relationships are worked out.
What each integration does
| Integration | Historical import (Discover) | Live capture | CLI import | Where it runs |
|---|---|---|---|---|
| Slack | yes | yes | align import slack (experimental) | both |
| Microsoft Teams | yes | yes | align import teams | both |
| Jira | yes | yes | align import jira | both |
| GitHub | yes | yes (validation-first) | align import github | both |
| Confluence | yes | yes | align import confluence | both |
| Zoom | yes | meeting transcripts only | align import zoom | both |
| Linear | yes | /align comments only | align import linear | both |
| Azure DevOps | yes | yes | no | hosted |
| Microsoft 365 Documents (SharePoint, OneDrive) | yes | yes | no | hosted |
| Google Drive | yes | yes | no | hosted |
| Google Meet | no | yes | no | hosted |
| Notion | yes | no | align import notion | both |
| GitLab | no | no | align import gitlab | CLI |
| Git (local history) | no | no | align import git | CLI |
| AI Assistants (MCP) | n/a | n/a | n/a | how agents read the graph |
How to read the columns:
- Historical import (Discover) means a hosted scan you can start from the app.
- Live capture means a webhook handler in the hosted connector. GitHub also validates pull requests against your decisions. See GitHub.
- Notion connects the same way as Jira and Confluence: an admin connects it once for the workspace, through a Notion OAuth app that asks for "Read content" only. Notion's consent screen lets the admin pick the pages to share, and Align sees only those. Discover scans them. There is no webhook, so there is no live capture, and Align does not reply in Notion yet. The CLI imports Notion with the person's own login, a separate path from the workspace connection.
- GitLab and Git have no hosted connector. Import them with the CLI.
- Azure DevOps, Microsoft 365 Documents, Google Drive and Google Meet have no CLI import. Google Meet has live capture only, because Discover cannot scan it.
- Deployment differs. Azure DevOps and Microsoft 365 Documents run in preview and are disabled in production. Google Drive runs in preview and is not set in production, so the chart default (off) applies. Google Meet is not deployed in either. Self-hosting, you set the flag.
Confluence, Zoom, Linear and Notion are built, tested, in the connector registry, and shipped as
container images. But connectors.<name>.enabled is false in the chart's default values, so a
stock install does not run them. On Align Cloud, ask us to turn one on. Self-hosting, set the
flag. See Configuration.
We do not ship a Google Docs, Datadog or GitHub Actions app. None has a hosted connector
that is part of the product. If you see mcp-datadog or mcp-github-actions in the open-source
tree, those are experiments with no deployment. They are not in the connector registry, the Helm
chart or the CI build matrix.
CLI imports (free, open source)
The Align CLI imports decision history from the tools you already use into a personal or shared graph. No account required. The table above lists every command. Notes:
align import gitreads a local repository and needs no token.align import gitlabtakes--domainfor self-managed GitLab.align import slackis experimental and needs a user token (xoxp-).
See the CLI guide for flags and examples.
How hosted capture works
Most capture begins with a deliberate human act. Align is not reading your channels and saving what it finds.
@align We decided to use feature flags for the checkout rollout
| Trigger | Where it works |
|---|---|
@align <decision> | Slack, Teams |
/align | Jira and Confluence comments, GitHub PRs and issues, Linear comments |
| React with 📌 or 🔖 | Slack, Teams. Configurable per workspace |
Ambient suggestions - where Align notices a decision-shaped conversation and offers to capture it - are off by default and opt in per channel, project, repository or space. Nothing from them is stored until a human confirms.
Some things are saved without a confirmation, for example a merged pull request, a Zoom meeting recording (by default), and a decision an agent records through the MCP server. Align saves them as remarks. A remark is shown to agents marked as unconfirmed, and it does not fail a check. Full per-platform matrix, including what each vendor's API makes impossible: Capture.
Discover
Discover scans history rather than waiting for new decisions. It runs against Slack, Teams, Jira, GitHub, Confluence, Zoom, Linear, Azure DevOps, Microsoft 365 Documents and Google Drive. Suggestions are surfaced for review and nothing enters the graph until you approve it.
Connecting an integration
- Settings → Integrations
- Connect next to the integration
- Authorize Align in the external service
- Choose which channels, projects or repositories are in scope
Enabling an org-level connector requires a Growth or Enterprise plan. The CLI needs no account and no connection step.
Data and privacy
- Align only accesses data you explicitly grant.
- Messages are processed to extract decisions, and the raw text is cleared from the decision record after analysis. Two paths hold content longer, and both are named in Data Retention.
- You can disconnect an integration at any time; its OAuth tokens are deleted on disconnect.
Self-hosted integrations
On Align cloud, Align's OAuth apps are used. Self-hosted, you register your own Slack, Teams, Jira, GitHub, Confluence or Zoom apps. See OAuth apps.
Need another integration?
The connector SDK is open source. Contact us to request one or to talk about building it.