Send PD Uptime & Status transition alerts from Blesta to a team notification endpoint using Pro. The webhook supplements email and can carry the monitor name, target, event and time to an HTTPS receiver.

Prepare the receiver

Confirm Pro is active and choose an authorised HTTPS endpoint that accepts JSON POST requests. Incoming Slack or Discord webhooks can use the payload’s message fields; another receiver can use its structured event fields. Review what the destination will receive, including monitor labels and target addresses.

Keep the full webhook URL private when it contains an embedded token. Do not put it in a public knowledge-base example, screenshot or monitor label.

Save the webhook setting

1. Open PD Modules → Uptime → Settings.
2. Find Send alerts to a webhook (Pro) and enter the intended HTTPS URL.
3. Review Who to alert, since webhook delivery is additional to email.
4. Review Also tell me when it comes back if recovery events should be sent too.
5. Save, then reopen the settings to check the configured destination through your normal private administrator workflow.

The payload includes plain text and content messages as well as event, monitor, target and at fields. Event values distinguish down and recovered. Plan the receiver around that payload rather than assuming the module supports arbitrary authentication headers or a custom payload builder.

Verify delivery at the receiver

Check a controlled or naturally occurring transition in Monitors and Incidents, then inspect the receiver’s own delivery evidence. Saving the URL or seeing a successful monitor action does not prove the receiver accepted the POST. The webhook path does not provide a persistent retry queue for an unchanged outage.

If nothing arrives, check Pro status, HTTPS, the saved URL, the actual state transition and receiver configuration. Avoid repeated manual check rounds as a way to resend an unchanged state.

See the PD Uptime & Status Blesta guide for related tasks, or explore PD Uptime & Status.