Dashboard integrations

Open Integrations in the web dashboard to browse apps, search by name, or filter by category. Connected apps show their connection status. Each connection belongs to your account.

Connect an app

Click an app card to view its capabilities, or choose Connect to start setting it up. The menu beside it provides links to the provider and its credential settings.

• GitHub: Choose Continue with GitHub and authorize the application. GitHub supplies issues, pull requests, notifications, workflow runs, and releases. Use Repositories in the connection panel to manage repository sync.
• Linear: Create a personal API key with Read permission for your teams. Paste it into the connection panel. Athas reads your 50 most recently updated assigned issues, including their project, priority, and workflow state.
• Vercel: Create an access token. Enter a team slug if you want team deployments, or leave it empty for your personal account. The token must have access to the selected account. Athas reads its 50 latest deployments and build states.
• Sentry: Create a personal auth token with event:read, then enter your organization slug. Athas reads the 50 most recently seen issues from the last 14 days, including resolved issues. This connection supports Sentry Cloud at sentry.io.

Linear, Vercel, and Sentry credentials are checked against the provider before saving. The first activity sync completes as part of connecting. A rejected token does not replace an existing connection.

Sync and manage

Open Manage, then choose Sync now to update the inbox. These integrations sync on demand, with up to 50 items per sync; they are not a complete historical import. Repeated syncs update matching items without resetting their Athas triage status.

Choose Open inbox to see items from that integration. Source links take you to the original issue or deployment. Athas does not write changes back to Linear, Vercel, or Sentry.

Use Update token when credentials expire or their permissions change. Sync failures appear in the connection panel and mark the app as needing attention.

Disconnecting removes the saved credential and stops future syncs. Previously imported items stay in your inbox. Revoke personal tokens in the provider's settings if you no longer need them. Disconnecting GitHub also revokes its application authorization when the server's OAuth credentials are configured.

Server configuration

Tokens are encrypted with AES-256-GCM and are never returned to the browser. Configure a stable INTEGRATIONS_SECRET on the server; the existing JWT_SECRET is used as a fallback. Changing that secret requires reconnecting accounts.

GitHub also requires GITHUB_CLIENT_ID and GITHUB_CLIENT_SECRET, with an OAuth callback at /api/integrations/github/callback. The other integrations use personal tokens and require no OAuth application registration.

The database initializes the connection metadata columns automatically while preserving existing GitHub connections.

API references

The connectors use the documented Linear GraphQL API, Vercel deployments API, and Sentry organization issues API.