DOCS

Integrations reference

Supported notification channel integrations, required credentials, and configuration details.

Notification channel integrations

Configure channels under Settings > Notification channels.

Slack

FieldDescription
Webhook URLIncoming Webhook URL from your Slack app configuration
ChannelOptional 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

FieldDescription
Webhook URLDiscord channel webhook URL

In Discord: channel settings > Integrations > Webhooks > New Webhook > copy URL.

Telegram

FieldDescription
Bot tokenToken from BotFather
Chat IDTarget chat or channel ID (prefix -100 for supergroups)

Create a bot via @BotFather on Telegram, then send /newbot to obtain the token.

Email

FieldDescription
RecipientsComma-separated list of email addresses

HOWLOPS sends email via its own transactional mail provider. No SMTP credentials are required.

PagerDuty

FieldDescription
Integration keyPagerDuty Events API v2 integration key

In PagerDuty: Services > select service > Integrations > Add integration > Events API v2 > copy the Integration Key.

OpsGenie

FieldDescription
API keyOpsGenie API integration key
Regionus or eu

In OpsGenie: Settings > Integrations > API > copy the API Key.

Generic webhook

FieldDescription
URLYour endpoint URL (must accept POST application/json)
SecretOptional; used to compute X-HOWLOPS-Signature-256 header

See Webhooks reference for payload shapes.

Microsoft Teams

FieldDescription
Webhook URLIncoming 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

IntegrationDirectionAuth methodTier
SlackOutboundIncoming webhook URLFree+
DiscordOutboundIncoming webhook URLFree+
TelegramOutboundBot token + chat IDFree+
EmailOutboundNone (managed)Free+
PagerDutyOutboundEvents API v2 keyStandard+
OpsGenieOutboundAPI keyStandard+
Generic webhookOutboundOptional HMAC secretFree+
Microsoft TeamsOutboundIncoming webhook URLFree+
Prometheus AlertmanagerInboundIntegration tokenStandard+
Generic inbound webhookInboundIntegration tokenStandard+

See also

Was this page helpful?