Get alerted wherever your team works.
Email, Slack, and webhooks — so you can plug Beaconmon into the tools you already use, or build your own automation on top.
Instant alert emails the moment a monitor goes down or recovers. Formatted to be clear at a glance — no digging through paragraphs to understand what happened.
Slack
Beaconmon posts to any Slack channel when a monitor changes state. Your team sees it together — no more "did you get the email?" conversations.
Webhooks
Send a JSON payload to any URL when a monitor event fires. Build custom automations — auto-create a Jira ticket, post to Discord, trigger a PagerDuty alert, or anything else your stack needs.
Coming soon
More ways to get alerted, without leaving this page to check your monitoring tool.
SMS
Text alerts for when email and Slack aren't enough. Ideal for on-call scenarios or critical production monitors. Business plan only.
Alert integration FAQ
Can I send alerts to multiple channels at the same time?
Yes. You can add as many alert channels as your plan allows (Pro: up to 5, Business: unlimited) and each monitor can notify any combination of them. Use email for your own inbox, Slack for your team, and a webhook for your ticketing system — all from the same monitor.
What events trigger an alert?
Beaconmon fires an alert when a monitor transitions to DOWN (after 2 consecutive failed checks from multiple locations) and again when it recovers to UP. SSL and domain expiry warnings fire on a tiered schedule at 30, 14, and 7 days before expiry. You can choose to receive only DOWN alerts, only recovery alerts, or both.
How do I connect Beaconmon to Slack?
In the dashboard, go to Alert Channels → Add Channel → Slack. You'll be prompted to authorise via Slack OAuth and pick a channel. No webhook URL to copy-paste — it's a single click.
What does the webhook payload look like?
The POST body is a JSON object with event (monitor.down or monitor.up), monitor_id, url, status_code, confirmed_locations (array of region slugs), incident_id, started_at, and optionally duration_ms on recovery. HTTPS only; Beaconmon does not follow redirects for security reasons.
Can I use webhooks to connect to PagerDuty, Discord, or Jira?
Yes — webhooks are designed for exactly this. Point the channel at a PagerDuty Events API URL to auto-create incidents, a Discord channel webhook URL for team notifications, or your own serverless function to open a Jira ticket. Any service that accepts an inbound HTTP POST will work.
Is there a retry policy if my webhook endpoint is down?
Yes. Beaconmon retries failed webhook deliveries up to 5 times with exponential backoff. If all retries fail, the failure is logged and visible in the channel's delivery history so you can investigate.
Ready to get alerted in the right place?
Set up monitoring in 5 minutes. Free forever for 10 monitors.