Integrations

Two directions

HowlOps integrations do one of two jobs:

Direction	What happens
Notification destination	HowlOps sends an alert, incident update, or recovery to chat, ticketing, paging, push, or webhook infrastructure.
Incoming source	Another service sends a webhook. HowlOps normalises its state, severity, and stable identifier into the incident lifecycle.

An incoming cloud or observability integration is webhook ingestion. It does not connect a cloud account, install an agent, poll metrics, or import infrastructure inventory. GitHub Actions and GitLab CI are incoming workflow or pipeline events, not repository access. HowlOps does not provide a container-registry or DNS-provider integration.

Available connections

This catalog reads the provider lists used by the platform. Generic transports such as email, SMS, voice, and webhooks use product icons; named services use the same brand marks as the Integrations screen.

Add a notification destination

1. Open Integrations → Channels.
2. Choose the destination.
3. Enter the fields requested for that provider, then save.
4. Send a test from the channel menu.

Some providers use OAuth or a managed bot. Others require a webhook URL, API token, routing key, or service credentials. The integration reference lists the exact fields and the supported direction for each provider.

Ticketing destinations create an issue or ticket from a notification. Unless a provider page explicitly says otherwise, closing that ticket does not resolve the HowlOps incident and later incident updates do not edit the original ticket.

Add an incoming source

1. Open Integrations → Hub.
2. Create an incoming integration and choose the source type.
3. Copy the generated URL into the external service's webhook configuration.
4. Send a test event and confirm that Last received changes.

For most sources, the unguessable token in the URL is the credential. Store the URL as a secret. Rotating the integration creates a new token and invalidates the previous URL immediately. CloudWatch via SNS also verifies the SNS signature and pins the topic after the first valid message.

Incoming request bodies are limited to 1 MiB. A provider event that does not contain the stable fields required by its parser is accepted as a request but does not create a placeholder incident.

Choose a guide

• Prometheus Alertmanager
• Grafana alerting
• Generic incoming webhook
• Slack notifications
• Microsoft Teams Workflows
• Outbound webhook payload and signing