Integrations

Route alerts from your monitoring stack to phone calls, Telegram and on-call escalation

WardenPoint accepts a webhook or REST call from any source you already trust — Grafana, Prometheus Alertmanager, Zabbix, Sentry, Uptime Kuma, Laravel or a custom script — and fans the alert out across eight delivery channels until somebody acknowledges.

Start free View API examples
Delivery channels
8
Source presets
7+
Public API
REST

Anatomy of one alert

LIVE
Grafana → webhook
checkout p99 latency above SLO
WardenPoint
normalise · route · escalate
Telegram
Voice call
Email

Sources

Plug in the tools your team already runs

Each source has a dedicated guide with payload examples and the escalation policy we recommend. Every chip links to a step-by-step setup.

Grafana
Contact-point webhook
Prometheus
Alertmanager receiver
Zabbix
Action webhook
Sentry
Issue alert
Uptime Kuma
Downtime alert
Laravel
Exception channel
Webhook
Any JSON source
Datadog
Monitor webhook
AWS CloudWatch
SNS subscription
GitHub
Webhook (signed)

Anatomy

One webhook in. Multi-channel timeline out.

Every integration follows the same four-step pipeline: receive, normalise into a typed payload, route per recipient policy, escalate until acknowledged. No glue code on your side.

  1. 01
    Receive

    Your source sends an HTTPS webhook or signs a REST call with an API key. Either route accepts the same payload contract.

  2. 02
    Normalise

    WardenPoint parses the payload into a typed NotificationPayload, attaches your company context and stamps a UUID for the lifecycle.

  3. 03
    Route

    The channel resolver picks the recipient's preferred channels for this priority — Telegram voice, PSTN call, SMS, WhatsApp, email or Viber.

  4. 04
    Escalate

    If the responder does not acknowledge within the timeout, the escalation chain moves to the next step and channel automatically.

Incoming alertPOST
POST /api/v1/notifications/send
 
{
"recipient_uuid": "00000000-0000-4000-8000-000000000001",
"message": "Checkout p99 latency above SLO for 5m",
"priority": "critical",
"source": "grafana"
}
WardenPoint fan-out202
{
"status": "queued",
"channels_planned": [
"telegram_voice",
"voice_call",
"email"
],
"escalation_chain_id": "esc_4j2k9bMcvL"
}

Catalogue

Per-source setup, in plain language

Open any integration to see the exact webhook URL, signing instructions, payload example and the escalation policy we recommend for that source.

Grafana
Monitoring · Dashboards

Add WardenPoint as a contact point. We accept Grafana's default webhook payload and label-based routing.

WebhookLabels routingAcknowledgement
Prometheus Alertmanager
Metrics · Alerts

Configure a webhook receiver in alertmanager.yml. Grouped alerts collapse into one incident with a single UUID.

ReceiverGroupingResolve hook
Zabbix
Infrastructure · Triggers

Create a Zabbix media type that posts a JSON body to WardenPoint. Severity maps directly to alert priority.

ActionSeverity mapTrigger context
Sentry
Errors · Releases

Use Sentry's webhook integration to escalate critical issues. Filter by environment, level or release tag.

Issue alertRelease contextTags
Uptime Kuma
Uptime · Monitors

Point any monitor's webhook notification to WardenPoint. Downtime acknowledgement cancels the chain.

Per monitorDowntimeRecovery
Laravel
Frameworks · Notifications

Use the standard Notification channel or a Monolog handler to escalate production exceptions and failed jobs.

Notification channelMonologFailed jobs
Custom webhook
Generic · Any source

Anything that can POST JSON works — internal services, GitHub Actions, schedulers, IoT devices, in-house tools.

JSON inAPI key authUUID lifecycle
Datadog
Monitoring · APM

Add WardenPoint as a Datadog webhook. Monitor priority maps to severity and a recovery posts a Resolved notice.

WebhookPriority→severityRecovery
AWS CloudWatch
AWS · Alarms

Subscribe an SNS topic to WardenPoint over HTTPS. CloudWatch alarms arrive as notifications; we auto-confirm the subscription and an OK state posts a Resolved notice.

SNS HTTPSAuto-confirmResolve notice
GitHub
CI/CD · Security

Add a repository or organization webhook. Failed Actions runs and code scanning / Dependabot / secret alerts page your on-call; a passing run resolves the prior failure.

Signed webhookActionsSecurity alerts
Email-to-alert
Inbound mail · Any tool

Point any tool's alert email at a unique inbox. The subject becomes the title, keywords set severity, and a dedup_key line gives you exact correlation.

Managed inboxSubject parsingPagerDuty parity

Patterns

Three integration shapes

Most teams reach for one of these. The contract on the wire is the same.

Webhook-first

Paste the WardenPoint URL into your monitoring tool's notification settings. Zero code, zero deploys.

$ https://api.wardenpoint.com/hooks/{key}

REST API

Call POST /api/v1/notifications/send from your service. Authenticate with an X-API-Key header.

$ curl -X POST /api/v1/notifications/send

Framework adapter

Wrap WardenPoint in a Laravel Notification channel, a Node logger transport or a Python handler.

$ $user->notify(new IncidentAlert($payload))

Frequently asked

Integration questions, answered

No. Every supported source has a dedicated webhook path that accepts its native payload. If your source can POST JSON, the only setup is pasting the WardenPoint URL into its notification settings.
Start in 5 minutes

Connect your first integration on the free plan

No credit card. Send a test webhook from Grafana, Alertmanager or curl and watch the escalation timeline render in real time.

Start free Talk to engineering
  • Free plan
  • No credit card
  • Test webhook in 5 minutes