Integrations
Connect your tools once. Every module reads from the same data.
Firebeam connects to your existing tools via OAuth and keeps their data synced in the background. Trackers (Jira, GitHub, GitLab, Bitbucket, Linear) feed the delivery modules; messaging (Slack) adds context; analytics providers (PostHog, GA4, Plausible, Clarity) power UserLens.
Connecting
On the Integrations page, each provider connects with a standard OAuth flow: you approve the access in the provider's own consent screen, and can disconnect at any time. Connected accounts show who connected them and when they last synced.
What Firebeam reads
Work items and their history from trackers, message history from Slack, and event data from analytics providers. Access is read-oriented by design. Firebeam does not modify your source data. The one deliberate exception: retro action items can be created in Jira or Linear when you explicitly ask for it.
How syncing works
Webhooks push changes as they happen, and scheduled background syncs fill any gaps. Modules show when each source was last synced, and a Sync now button forces an immediate refresh when you need it.
Tracker sources and projects
After connecting a tracker, link its sources (a Jira project, a GitHub repository, a Linear team) to a Firebeam project under Projects. That mapping decides which items each module analyzes.
Disconnecting
Disconnecting an integration stops the syncing and invalidates the stored tokens. Data already synced remains until deleted with its project or company.
Every provider Firebeam connects
Trackers feed the delivery modules: Jira, GitHub, GitLab (including self-managed), Bitbucket, Linear and Azure DevOps. Slack and Microsoft Teams are where reports, alerts and the channel digest are delivered; Firebeam posts there but does not read your messages. Notion can receive backlog items. Analytics providers (PostHog, Google Analytics 4 and Plausible) power UserLens. Each connects from the Integrations page with the flow it needs: OAuth for most, an access token for self-managed GitLab, Bitbucket tokens and personal-account Azure DevOps, and an API key for analytics providers.
One connection, shared by the workspace
Each teammate connects their own account, but the data that comes in is shared across the workspace, so viewers and other project managers see the same modules without having to connect anything themselves. Connecting and disconnecting is project-manager and admin work; everyone else simply reads the results.
When a connection needs reconnecting
Firebeam signs in to each tool with a secure token and refreshes it automatically in the background, so you rarely have to think about it. A connection only needs reconnecting when that access is genuinely withdrawn: you changed your password, you or an admin revoked Firebeam in the tool's connected-apps settings, or a personal access token (used for personal Microsoft accounts on Azure DevOps) reached its expiry date. When that happens the connection is flagged 'Needs attention', syncing pauses, and a banner appears on your dashboard. Fixing it is one click: open Integrations and press Connect on that provider to sign in again. Your projects, history and settings are left untouched.
Connecting with a token
GitLab, Bitbucket and Azure DevOps can also connect with an access token instead of signing in. Use this for a self-managed GitLab (enter your GitLab's address and a personal, group or project access token with the api scope), for Bitbucket with an Atlassian API token and your account email (or a repository or workspace access token with the email left empty), and for Azure DevOps organisations on a personal Microsoft account. A self-managed GitLab must be reachable from the internet.
When a connection stops working
If a tracker stops accepting Firebeam's sign-in (an expired or revoked token, or a removed app), the integration switches to Needs attention, a banner asks you to reconnect, and the notification bell tells the team. It no longer looks connected while nothing syncs.