Slack

Alerts land where your team is already talking

A plain HTTPS POST to an incoming webhook URL by default: no app to install, no OAuth screen to click through. Connect the ForgeOps Slack App instead when you want real Resolve/Ignore buttons on the message itself.

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
Optional: connect the Slack App for interactive Resolve/Ignore buttons, actionable right from the message

Just a webhook URL, nothing to install, by default

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. Nothing to add to your workspace and no OAuth scopes to review: the webhook URL is the entire integration, and it's the default for a reason.

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.

Notification rules configured per trigger and channel, e.g. a new issue to Slack, a regression to email

Slack is one channel among six, configured the same way as the rest.

Optional: interactive buttons via a real Slack App

Connecting the ForgeOps Slack App to a workspace (a one-time OAuth install, from an organization's own Slack settings) unlocks a second way to point a rule: a channel name instead of a webhook URL. A rule targeting a channel gets real Resolve/Ignore buttons directly on the alert for issue-triggered notifications, no need to switch back to ForgeOps to act on it.

The two paths coexist freely: a webhook-URL rule and a channel-targeted rule can both exist side by side, on the same project, at the same time.

The new notification rule form, showing the trigger and channel dropdowns, target field, and spike threshold fields

Paste the webhook URL into the same target field every channel uses.

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 destination shows up as a failed delivery you can see, not a delay your users feel.

See it with your own alerts

Free plan included, no credit card required. New organizations start with 14 days of Business.

Get started free