Integrations reference
Supported notification channel integrations, required credentials, and configuration details.
Notification channel integrations
Configure channels under Settings > Notification channels.
Slack
| Field | Description |
|---|---|
| Webhook URL | Incoming Webhook URL from your Slack app configuration |
| Channel | Optional override (default: the channel configured in the webhook) |
HOWLOPS posts a message with the incident summary, severity, and a direct link to the monitor. Slack must authorize the incoming webhook for your workspace.
To set up: In Slack, go to Apps > Incoming Webhooks > Add to Slack > select channel > copy the webhook URL.
Discord
| Field | Description |
|---|---|
| Webhook URL | Discord channel webhook URL |
In Discord: channel settings > Integrations > Webhooks > New Webhook > copy URL.
Telegram
| Field | Description |
|---|---|
| Bot token | Token from BotFather |
| Chat ID | Target chat or channel ID (prefix -100 for supergroups) |
Create a bot via @BotFather on Telegram, then send /newbot to obtain the token.
| Field | Description |
|---|---|
| Recipients | Comma-separated list of email addresses |
HOWLOPS sends email via its own transactional mail provider. No SMTP credentials are required.
PagerDuty
| Field | Description |
|---|---|
| Integration key | PagerDuty Events API v2 integration key |
In PagerDuty: Services > select service > Integrations > Add integration > Events API v2 > copy the Integration Key.
OpsGenie
| Field | Description |
|---|---|
| API key | OpsGenie API integration key |
| Region | us or eu |
In OpsGenie: Settings > Integrations > API > copy the API Key.
Generic webhook
| Field | Description |
|---|---|
| URL | Your endpoint URL (must accept POST application/json) |
| Secret | Optional; used to compute X-HOWLOPS-Signature-256 header |
See Webhooks reference for payload shapes.
Microsoft Teams
| Field | Description |
|---|---|
| Webhook URL | Incoming Webhook connector URL from your Teams channel |
In Teams: channel > ... > Connectors > Incoming Webhook > configure > copy URL.
Inbound integrations
Prometheus Alertmanager
HOWLOPS can receive Prometheus Alertmanager webhook alerts and convert them to incidents.
Endpoint: POST /api/v1/integration-rules (create a rule with type: alertmanager)
Alertmanager webhook config:
receivers:
- name: xinex
webhook_configs:
- url: https://api.example.com/api/v1/integrations/alertmanager/<rule_id>
send_resolved: true
Generic inbound webhook
Any system that can send an HTTP POST can trigger incidents via:
POST /api/v1/integrations/<rule_id>
Authorization: Bearer <integration_token>
Content-Type: application/json
{
"title": "Deploy failed",
"severity": "critical"
}
Integration matrix
| Integration | Direction | Auth method | Tier |
|---|---|---|---|
| Slack | Outbound | Incoming webhook URL | Free+ |
| Discord | Outbound | Incoming webhook URL | Free+ |
| Telegram | Outbound | Bot token + chat ID | Free+ |
| Outbound | None (managed) | Free+ | |
| PagerDuty | Outbound | Events API v2 key | Standard+ |
| OpsGenie | Outbound | API key | Standard+ |
| Generic webhook | Outbound | Optional HMAC secret | Free+ |
| Microsoft Teams | Outbound | Incoming webhook URL | Free+ |
| Prometheus Alertmanager | Inbound | Integration token | Standard+ |
| Generic inbound webhook | Inbound | Integration token | Standard+ |
See also
Was this page helpful?