← All Features

Alert Contacts
Email, Slack & Webhook Delivery

Route monitoring alerts to the channels your team actually uses. Verified email, Slack Incoming Webhooks, and a stable JSON payload for any internal system — with test alerts to prove it works before you need it.

Start Monitoring Free
Channels

Three Delivery Channels, One Contact Book

Add contacts once and attach them to as many alert rules as you need. Every channel type shares the same event model, so you can mix email, Slack, and webhooks on the same rule without duplicating configuration.

  • Email — double opt-in verification
  • Slack Incoming Webhook — paste and go
  • Generic webhook — any HTTPS URL
  • Many contacts per rule, many rules per contact
[email protected]Email · Verified Apr 2
Active
#
#alerts-prodSlack Incoming Webhook
Active
{}
hooks.internal.acme.com/gopingerWebhook · JSON payload
Active
[email protected]Email · verification sent
Pending
Slack

Slack Alerts Without the OAuth Dance

Create an Incoming Webhook in Slack, paste the URL into GoPinger, and you're done. No Slack app to install, no workspace admin approval, no permissions review — just a message in the channel you chose the moment a rule fires.

  • One URL, no OAuth flow
  • Separate webhooks per channel — route by severity
  • Monitor name, incident cause, and timestamp included
  • Recovery notifications on the same channel
# alerts-prod14:03
GoPinger APP
🔴 Monitor down: api.acme.com
Rule: Monitor Down
Cause: HTTP 503 from 3 of 4 locations
Started: 14:02:15 UTC
Webhooks

Documented JSON Payload for Any Tool

Pipe alerts into your incident tool, your internal dashboard, PagerDuty, Opsgenie, or a self-built system. GoPinger sends a stable JSON POST with Content-Type: application/json and a documented schema for three event types — monitor.down, monitor.up, and test.

  • Stable payload schema, safe to parse
  • HTTPS POST, 10-second timeout
  • Includes incident ID for cross-system correlation
  • Recovery payload includes incident duration
POSThooks.internal.acme.com/gopinger
{
  "event": "monitor.down",
  "monitor_name": "api.acme.com",
  "monitor_url": "https://api.acme.com/health",
  "incident_id": "inc_8f3b2c",
  "cause": "HTTP 503 from 3 locations",
  "rule_name": "Monitor Down",
  "started_at": "2026-04-11T14:02:15Z",
  "timestamp": "2026-04-11T14:03:15Z"
}
Verify

Verify Before You Trust

New email contacts get a verification email on the spot; they stay unverified (and silent) until they confirm. Slack and webhook contacts skip verification but gain a "Send test" button so you can prove the channel works before a real incident relies on it.

  • Email double opt-in, resend on demand
  • Test alert per rule, not per contact — no copy/paste
  • Distinct test event payload — safe for webhooks
  • Unverified contacts silently skip real alerts — no lost signal
Email verified
[email protected] will now receive alerts from rules it is attached to.
Verification completed just now.
Ready to receive alerts

Frequently Asked Questions

Everything you need to know about GoPinger alert contacts.

What types of alert contacts does GoPinger support?

GoPinger supports three contact types today: email (verification required), Slack (via Incoming Webhook URL, auto-verified), and generic webhook (any HTTPS URL, auto-verified). You can attach multiple contacts to any alert rule.

Why do I have to verify my email contact?

Double opt-in prevents malicious actors from signing up other people for your alerts and protects your sender reputation. You receive a verification link the moment you add an email contact — one click and you are ready to receive alerts. You can resend the verification email at any time.

What does the webhook payload look like?

Every webhook is a JSON POST with Content-Type: application/json and User-Agent: GoPinger/1.0. Down events include monitor_name, monitor_url, incident_id, cause, rule_name, started_at, and a timestamp. Recovery events include monitor_name, monitor_url, incident_id, duration_seconds, resolved_at, and a timestamp. Test events contain a simple message field. Payloads are stable and documented.

Does the Slack integration require a Slack app?

No. Paste in your Slack Incoming Webhook URL and you are done. No OAuth, no app install, no admin approval. Messages arrive in the channel you chose when you created the webhook in Slack.

Can I test a contact before a real incident?

Yes. Every alert rule has a "Send test alert" button that delivers a synthetic notification to every contact attached to the rule. Use it after you add a new contact to prove the end-to-end pipeline works.

How many alert contacts can I have?

The per-plan limit is shown on the pricing page — from 2 contacts on the free tier up to 200 on Enterprise. The free tier covers email and webhook contacts; Slack, Microsoft Teams, and Freshdesk channels unlock on Starter and above. Upgrade if you need more.

Route Alerts to the Channels Your Team Uses

Email and webhooks on the Free plan, with Slack and Microsoft Teams on Starter and up — all verified, testable, and ready when you need them. No credit card, no per-contact fees.

Start Monitoring Free