Notification Receivers for Shared Email Addresses and Webhooks
How receivers send an organization's or event's notifications to a shared email address or a webhook, with filters, pausing, and signing secrets.
A receiver sends notifications to a place instead of a person: a shared team mailbox, or an HTTPS address that another system listens on. Use one when a team needs the alerts without everyone following individual items, or when you want to feed event activity into another tool.
Receivers are available through the API. There is no screen for them in BackOps yet, so setting one up needs someone comfortable making API calls.
What a Receiver Is
A receiver belongs to an organization or to a single event, and it is either an email receiver, with an address, or a webhook receiver, with a URL that is checked before it is saved. Each receiver lists the notification types it receives, at least one, and gets only those types for its owner.
You can pause a receiver without deleting it and turn it back on later, or delete it permanently.
Webhook Signing
Each webhook receiver has a secret used to sign what BackOps sends, so the listener can confirm a request came from BackOps. The secret is shown once, when the receiver is created. Rotating it replaces the secret and shows the new one once, so store it where your integration can read it. Email receivers have no secret.
Permissions
Managing receivers needs the Notifications.ManageReceivers permission, which is part of the admin level on both organizations and events.
In the API
The Notifications API reference documents each operation: create a receiver, list receivers, update a receiver, deactivate a receiver, and rotate a secret.