Documentation

Choose and manage integrations

Connect a team channel or your own application to confirmed outage and recovery events.

What you’ll accomplish

An enabled destination with the right event subscriptions and a successful connection test

In this guide

Choose a destination

Open Settings → Integrations in the workspace you want to configure. The catalog separates available integrations from planned providers. A planned provider is not yet a working destination.

Use Slack when responders work in a shared channel. Use Signed webhooks when your own application needs to receive incident events. Both support confirmed outages and recoveries; they are not a stream of every individual check.

Workflow walkthrough

From incident to destination

Monitor policy

An incident meets the configured confirmation requirements. Individual failed checks do not trigger these integration messages.
A simplified view of an integration delivery. Select a step to explore it.

Set up the connection

Pick an available integration

Select the provider’s setup action. Give the connection a name that identifies its purpose, such as Production alerts.

Configure the destination

For Slack, follow the incoming webhook guide. For your own receiver, follow the signed webhook guide, including its endpoint and signature requirements.

Choose the events

Subscribe to confirmed outages, recoveries, or both. For a response channel, including recovery helps the team see when the incident has ended.

Test the connection

Open Connected and use Test. Confirm that the intended channel or application received the test, not just that a similar destination is working elsewhere.

Understand access

Integration management depends on your workspace permissions. If setup or management controls are disabled, ask a workspace administrator to review your access. Changing workspaces changes which integrations you manage.

Do not paste webhook URLs or signing secrets into support messages, public status updates, or screenshots. Treat them as credentials.

Pause or remove a destination

Use the enabled control in Connected to pause a destination temporarily. Enable it again when you are ready for future events. Do not assume a pause will replay missed events later.

Remove a connection when it should no longer receive future events. Existing notification history remains available. A request already in flight may still finish.

If the test fails

Check the saved destination, permissions at the receiving service, and whether the receiver is reachable. Use notification troubleshooting to separate event selection from receiver problems.

Need a hand with this guide?

Tell us where you got stuck. We’re here to help.

Contact us