Integrations
Connect calendars, Slack, GitHub, Linear, Jira, Notion, Figma, ICS, and webhooks; understand sync, write-back, and plan limits.
Open Home → Settings → Integrations to connect and manage external tools. The hub shows provider capabilities, granted scopes, account, connection health, last sync, object count, and recent integration activity.
Available providers
| Provider | What Align uses it for | Write behavior |
|---|---|---|
| Google Workspace | Calendar events in Meeting Prep, Search, Ask Align, and context | Read-only calendar connection |
| Microsoft 365 | Outlook calendar events in Meeting Prep, Search, Ask Align, and context | Read-only calendar connection |
| Secret ICS URL | Calendar availability and event context | Read-only feed; treat the URL like a password |
| Slack | Search invited channels, answer @Align, close threads into drafts, and send approved records back | Posts only through explicit product actions |
| GitHub | Branches, pushes, pull requests and merges that move tickets; issues, checks, reviews and merge evidence | Create issues/comments after confirmation; ticket moves follow your Inbox setting |
| Linear | Two-way sync between a Linear team and a Plans project | Edits flow both ways within seconds |
| Jira | Two-way sync between a Jira project and a Plans project | Edits flow both ways within seconds |
| Notion | Explicitly shared pages and databases as cited knowledge | Read-only; Notion remains the editor |
| Figma | Authorized design files, thumbnails, comments, versions, and selected team projects | Read-only evidence links |
| Webhooks, Zapier & Make | Bring external records into Align and emit signed Align events | Configured incoming and outgoing automation |
Provider cards may appear as not configured when a self-hosted deployment has not supplied that provider's OAuth credentials.
Slack workflow
- Connect Slack, then type
/invite @Alignin each channel Align should access. It does not read every workspace channel automatically. - Mention
@Alignor DM it to ask a workspace question.@Align helpshows the supported actions. - Use Close with Align from a message's More actions menu. Align drafts the decision or work record; a person reviews it before creation.
- From a Decision or Work item, choose Send to Slack to post an approved card to a channel or the original thread.
Delivery integrations
Jira and Linear sync both ways. On a Plans project, choose Sync with Jira or Linear. Title, description, status, assignee, priority, due date and comments stay in step in both directions within seconds, with a status mapping between your Plans workflow and the tracker. See Plans.
GitHub moves tickets. A branch starts work, a pull request puts it in review and a merge marks it done. Align reads activity from each person's GitHub login every few minutes, or instantly from the Align GitHub App installed on the organization. Moves wait in the Plans Inbox unless the person turned on Auto-move my own tickets.
On a single work item, Implementation & links still attaches an existing GitHub, Linear or Jira object, or creates one, and shows its live state.
GitHub evidence can include pull-request checks, review, and merge status. Figma and Notion links keep the design or spec next to the project, Decision, or work item without moving authorship into Align.
Sync and connection health
- An initial sync runs after OAuth succeeds.
- Sync now starts a manual refresh.
- Connection details show the latest objects and provider-specific health.
- Needs attention means the last sync failed or authorization must be refreshed.
- Disconnecting removes Align's stored connection. It does not delete records in the provider.
Webhooks, Zapier, and Make
The webhook connection has two directions:
Incoming
POST JSON to the private inbound URL to create a task or decision; title is required. Send an id field or Idempotency-Key header to avoid duplicates. Treat the inbound URL as a secret.
Outgoing
Choose an HTTPS destination and the Align events to send. Each request includes X-Align-Signature: sha256=…, an HMAC over the raw body using the connection's signing secret. The hub can send a test event and rotate the inbound URL and signing secret; rotation invalidates the old values immediately.
Plan limits
The server enforces connector limits and the hub explains a lock before connection:
- Calendar connections, GitHub and the MCP server are available on every plan; they are part of the loop, not an upsell.
- Free includes Slack and a two-way mirror with one work tracker, Linear or Jira.
- Team mirrors both trackers and unlocks every connector, including Notion and Figma.
- Webhooks, Zapier, and Make require Business.
Existing connections remain visible so you can diagnose or disconnect them even when starting a new connection is restricted.
Safety model
- OAuth state is signed and expires; callback return URLs are allow-listed.
- Stored provider credentials are encrypted.
- Search and Ask Align only use objects available through the signed-in user's Align permissions.
- External create/update/post actions are controlled actions and require confirmation in the product flow.
- Notion reads only pages explicitly shared with the Align connection; Slack reads channels the app was invited to.
Last updated on