Sentinel
Open Console

Connectors

The destinations Sentinel can deliver to, and how to set each one up.

1 min read Updated Oct 21, 2026 Sentinel Platform Team
connectorsslackpagerdutywebhookdelivery

Available connectors #

  • Slack — post to a channel through an incoming webhook.
  • Microsoft Teams — post to a channel through an incoming webhook.
  • Google Chat — post to a space through an incoming webhook.
  • Discord — post an embed to a channel through a channel webhook.
  • Mattermost — post to a channel through an incoming webhook.
  • PagerDuty — raise an incident.
  • Opsgenie — raise an alert.
  • Webhook — deliver to any HTTP endpoint, signed.

Each connector renders its own setup form, so adding a destination is the same flow whichever one you choose.

Setting up a chat destination #

  • Create an incoming webhook in your chat application.
  • Paste the webhook URL into the connector.
  • Send a test delivery and confirm it arrives.
  • Point a workflow at the connector.

Setting up an incident destination #

  • Create an integration key in PagerDuty or Opsgenie.
  • Paste the key into the connector.
  • Send a test delivery and confirm the test incident arrives.
  • Point a critical-priority workflow at the connector.

Test deliveries are real

A test goes to the destination you configured and creates the incident or message it would normally create. It is recorded beside your real deliveries so the trail stays complete.

A general webhook #

The webhook connector delivers to any HTTP endpoint. It is the right choice when you are integrating with something the catalogue does not cover.

  • Method and URL — where to deliver.
  • Headers — any your receiver needs.
  • Signing secret — enables signature verification on the receiver.

Rotation #

  • Chat webhooks can be rotated in the chat application and updated on the connector.
  • Signing secrets can be regenerated from the connector.
  • Update the workflow's destination if you replace a connector.

Keep one connector per destination. Two workflows sharing a connector means you cannot tell which one delivered a message when you are reading the thread.