Setup
Create a Mattermost incoming webhook
- In Mattermost, open Main Menu → Integrations → Incoming Webhooks
- Click Add Incoming Webhook
- Choose a display name (e.g., “DevHelm”) and a default channel
- Click Save and copy the generated webhook URL (e.g.,
https://mattermost.example.com/hooks/xxxxxxxxxxxx)
Configuration
| Field | Description | Required |
|---|---|---|
webhookUrl | Mattermost incoming webhook URL | Yes |
channel | Override the webhook’s default channel (e.g. incidents or @username) | No |
iconUrl | Publicly accessible URL for a custom bot icon | No |
Channel and icon overrides
channel and iconUrl only take effect if your Mattermost server permits webhook overrides. Enable System Console → Integrations → Integration Management → Enable integrations to override usernames and override profile picture icons. The iconUrl must be reachable from your Mattermost server — relative paths or internal-only URLs are ignored.
Troubleshooting
Webhook disabled or returns HTTP 403
Webhook disabled or returns HTTP 403
Incoming webhooks can be turned off per-server. Confirm an administrator has enabled System Console → Integrations → Integration Management → Enable Incoming Webhooks, and that the webhook itself hasn’t been deleted under Integrations → Incoming Webhooks.
Channel override has no effect
Channel override has no effect
The webhook posts to its configured default channel unless the server allows overrides. Enable Enable integrations to override usernames and icons in the System Console, then re-run
devhelm alert-channels test <channel-id>.Self-hosted server with a self-signed certificate
Self-hosted server with a self-signed certificate
DevHelm requires a valid TLS certificate for the webhook host. Install a certificate from a trusted CA (e.g. Let’s Encrypt) on your Mattermost instance — self-signed certificates are rejected during delivery.