Slack
Alerts land where your team is already talking
A plain HTTPS POST to an incoming webhook URL you paste in -- no app to install, no OAuth screen to click through.
- One Slack incoming webhook URL per rule, the same mechanism Slack's own docs recommend
- A new issue, a regression, a spike, or a missed heartbeat, each its own message
- Delivery runs off the ingestion hot path, so a slow or unreachable webhook never adds latency to reporting an error
Just a webhook URL, nothing to install
Slack delivery is a plain JSON POST to whatever incoming webhook URL you paste into the rule's target field, the same URL format Slack's own "Incoming Webhooks" app hands you. There's no ForgeOps app to add to your workspace and no OAuth scopes to review: the webhook URL is the entire integration.
Under the hood it shares the same HTTP-delivery path as the generic Webhook channel below, just formatted as a Slack message payload instead of structured JSON meant for your own code to parse.
Slack is one channel among five, configured the same way as the rest.
Never blocks on Slack being slow
Notification delivery runs in a background job, kicked off after an event's already been grouped and stored, never inline in the request your app made to report the error. A slow or temporarily unreachable Slack webhook shows up as a failed delivery you can see, not a delay your users feel.
Paste the webhook URL into the same target field every channel uses.