Notifications

SitePulse notifies your team when automatic monitoring opens, escalates, or resolves issues, and when manual checks complete or fail in the background.

​

Notification configurations

Notification destinations are managed by admins and owners. A team can have multiple destinations across these channels: Each configuration:

• Subscribes to Issue detected and/or Issue resolved events
• Applies to all check tools or only specific tools (Status, SSL, DNS, Broken Links, Performance)
• Can be enabled, disabled, and tested independently

Because each configuration is independent, you can route different tools or environments to different destinations. Notification configurations determine where alerts go. The conditions for opening issues (thresholds, confirmation retries, follow-up timing) are controlled by monitoring settings.

​

When notifications are sent

​

Issue lifecycle notifications

When automatic monitoring opens an issue or marks one resolved, SitePulse sends notifications to all enabled destinations that subscribe to the matching event and tool scope.

​

Issue escalation

When escalation is enabled, SitePulse schedules follow-up reminders at the intervals you select (15 minutes through daily). Escalation reminders are delivered to notification configurations subscribed to Issue detected. No separate channel setup is required. Reminders stop when the issue is resolved or is no longer in an active state (open or acknowledged). Quiet time suppresses escalation the same way it suppresses initial issue alerts.

​

Manual check notifications

When you run a manual check, SitePulse can notify the team on completion or failure (for longer-running checks like SSL, broken links, or performance that finish in the background). These notifications do not depend on automatic monitoring thresholds and do not open issues.

​

Notification channels

​

Email

Add email addresses that receive issue alerts. Each email notification typically includes:

• Summary of what was detected
• Severity (critical / warning / info)
• The affected site
• Key details from the check result

​

Slack

Slack app — an OAuth connection: authorize the SitePulse app and pick a channel. No webhook URL is required. Slack webhook — a Slack incoming webhook URL, if you prefer webhook-based delivery.

​

Discord

Authorize the SitePulse Discord integration and choose a channel. SitePulse stores the incoming webhook returned by Discord and formats issue alerts as Discord embeds.

​

Microsoft Teams

A Microsoft Teams incoming webhook URL. SitePulse formats messages for Teams workflow webhooks.

​

Generic webhook

An HTTP endpoint (GET or POST) that receives issue lifecycle events. Use webhooks to integrate with PagerDuty, custom automation, or other systems. See Webhook notifications for configuration fields, payload schemas, headers, delivery behavior, test vs production payloads, and URL requirements.

​

Testing destinations

HTTP-backed destinations can be tested from the notification configuration. Test delivery verifies connectivity and formatting, but it sends a test payload, not a real issue payload.

​

In-app notifications

While using the SitePulse dashboard, issue lifecycle notifications appear in real time (subject to quiet time and your permissions).

​

Quiet time

Quiet time suppresses outbound notifications during a daily window. Use it for overnight periods or planned maintenance. Checks continue to run during quiet time — only outbound notifications are suppressed. Issues can still open, acknowledge, and resolve.