Expanded inbound catalog
Connect popular monitoring, error-tracking, CI/CD, and status-page products to HowlOps.
HowlOps has inbound presets for monitoring, error-tracking, CI/CD, and
status-page products. Each preset creates a credential-bearing URL under
/api/v1/webhooks/incoming/<token>, understands that product's alert format,
and looks for the provider's stable event key. A recovery closes the existing
incident only when the source sends a supported recovery state with the same key.
Setup matrix
| Product | Setup in the source | Recovery behavior |
|---|---|---|
| Better Stack | Outgoing webhook, incident_change, default body | resolved closes started/reopened by incident ID |
| New Relic | Workflow webhook using the template shown in the HowlOps drawer | Closed issue closes activated issue by issueId |
| Checkly | Webhook alert channel using the drawer template | ALERT_RECOVERY closes failure/degraded by CHECK_ID |
| Splunk | Native webhook alert action | Optional recovery search uses the same correlation_key and status=resolved |
| Sumo Logic | Webhook connection using the drawer template | Resolved states close by monitor Id |
| Zabbix | Webhook media type using the parameters and script in the drawer | {EVENT.VALUE} 0 closes value 1 by {EVENT.ID} |
| GitHub Actions | Repository webhook subscribed to Workflow runs | Next successful run closes a failed run for the same repository/workflow/branch |
| GitLab CI | Project webhook subscribed to Pipeline events | Next successful pipeline closes failure for the same project/pipeline/ref |
| updown.io | Add the generated URL under Settings → Webhooks | UP/valid/renewed events close matching availability and TLS incidents |
| Atlassian Statuspage | Subscribe to a public page using Webhook | Resolved incidents and operational components close their matching events |
| Cronitor | Add the generated URL under Integrations → Webhooks | Native RECOVERY closes ALERT by monitor key |
| Healthchecks.io | Use the JSON body copied from the HowlOps drawer for Down and Up | up closes down by check UUID |
| Rollbar | Project webhook rules for new/reopened/reactivated/resolved items | resolved_item closes by item ID |
| Bugsnag | Project webhook for new/reopened errors and state changes | A fixed/ignored/snoozed error closes by errorId |
| CircleCI | Project webhook subscribed to Workflow Completed | Next successful workflow closes failure for the same project/workflow |
| Vercel | Team webhook for deployment error/cancelled/succeeded | Success closes failure for the same project/target |
The setup drawer is the source of truth for the exact current payload template. Copy it as a whole: changing or omitting the ID field can prevent deduplication and auto-resolution.
Verify the connection
Send one failure event from the source and confirm the integration's Last received time changes. Then send the source's native recovery event and confirm it resolves the same incident. If the source has no recovery event, resolution remains a manual action.
After testing with a temporary URL or shared log, rotate the integration token and update the source. Rotation invalidates the previous URL immediately.
Payload validation
HowlOps rejects empty, malformed, oversized, and provider-incompatible payloads instead of creating a placeholder incident. JSON bodies are limited to 1 MiB. UptimeRobot form data and query-string payloads remain supported; JSON arrays are accepted for providers such as updown.io that batch events.
Was this page helpful?