The integrations that send a bug report where your team already works

A connector takes a report out of Session Replay and puts it in the place your team looks anyway: a chat channel, an issue in the tracker you already work in, or an endpoint of your own. This page lists every destination, what each one does with a report, and what connecting it takes.

Install the extensionSee how it works

What a connector is

A report is captured once and read anywhere. A connector is how it arrives somewhere your team is already looking, rather than waiting for somebody to open the dashboard. It is the same thing other tools call an integration; in the dashboard the screen is called Connectors.

The destinations do not all behave the same way, and the difference matters when you pick one. Some post on their own as reports arrive. Others file only when somebody presses the button on a report.

Available today

The destinations a team admin can connect from the dashboard right now.

Slack

Available now
What arrives
Posts every new report into the channel you choose, as it arrives, with the page it was filed on, its title, a link that opens the report, and how bad it looks once it has been judged. If the channel is allowed to change reports, anyone in it can move a report's status and set its severity from the message.
What connecting takes
A team admin presses Add to Slack and approves it in your workspace, then picks a channel. Session Replay asks for two things only, permission to post and permission to list channels so you can pick one. A private channel needs the app invited to it first. Slack bug tracking, end to end
In the channel
New bug report · shop.example.com

Discount code does not change the total

Page: shop.example.com/checkout

Reported by        Severity
Anonymous          Major

Status             Failed requests
Pending            1

First error:
Uncaught TypeError: discount is null (cart.js:214)

[ Open report ]  [ Start work ]  [ Mark resolved ]

Severity
[ Minor ]  [ ✓ Major ]  [ Critical ]

Screenshot · Chrome · 31 Aug at 14:20

Microsoft Teams

Available now
What arrives
Posts every new report into the Teams channel you choose, as it arrives, with the page it was filed on, its title, who filed it, how many requests failed, and how bad it looks once it has been judged.
The card carries a link that opens the report. Nothing written in the channel comes back here, so status and severity are set in Session Replay. Cards arrive from the Teams Workflows bot, under its name rather than ours.
What connecting takes
A team admin creates a Workflows webhook in your own Teams tenant, pastes the URL it gives back here, and names the channel it posts into.
In the Teams channel
New bug report · shop.example.com

Discount code does not change the total

Page: shop.example.com/checkout

Reported by       Anonymous
Severity          Major
Status            Pending
Failed requests   1

First error:

Uncaught TypeError: discount is null (cart.js:214)

[ Open report ]

Screenshot · Chrome · 31 Aug at 14:20

Jira Cloud

Available now
What arrives
Creates an issue in the project you chose, carrying the report and a link to it, and optionally writes the link into a field you nominate. Nothing is filed automatically: an issue is created only when somebody presses the button on a report.
What connecting takes
A team admin signs in at Atlassian and consents, then chooses the Jira site, the project and the issue type. There is no Marketplace app and nothing to install on your Jira site.
In the project
https://session-replay.com/replays/8f3c1ab9d24e

What the reporter wrote

  The discount code applies but the total does not change.

Page: https://shop.example.com/checkout
Browser: Chrome 139 · Operating system: macOS 15.5
Reported by: Anonymous · Severity: Major

12 console lines · 34 requests, 1 failed

First error: Uncaught TypeError: discount is null (cart.js:214)

Webhook

Available now
What arrives
Posts your report events to an HTTPS endpoint of your own as signed JSON, for your own code to act on. The body carries the report's identity, its domain, its status and severity and its share link. The capture itself is never in the body, it stays behind the link. Every request is signed with HMAC-SHA256 over the timestamp and the raw body, and a failed delivery is retried on a widening schedule, up to six attempts, each one in the delivery log.
What connecting takes
A team admin adds the URL, picks which events to send and binds it to one of your domains or to all of them. The signing key is shown once, when the destination is created, and can be rotated. How webhooks reach Zapier, Make and n8n
Exactly what the Test button sends
{
  "event": "report.created",
  "version": 1,
  "test": true,
  "sent_at": "2026-09-01T06:04:51Z",
  "data": {
    "report": {
      "id": "00000000-0000-0000-0000-000000000000",
      "share_token": "test-delivery-not-a-real-report",
      "share_url": "https://session-replay.com/replays/test-delivery-not-a-real-report",
      "status": "pending",
      "severity": "minor",
      "created_at": "2026-09-01T06:04:51Z",
      "updated_at": "2026-09-01T06:04:51Z"
    },
    "site": {
      "id": "00000000-0000-0000-0000-000000000000",
      "domain": "example.com"
    }
  }
}

GitHub

Available now
What arrives
Creates an issue in the repository you chose, carrying the report and a link to it. Nothing is filed automatically: an issue is created only when somebody presses the button on a report.
The first line of every issue is the report's link, and that link is public. Anyone who can read issues in the repository can open the report without signing in, and in a public repository that is everybody.
What connecting takes
A team admin connects GitHub, chooses the account or organisation and then the repository, and binds it to one of your domains or to all of them. Session Replay never edits, closes or deletes anything, and never reads your code. GitHub bug tracking, end to end
In the repository
[Open report](https://session-replay.com/replays/8f3c1ab9d24e)

### What the reporter wrote

> The discount code applies but the total does not change.

- Page: https://shop.example.com/checkout
- Browser: Chrome 139
- Operating system: macOS 15.5
- Reported by: Anonymous
- Severity: Major

12 console lines · 34 requests, 1 failed

First error:
```
Uncaught TypeError: discount is null (cart.js:214)
```

Linear

Available now
What arrives
Creates an issue in the Linear team you chose, carrying the report and a link to it. Nothing is filed automatically: an issue is created only when somebody presses the button on a report.
What connecting takes
A team admin connects a Linear workspace, chooses the team to file into, and binds it to one of your domains or to all of them. Read access is used only to list your teams, and nothing there is edited, closed or deleted. Linear bug tracking, end to end
In the team
[Open report](https://session-replay.com/replays/8f3c1ab9d24e)

### What the reporter wrote

> The discount code applies but the total does not change.

- Page: https://shop.example.com/checkout
- Browser: Chrome 139
- Operating system: macOS 15.5
- Reported by: Anonymous
- Severity: Major

12 console lines · 34 requests, 1 failed

First error:
```
Uncaught TypeError: discount is null (cart.js:214)
```

What connecting one takes

A team admin authorises it

Connecting is done once, for the whole team, by somebody who administers it. It is not a setting each person turns on, and nobody is asked to sign in to the other tool to read what arrives.

You pick where it lands

A channel, a project and issue type, a repository, a team, or a URL of your own. The choice is made at setup and every report afterwards follows it.

Reports start arriving

Some destinations post as reports come in. Others file only when somebody presses the button on a report. Which is which, and what the message looks like when it arrives, is on the card for each destination above.

What a connector does not do

A connector carries a report outward and stops there. So that you can judge one fairly before you wire it up:

  • The capture is never in the payload. What travels is the report's details and the link that opens it, and the screen, console and network log stay behind that link.
  • A report's share link is public. Anyone holding it can open the report, so a channel or an issue carrying that link is handing it on.
  • Nothing is read back. No connector reads your Slack messages, your Jira issues or your repository.
  • There is no two-way sync. Closing the Jira issue does not close the report, and comments written there do not come back.
  • A connector is set up by a team admin, once, for the whole team. It is not a per-person setting.

Put your reports where your team already works

Capture a bug once, and let it arrive in the channel, the project or the endpoint your team already watches.

Install the extensionSee pricing