Integrations

Integrations exist so a planning session starts from the work your team already has, and so the estimate the team lands on does not have to be retyped somewhere else afterwards.

There are two shapes of integration. Work item sources — Jira and Linear — are API-backed connections made once for a SprintBee organization and then attached to a Workspace, where they feed the queue and take estimates back. Everything else is lighter: the Browser Companion reads a tab you already have open, and Slack and Microsoft Teams receive one-way notifications.

Jira#

Jira Cloud connects two ways. A personal connection is authorized by one teammate with their own Jira account — no Jira admin involved — and comments and estimates are posted under that person's Jira identity. An organization connection is the SprintBee Jira app, installed once by a Jira site admin and paired with the SprintBee organization, so actions are attributed to SprintBee rather than to a teammate.

Either connection gives a Workspace the same abilities: moderators search Jira and import issues into the queue, split an oversized item into new Jira issues, and accepting an estimate writes the value back to the fields you map. Retro facilitators can turn an Improvement Action into a connected Jira issue. Jira is a paid feature.

Set up Jira

Linear#

Linear connects once from the SprintBee organization and then attaches to a Workspace the same way Jira does — search and import into the queue, split into new Linear issues, write accepted estimates back to Linear's estimate field, and create connected Improvement Actions from a retro. Linear is a paid feature.

Set up Linear

Browser Companion#

The Browser Companion is a Chrome extension that pairs the Jira Cloud or Linear issue already open in your browser with a SprintBee room. It uses no tracker API at all, which is the point: there is nothing to authorize and no admin to ask.

A moderator captures the visible issue into the room's queue. The Companion never searches your tracker and never writes anything back to it. Capturing into the room you are paired with is free on every plan. Two extras are paid: routing a capture into a different room than the one you are paired with, and keeping the Companion connected in the background with no room tab open.

Set up the Browser Companion

Slack and Microsoft Teams#

A Workspace can post voting-window updates — opened, closing soon, closed — to a Slack channel, a Microsoft Teams channel, or both at once, and can optionally announce each accepted estimate. Traffic only ever flows outward; neither channel can pull work into a room.

Slack connects in one click with Add to Slack, or by pasting an incoming webhook URL. Teams uses a Power Automate Workflows webhook. Notifications are a paid feature, separate from async voting itself, which is free.

Set up Slack · Set up Microsoft Teams

Where each one is set up#

Three different places, and knowing which is which saves the most time:

What	Where
Jira and Linear connections	Dashboard → Integrations, by the organization owner
Attaching a source to a Workspace	Workspace → Integrations & notifications
Slack and Teams webhooks	Workspace → Integrations & notifications
Browser Companion pairing	The extension's own Chrome side panel

A Workspace uses one active work item source at a time, so choosing Jira or Linear for a Workspace is a choice, not an addition.

Because plan access is resolved through the organization a person owns, expect the owner to make these connections. A teammate who belongs to a paid organization but does not own one may not see the paid controls.