Zulip alerts
Send kwatch incident alerts to Zulip. Use the interactive manager for installation and credential setup. This page explains the provider fields and shows a minimal configuration fragment.
Before you start, have these values ready:
emailโ Bot email.tokenโ Bot API key.channelโ Channel/stream to post to.
Credentials, tokens, keys, passwords, and webhook URLs must be mounted
from a Kubernetes Secret. Use an exact ${file:/absolute/path} reference
for every field marked Secret.
Configurationโ
| Field | Type | Required | Secret | Validation | Default | Description |
|---|---|---|---|---|---|---|
email | string | yes | no | โ | โ | Bot email |
token | string | yes | yes | โ | โ | Bot API key |
channel | string | yes | no | โ | โ | Channel/stream to post to |
url | string | no | no | url | https://zulip.example.com/api/v1/messages | Server URL (default: https://zulip.example.com/api/v1/messages) |
title | string | no | no | โ | โ | Custom title |
routes | json | no | no | json | โ | Optional JSON route filters. |
retry.maxAttempts | integer | no | no | integer | โ | Optional maximum retry attempts. |
retry.delay | string | no | no | โ | โ | Optional retry delay, for example 5s. |
fallback | string | no | no | โ | โ | Optional fallback provider name. |
Minimal exampleโ
alert:
zulip:
email: <email>
token: "${file:/config/zulip-token}"
channel: <channel>
Add routes, retry, and fallback when you need delivery filtering or recovery. See the channels overview for guidance, or the complete provider reference for the catalog-wide view.