Destination types
A destination type defines which third-party service your notifications are sent to and how they are formatted. Each destination type includes its own configuration schema and payload structure, allowing Notification Center to deliver messages to Slack, PagerDuty, HTTPS endpoints, and more.
Understand why destination types matter
Destination types ensure notifications are delivered correctly and consistently by defining both connection details and message schemas for each vendor.
Each destination type specifies:
- connector configuration fields such as authentication keys and endpoints
- message schema that defines the notification payload
- supported payload types for different types of messages
Configure connectors for each destination
Each destination type includes a dedicated connector configuration that tells Notification Center how to communicate with the external service.
Use connectors to:
- enter required connection parameters such as URLs, tokens, or headers
- define payload structure for HTTP-based or vendor-specific formats
- apply dynamic fields to support variable routing and templating
See Connectors for setup instructions.
Define message structure and templates
Message configuration controls how a notification payload is formatted for each destination. Each destination type supports one or more payload schemas, which presets use to generate consistent, reusable templates.
Use message configuration to:
- choose or customize the payload type for your vendor
- build presets that standardize notification formatting
- preview the final message as it will appear in the destination system
See Presets overview for more information.
Explore supported destination types
Notification Center currently supports the following destinations:
| Destination type | What it does | Setup guide |
|---|---|---|
| Generic HTTPS | Sends notifications to any HTTP or HTTPS endpoint. | Generic HTTPS connector |
| PagerDuty | Sends alerts to PagerDuty services using integration keys. | PagerDuty connector |
| Slack | Delivers formatted notifications to Slack channels. | Slack connector |
Each destination type includes setup steps, configuration fields, and message schemas aligned with the vendor’s API.
Next steps
- Connectors: Create connectors for each destination type you want to use.
- Presets overview: Configure message templates that follow each destination’s schema.
- Routing overview: Route alerts and cases to the right destination types using labels and conditions.