Webhook adapters

Test before you connect

Preview exactly how a provider payload maps, then send a safe end-to-end test.

Before pointing a real monitoring system at WarnFire, you can rehearse in the console — first without any side effects at all, then with a real (but safely fenced) test page.

Open Configuration → Services and scroll to the Provider webhook adapters panel.

Preview a mapping

1. Choose the Adapter (for example alertmanager). The panel shows the exact web address your provider will use.
2. Paste a sample payload into Provider payload — the panel starts you off with a realistic example you can edit.
3. Press Preview mapping.

You’ll see precisely what WarnFire would make of it: the incident title, severity, the dedup key used for correlation, links, labels — the whole mapped event. Nothing is sent, nothing is created, no one is paged. Preview as many times as you like.

If the payload has a problem, the preview tells you why in plain terms (for example, an unsupported Alertmanager version) so you can fix your provider’s configuration before going live.

Send a test

When the preview looks right:

1. Pick a service from the dropdown next to Send test.
2. Press Send test and confirm.

This one is real: the payload travels the entire production path — validation, deduplication, incident creation, escalation — and pages whoever is on call for that service. That’s the point: you’re proving the whole chain, end to end.

Two safety properties to know:

• Test events live in their own lane. WarnFire tags test correlation keys separately, so a pasted copy of a real production alert can never touch, update, or close a real incident. Tests and production traffic cannot collide.
• Repeat clicks don’t pile up. Sending the identical test twice is recognized as a repeat — you won’t create a stack of duplicate incidents while experimenting. Change the payload and it counts as a new event, exactly like production.