Skip to main content

Email Heartbeat Overview

Some hosts cannot open outbound HTTP (locked-down cron boxes, legacy servers) but can still send mail. Seiri treats an email to your monitor’s address the same as an HTTP ping.

Where it lives​

Services → Email Pings in cloud.seiri.app (page title: Email Heartbeat).

Email heartbeats are configured on top of an existing webhook — create the webhook under Core → Webhooks first.

Address shape​

{webhook_ref}@ping.seiri.app

Example: deno-xFY-7Yv@ping.seiri.app

The local part is the webhook ref only (not org-slug:ref). That differs from the HTTP ping URL, which uses the full endpoint ID.

Check-in methodIdentifier
HTTPhttps://ping.seiri.app/webhook/<org-slug>:<webhook-ref>/success
Email<webhook-ref>@ping.seiri.app

How it works​

  1. Create a Periodic or Cron webhook.
  2. Open Email Pings → Configure Email Heartbeat.
  3. Select the webhook, set an allowlist of senders, save.
  4. From the job, send mail to {webhook_ref}@ping.seiri.app when work finishes.
  5. Put [FAIL] or [ERROR] in the subject to report failure.

Allowlist and limits​

  • Allowlist entries: exact addresses (cron@example.com) or domains (*@trusted.com).
  • Empty allowlist = not configured (emails will not count).
  • Default rate limit: about 60 emails/hour per webhook.
  • HTML is stripped; attachments are ignored; oversized bodies are rejected.
Email Heartbeat page
Services → Email Pings — configure allowlist and rate limit per webhook

See Quickstart.