Addons (App Store)

Addons connect other tools to your workspace — for example, turning errors from your error tracker into tickets, or filling a fresh workspace with sample tickets. Each workspace decides for itself which addons it installs and how they're set up.

Open Settings → App Store (under Integrations).

Who can do what

Everyone on the team can open the App Store and see what's installed. Only workspace owners and admins can install, set up, switch off, uninstall or run an addon; for everyone else the controls are greyed out with Only workspace owners and admins can manage addons.

The App Store

Each addon has a card with its name, version and a short description, plus badges for what it can do:

Addons without this last badge never see internal tickets or internal comments.

Install and set up

1. Click Install on the addon's card.
2. Under Configuration, pick where its tickets go (New tickets go to — only tickets on the customer board can reach your customers), adjust the other options and click Save.
3. If the addon needs access to the other tool, enter it under Credentials and save. Credentials are stored encrypted and never shown again; to keep a stored value, leave its field empty.
4. If the card shows a Webhook URL, click Copy and paste it into the other tool, so it can send events to your workspace.

The card shows when it was installed and last updated.

Switch off or remove

• Enabled — switch off to pause an addon without losing its setup. A paused addon receives nothing and can't run its actions.
• Uninstall → Confirm uninstall — removes the addon and its setup. Tickets it created stay; their links to the other tool (the Linked row on a ticket) are removed.

An addon marked Not available is still installed but no longer offered. Uninstall it to clean up.

Available addons

Demo tickets

Fills a fresh workspace with realistic sample tickets, so there's something to look at.

1. Install Demo tickets.
2. Under Actions, set Count (1–50, 20 by default) and click Run next to Seed demo tickets.

The tickets use your ticket types, statuses and priorities, start with [Demo] so they're easy to find and clean up, and some get a few internal comments. By default your team gets no emails about them.

Sentry

Turns errors from Sentry into tickets and keeps both sides in step.

• A new issue in Sentry creates a ticket with a short summary and a link back to Sentry (never the full error details). It's an internal ticket unless you change that.
• The same issue again adds an internal comment to that ticket (or nothing, if you set it to ignore repeats).
• Resolved in Sentry moves the ticket to the status you set in Resolved status.
• Ticket closed here resolves the issue in Sentry; reopening the ticket reopens the issue. This part needs the token and your Sentry organization in the setup.

Setup, in short:

1. Install Sentry in the App Store and copy its Webhook URL.
2. In Sentry, create an internal integration (Settings → Developer Settings → Custom Integrations), paste the webhook URL and turn on issue events.
3. Copy the integration's client secret into Client secret under the addon's Credentials — Sentry signs every event with it, and anything not signed with it is rejected.
4. To close Sentry issues from here, also enter the integration's token in Token and your Sentry organization in Org slug (under Configuration).

The addon has the Receives internal tickets badge: it's meant for your team's own Sentry, and Sentry tickets are internal by default.