Integrations
Align connects to your existing tools in two ways: hosted apps that capture decisions as they happen (Pro 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 Pro 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.
Hosted integrations
| Integration | Capture | Discover scan | Status |
|---|---|---|---|
| Slack | yes | yes | Generally available, on by default |
| Microsoft Teams | yes | yes | Generally available, on by default |
| Jira | yes | yes | Generally available, on by default |
| GitHub | yes (validation-first) | yes | Generally available, on by default |
| Confluence | yes | yes | Generally available, off by default |
| Zoom | meeting transcripts only | yes | Available, off by default |
| Linear | /align comments only | yes | Available, off by default |
| AI Assistants (MCP) | n/a - this is how agents read the graph | n/a | Generally available |
Confluence, Zoom and Linear are fully 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 Notion, Google Docs, Datadog or GitHub Actions app. Notion history can be
imported with the CLI. The other three have no hosted connector at all - if you see
mcp-datadog or mcp-github-actions in the open-source tree, those are experiments with no
tests and no deployment, and they are not part of the product.
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.
| Source | Command | Notes |
|---|---|---|
| Git commit history | align import git | Local repository, no token needed |
| GitHub | align import github | |
| GitLab | align import gitlab | --domain for self-managed |
| Jira | align import jira | |
| Confluence | align import confluence | |
| Linear | align import linear | |
| Notion | align import notion | CLI only - there is no hosted Notion connector |
| Slack | align import slack | Experimental. Needs a user token (xoxp-) |
| Microsoft Teams | align import teams | |
| Zoom | align import zoom |
Git, GitLab and Notion are CLI-only: they have no hosted connector, no webhook and no ambient capture. See the CLI guide for flags and examples.
How hosted capture works
Every capture path begins with a deliberate human act. Align is not listening to your channels.
@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 |
| Post-meeting transcript | Teams, Zoom |
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 is stored until a human confirms. 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 and Linear. 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 Pro 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
Self-hosted Align uses Align's centrally-managed OAuth applications. You do not need to register your own Slack, Teams, Jira, GitHub, Confluence or Zoom apps. See Connector Authentication for how that works and what to do if your security policy requires your own apps instead.
Need another integration?
The connector SDK is open source. Contact us to request one or to talk about building it.