Integrations
Integrations in the Workspace area (Admin) — route /workspace/integrations.
Integrations lives in the Workspace area of the dashboard, under Admin.
At a glance#
| Dashboard route | /workspace/integrations |
| Area | Workspace (workspace) |
| Group | Admin |
| Platforms | Available for every app platform. |
What it does#
Integrations is the single hub for everything ScaleBun connects to. Each connection is created from a catalog entry, shows its live status, and opens into a drawer for configuration. Alongside the catalog: routing rules for deciding which alerts go where, push providers, and data sources.
The catalog covers alerting and ticketing:
| Provider | What it does |
|---|---|
| Slack | Posts crash and issue alerts to a channel, deep-linked back to the replay. |
| Discord | Channel alerts. |
| Microsoft Teams | Channel alerts. |
| Jira | Creates and links tickets from issues. |
| GitHub | Creates and links issues. |
| PagerDuty | Paging for on-call escalation. |
| Opsgenie | Paging for on-call escalation. |
Slack, and any provider with an environment map, can route each environment's alerts to its own destination, with the default used for anything unmapped.
When to use it#
Once, during setup, and then whenever an alert goes to the wrong place. Connecting an alerting provider is the highest-value ten minutes in the whole dashboard: it is the difference between finding out about a crash spike because you happened to look and finding out because you were told.
Workflow#
Connect alerting before ticketing
Alerting tells you something is wrong. Ticketing organises work you already know about. Do them in that order.
Map environments explicitly
Production alerts in the same channel as staging alerts train the channel to be ignored. Every provider with an environment map supports splitting them.
Send a test
Confirm delivery at connect time. A misconfigured alert channel is silent, and silence is indistinguishable from good news.
Set routing rules once alerting works
Routing decides which alerts are worth interrupting someone for. Default to fewer.
Permissions and prerequisites#
Connecting requires ADMIN or OWNER; DEVELOPER can also connect integrations. You need
credentials from the provider — a Slack bot token with chat:write, for instance.
Push providers are relevant only if you send push.
Limits and edge cases#
Private Slack channels need an invite. Public channels are joined automatically; a private channel requires
/invitefor the bot before it can post.A webhook that fails repeatedly is auto-disabled, and that is recorded in the audit log. It will not silently keep retrying forever.
Some catalog entries are mobile-relevant only and are hidden for a web app.
Ticket status is synced, not live. A linked ticket reflects the last sync.
Troubleshooting#
Slack connected but no messages arrive. Check that the bot is in the target channel — this is the most common cause by a wide margin — then check routing rules, then the environment map.
Alerts stopped without anyone changing anything. Look for webhook.auto_disabled in the audit log.
A token stopped working. Rotate it at the provider and re-enter it. Tokens are frequently revoked by the provider's own policies rather than by you.
Where the data comes from#
Served by
Integrations
Push credentials