Skip to main content

Integrations

Integrations connect Align to the tools your team already uses: source control, error monitoring, deploys, chat, metrics and task tracking.

How integrations work​

Align runs the apps; you bring the access. Align registers and maintains the apps it connects through: its GitHub App, the Alignsoft Sentry integration, and the Railway and Illumera apps in the Marketplace. Your workspace authorises its own accounts: you install Align's GitHub App on your GitHub organisation, create a key in your own Sentry organisation, or paste a token from your own Prometheus. You never enter the credentials of Align's own apps, such as the GitHub App's ID or private key.

Slack works differently today: you create the incoming webhook or Slack app in your own Slack workspace and paste its webhook URL or bot token into Align. See Slack.

Connections belong to the workspace​

  • Each workspace's connections are its own. Another workspace cannot see or use them, even when both connect the same outside account. If you belong to several workspaces, switch to the one you want before you connect anything.
  • The keys and tokens you enter are stored encrypted (AES-256-GCM) for your workspace and are never shown again. A form shows only that one is stored, for example "Saved — leave blank to keep". Leave the field blank to keep the stored value, or enter a new one to replace it.
  • Most connections are checked when you save them: Align calls the service with your credentials and shows whether it worked. You can check again at any time.
  • Disconnecting an integration removes its stored credentials.

Where they live​

Integrations are in Settings → Integrations, which only admins see. The page has two parts:

  • Add-ons, with the Illumera add-on card where it is offered.
  • Integrations, grouped into categories: Communication & Notifications, Developer Tooling, Authentication & Identity, AI & Automation, File Storage & Collaboration, Payments & Invoicing, eSignatures, and Project Management & Collaboration.

Most rows have a switch and, once the integration can be set up, a Configure button that opens its form. The Railway row has Marketplace buttons instead (see Railway). Rows marked Coming Soon are not available yet: Microsoft Teams, Twilio SendGrid, GitLab, Okta, Azure AD, Zapier, Google Drive, SharePoint / OneDrive and Dropbox. Align can also switch a provider off for the whole platform, which removes it from the list.

If the list is empty, click Initialize Integrations. Sync Missing Integrations adds any provider missing from the list.

Some settings that use an integration are per project, in the project's settings on the Integrations tab: linked GitHub repositories, the Sentry project, a project-specific Slack webhook, and CI settings.

Personal connections​

A few connections belong to a person rather than the workspace. Open your profile settings, go to the Integrations tab, and click Manage integrations. There you can connect your own GitHub account (where Align has switched on verified linking), Google Drive (where Align has set it up), and your own MCP connectors for Max. These act only for you and are never used for other people.


GitHub​

Install Align's GitHub App on your GitHub account or organisation, link repositories to projects, and Align links commits and pull requests to entries, credits them to the right people, records CI results, and moves entries when work is merged and deployed. One GitHub account can serve several workspaces, and each workspace keeps its own user mappings.

See GitHub Integration.

Sentry​

Connect with a key from your own Sentry organisation, or install Alignsoft on sentry.io. Align links Sentry errors to entries, shows production errors on the project dashboard, and feeds production-health reports.

See Sentry Integration.

Railway​

Install Railway from the Marketplace, paste the webhook URL Align gives you into your Railway project, and map your environments. Deploys then move the entries they carried and feed deploy reports.

See Railway Integration.

Slack​

Slack is under Communication & Notifications. Turn on its switch and the Slack Configuration form opens. It takes either or both of:

  • a Webhook URL: an incoming webhook from a Slack app in your Slack workspace. A webhook posts to the one channel it was created for.
  • a Bot user OAuth token (optional): from a Slack app with the bot scopes chat:write, chat:write.public, channels:read and groups:read, installed in your Slack workspace. A bot token can post to any channel you choose.

Channel Name (optional) is for display only. Turn on Slack Notifications, click Save Settings, and use Test Webhook to send a test message. Both credentials are stored encrypted, and the form never shows them again.

What goes to the webhook. With a webhook set, Align posts entry activity to its channel: new entries, assignments, updates, comments, automatic status changes and production deploys. A project can send its own activity to a different channel: set its Slack Webhook URL on the project's Integrations tab. Slack must still be on for the workspace.

Channel destinations. With a bot token, you choose channels in Settings → Notifications:

  1. Under Slack channels, click Add a channel and pick from the channels the bot can see.
  2. For each channel, the Clients may read this switch marks it Client-safe. Align never guesses this from the channel's name.
  3. Under Notification routing, choose a Slack channel for each notification and audience (Team or Client). Scheduled digests are delivered this way.

The client-safe rule. A notification for clients goes to Slack only through a bot token, and only to a channel marked client-safe. It never falls back to the webhook or to a default channel. A client row in the routing table offers only client-safe channels; with none chosen, nothing is sent to Slack. A team notification left on Default channel goes to the webhook's channel, if there is one.

Prometheus, Grafana and Loki​

These three are under Developer Tooling. Click Configure, fill in the form, and click Connect. Align checks the address and credential straight away and shows Connected or Error. Re-validate checks again; Disconnect removes the connection.

ProviderWhat it needsWhat Align reads
PrometheusPrometheus base URL (it must serve the HTTP API, /api/v1), and a Bearer token if your Prometheus requires one95th-percentile latency, error rate (the share of requests with a 5xx code) and throughput, from the standard http_request_duration_seconds and http_requests_total metrics
GrafanaGrafana base URL and a Service account token (the Viewer role is enough)Active alerts from Grafana's alerting
LokiLoki base URL (it must serve /loki/api/v1), a Bearer token if required, and a Tenant id (X-Scope-OrgID) for multi-tenant LokiCounts of log lines containing "error", and spikes in that count

Align uses these in reports that Max builds: Latency / Throughput SLO, Error-rate / Saturation, Active Alerts, Log Error Spikes, and the Production Incident Report. See Max. One connection serves every project in the workspace.

The address must be reachable from the internet. Align refuses private and internal network addresses. Plain http:// addresses are allowed for self-hosted servers. Align only reads from these services.

TaskFlow​

Taskflow is under Project Management & Collaboration. It syncs TaskFlow tasks and Align entries in both directions. Turn on its switch and click Configure to open Taskflow Configuration.

Setting it up

  1. Under Connection Settings, enter the Taskflow Base URL (without /api; Align adds it), the API Token and the HMAC Shared Secret. Click Test Connection, then Save Connection.
  2. Give the Align Webhook Receiver URL shown in the panel to the TaskFlow team, so TaskFlow sends task events to Align.
  3. Under Workspace / Project Sync, map each TaskFlow workspace and project to an Align project.
  4. Review Field Mapping and Status Mapping. If status sync is off and no mapping exists, Enable & seed defaults fills in a starting set.
  5. Under Sync Feature Flags, turn on what you want. All start off.

What syncs

  • TaskFlow to Align. New tasks in a mapped project are imported as entries, and changes to linked tasks are applied through your field and status mappings. Align takes changes from TaskFlow's webhook and from a reconciliation pass every five minutes.
  • Align to TaskFlow. A new entry in a mapped project creates a TaskFlow task, and edits to a linked entry update its task. With Status sync on, every status change on a linked entry is pushed, whatever made it.
  • Sync now. Each mapping has a direction (Pull, Push or Both) and a Sync button. Full re-imports every task in the project.
  • Conflicts. When both sides changed, the change waits in the Conflict Review Queue.

The other switches add Comment sync, Project intake and Member intake (new TaskFlow projects and members wait for an admin's approval under Incoming from Taskflow), Federate approvals into Align inbox, and Push Align cost approvals to Taskflow. User Account Linking pairs TaskFlow users with Align users, and OKR Rollup Mappings link Align work to TaskFlow key results.

If TaskFlow rejects the API token three times in a row, sync pauses and the panel says "Token rejected — re-enter your API token". Save a valid token to resume. Remove Connection removes the connection and its stored credentials.

Fireflies​

Fireflies is under Communication & Notifications. Its form takes a Fireflies API key, which Align checks and stores encrypted. Align does not yet fetch meeting transcripts from Fireflies, so connecting it has no visible effect today.

Other integrations in the list​

IntegrationWhat it is for
Replit AgentConnect a Replit account so Max can send implementation requests to Replit Agent. A platform admin must first allow it for the workspace; then click Connect with Replit. See External Writes.
Auth0Sign-in through your own Auth0 tenant: Domain, Client ID, Client Secret, Callback URL and Default Role for New Users. For SAML single sign-on, use Settings → Single Sign-On instead.
OpenAIChooses the AI provider and model for your workspace. The API key is not entered in this form.
WhatsAppWhatsApp notifications through Meta's Cloud API. Align does not store the access token typed into the form; it must be set in Align's server settings, so contact Align support to set it up.
StripePayments for client invoices. Only Align's platform operators can change its settings.
Native SMTP, Resend, Dropbox SignAlign's own email sending and e-signature accounts, set up by Align for every workspace. There is nothing to configure; the form says so.

What Align writes to other systems​

Most integrations only read. The ones that write — GitHub comments and check runs, TaskFlow tasks, Slack messages — are listed, with what triggers each write, in External Writes.

Support​

Questions or issues: support@alignsoft.us.