Features

Notifications

7di alerts you the moment something changes. Browser push notifications reach you on desktop or phone instantly. Outgoing webhooks let you route those same alerts into Discord, Slack, or any HTTP endpoint.

Enable push notifications

  1. Click the bell icon in the top right of your dashboard.
  2. Click Enable notifications.
  3. Allow the browser permission prompt.

That is it. You will now receive push notifications from 7di even when the tab is in the background, as long as the browser is running.

What triggers a notification

  • Monitor goes down or errors — any widget whose status changes to down or error.
  • Monitor recovers — a previously down widget comes back up.
  • Webhook goes silent — a webhook widget stops receiving pings within its configured interval.
  • AI alert fires — a smart alert condition evaluates to true.
  • Low credits — your credit balance drops below 50 or 10.

Cooldown

Notifications include a cooldown to prevent spam. If a monitor goes down and stays down, you receive one notification, not one per check. A recovery notification fires when it comes back up.

Smart alert widgets have a configurable cooldown; you can set how long to wait before firing again if the condition remains true.

Notification history

All notifications are stored in the bell panel. Click the bell icon to see your recent notification history, even after you have dismissed the browser alerts.

Muting a page

You can mute a page to disable all notifications from its widgets. This is useful for pages you want to monitor visually but not be alerted by. Find the mute toggle in the page settings.

Multiple devices

Enable notifications separately on each device or browser you use. Each one registers independently and will receive alerts.

Outgoing webhooks

In addition to browser push, 7di can POST a notification payload to any HTTP endpoint when a monitor goes down or errors. This is how you send alerts to Discord, Slack, or your own services.

Go to Dashboard → Webhooks to add one. Each webhook has a name, a destination URL, and an optional page scope. If you scope it to specific pages, only monitors on those pages will trigger it. If left unscoped, it fires for all your monitors.

Webhook payload

Every outgoing POST sends JSON with the following fields:

{
  "type": "monitor_down" | "monitor_error",
  "title": "...",
  "body": "...",
  "monitor_id": "...",
  "timestamp": "2024-01-01T00:00:00.000Z",
  "embeds": [{ ... }]
}

The embeds array is formatted for Discord's webhook API, so pasting a Discord webhook URL works out of the box. Slack and other services that accept JSON POSTs work too using the title and body fields.

Testing a webhook

Each webhook in the list has a test button (the play icon). Clicking it sends a test payload immediately so you can confirm delivery before a real alert fires. The result shows the HTTP status returned by your endpoint.

Enabling and disabling webhooks

Use the power icon on each webhook to enable or disable it without deleting it. Disabled webhooks receive no payloads until re-enabled.

Notifications · 7di Docs