Connect a destination
A destination is a Slack channel Feather posts to, backed by a Slack integration connection. Discover the channels your Slack app can post to, then create a destination:Enable and route event types
Browse the catalog of notification event types withGET /v1/notifications/types. Each type has a category, default severity, and payload schema, merged with your org’s configuration.
The fastest start is to enable the recommended set:
delivery_mode is immediate, hourly_digest, or daily_digest. Route an event type to a specific destination with PUT /v1/notifications/routes ({ event_type, destination_id, enabled }); events without a route fall back to your default destination.
Settings, templates, and testing
- Settings —
GET/PUT /v1/notifications/settingsset thedefault_destination_id, timezone, quiet hours, and digest send time. - Templates — customize the message per event type and channel with
GET/PUT /v1/notifications/types/{event_type}/template. Preview and validate before saving with.../template/previewand.../template/validate. - Test — fire a real notification synchronously with
POST /v1/notifications/types/{event_type}/test-send. - Delivery log — see what was sent (and why something wasn’t) with
GET /v1/notifications/delivery-log.
Next steps
Evaluations
Evaluation failures are a common notification trigger.
Connect an integration
Connect Slack so notifications have somewhere to go.