Alert channels

Email, Telegram and signed webhooks.

Channels live on your account; each monitor picks which of them to use. Add them on the Alerts page.

Email

Available on every plan. Add as many addresses as you like — one for you, one for whoever is on call.

Add a Telegram channel, then send our bot the eight-character code it gives you. The bot links that chat to your account and replies to confirm. From then on alerts arrive as messages.

The link works from a group chat too: add the bot to the group and send the code there, and the whole team gets alerted.

Webhook

We POST JSON to your URL:

{
  "sent_at": "2026-08-22T11:04:02Z",
  "event": "monitor.down",
  "level": "down",
  "title": "API — production is down",
  "body": "Expected 200, got 502",
  "url": "https://saasfoundry.app/app/monitors/12/",
  "facts": {
    "Monitor": "API — production",
    "URL": "https://api.example.com/health",
    "Reason": "Unexpected status code",
    "Status": "502"
  }
}

Every request carries X-SaaSFoundry-Signature: t=<unix>,v1=<hex>, where the digest is HMAC-SHA256(secret, "{t}.{body}"). Verify it the same way you would verify Stripe.

Event types

Event	Sent when
`monitor.down`	A monitor fails its threshold
`monitor.up`	It recovers
`monitor.ssl_expiring`	30, 14, 7, 3 or 1 days before a certificate expires
`monitor.domain_expiring`	Same thresholds, for the domain registration
`monitor.dns_changed`	DNS records moved
`monitor.schema_changed`	A JSON response changed shape
`webhook.delivery_failed`	A forward exhausted its retries
`test`	You pressed Test