Skip to main content
How it works Integrations Pricing Blog Sign in Start free trial

If it speaks webhooks, it works with CallPing.

There is no integration to install. Drop your CallPing webhook URL into your monitoring tool’s alert configuration. That is the entire setup.

Setup in three steps

  1. Copy your CallPing webhook URL. Find it on the Endpoints page in the portal.
  2. Paste it into your tool’s alert configuration. Most tools call this “webhook URL” or “outgoing webhook.”
  3. Send a test alert. You should hear your phone ring within a few seconds.

That is it. There is no API key dance, no OAuth flow, no agent to install on your servers. The endpoint UUID is the credential.

Compatible monitoring sources

“Compatible with” means these tools send webhooks in formats we parse out of the box. There is no partnership, certification, or vendor relationship implied — every tool below is your existing vendor, sending HTTP to our endpoint URL.

Monitoring and observability

Datadog
Compatible
Grafana
Compatible
Prometheus Alertmanager
Compatible
Sentry
Compatible
New Relic
Compatible

Uptime and synthetic monitoring

UptimeRobot
Compatible
Better Stack
Compatible
Statuscake
Compatible
Pingdom
Compatible — verify webhook URL
Healthchecks.io
Compatible
Hyperping
Compatible

SaaS, security, and platform alerts

Stripe
Compatible
Cloudflare alerts
Compatible
AWS CloudWatch
Via Lambda forwarder
GitHub Actions
curl in workflow

Custom scripts and bespoke sources

If your tool can run curl, hit fetch, or fire an HTTP POST, it works with CallPing. The minimum payload is a single key:

curl -X POST https://api.callping.app/api/wh/YOUR_UUID \
  -H "Content-Type: application/json" \
  -d '{"severity": "critical", "message": "Backup job failed"}'

The severity field decides which routing rule matches. Everything else is metadata you can match on with contains, gt, lt, etc.

Tools that need a small wrapper

A handful of tools ship payloads with severity nested inside an object. CallPing only reads top-level fields, so for these you either configure a custom payload template or run a one-line transformer.

  • PagerDuty (sending TO CallPing). Use a custom payload template that promotes event.severity to the top level.
  • Opsgenie webhooks (sending TO CallPing). Similar — use a custom payload template, or route on Opsgenie’s details.priority field with a contains rule.
  • AWS CloudWatch SNS subscription. Subscribe a small AWS Lambda function to your CloudWatch SNS topic and have the Lambda fetch() the CallPing endpoint with the CloudWatch event body forwarded as JSON. The same shape as the curl example on the How it works page, just inside a Lambda handler.

Things we do not have

  • Native installable plugins. We do not ship a Datadog plugin or a Grafana datasource. Both tools natively support outgoing webhooks; the plugin would add a dependency without adding a feature.
  • A marketplace. No app store, no integration directory, no certified-partner program. The webhook URL is the integration.
  • Pre-built mappers for every vendor’s payload shape. Most payloads have severity / message / priority / status at the top level. The exceptions are documented above.

Send your first test alert in five minutes.

Sign up, copy your endpoint URL, paste it into your tool, fire a test. If your phone does not ring, our contact form gets your message into our support queue.

Card required at signup. No charge for 14 days. Cancel any time from your billing page before day 14 to avoid the charge. By starting a trial, you agree to our Terms of Service, Privacy Policy, and Acceptable Use Policy — including your responsibility to obtain consent from every recipient you configure CallPing to call.