Slack.

Connect your workspace

1. In Brily, go to Settings → Integrations → Slack.
2. Click Install. You'll be taken to Slack to authorise the app — we request the minimum scopes required: chat:write, channels:read, links:write.
3. After authorising, the integration appears in your workspace under Apps → Brily. Invite @Brily into any channels you want to route alerts to.

You can install the integration in multiple Slack workspaces per Brily project — useful for agencies where each client has their own workspace.

Create an alert route

Under Alerts → Routes, click New route. A route consists of three things:

• Match criteria — severity, project, tag, monitor name pattern. A route with no match criteria matches everything.
• Destination — a Slack channel (or multiple).
• Time window — always, or business hours in a named timezone.

A conventional setup for a small team:

• P1 (outage) → #ops-alerts · always
• P2 (degradation) → #ops-digest · business hours
• P3 (info) → #ops-digest · business hours

Alert formatting

Every alert posted to Slack contains:

• Severity badge and monitor name
• Short reason (the assertion that failed, or the error seen by each probe region)
• Links: Open in Brily, View runbook, Promote to status page incident
• A 5-minute uptime chart of the affected monitor

You can attach a runbook URL to every monitor in Monitors → (edit) → Runbook. It shows as a button in the alert.

One-click promote to incident

The Promote to incidentbutton on a Slack alert opens a modal pre-filled with the monitor's affected component, severity, and a first-draft Investigating update. Submit and the status page publishes immediately; subscribers are notified.

The reverse direction works too: posting an update on the status page from the dashboard pings the Slack thread where the alert was discussed, so Slack stays the source of truth for conversation.

Muting during maintenance

Create a maintenance window in Alerts → Maintenance windows. Slack alerts suppress for matching monitors; the status page can optionally show a scheduled-maintenance banner.

Common issues

Alerts post to the wrong channel

Check that @Brilyis a member of the destination channel. Slack silently drops messages to channels the bot isn't in.

No alerts appearing

Under Alerts → Routes, use the Test routebutton. This sends a synthetic alert matching the route's criteria. If it arrives, your route is fine and the issue is with the match criteria on the actual monitor.

Duplicate messages

Two routes may be matching the same alert. Route matching is OR; an alert posts once per matching route. If you want only the highest-priority match to fire, use Route priority (premium feature on Team+).

Revoking access

In Slack, go to Apps → Brily → Configuration → Uninstall. In Brily, go to Settings → Integrations → Slack → Disconnect. Do both to fully sever the connection.