INTEGRATION

Rocket.Chat

Posts to a channel via an incoming webhook. Works on any self-hosted Rocket.Chat.

How the wire-up works

Three things to know: the protocol, the credential, and what the alert payload looks like. The setup is the same on free and Pro.

Protocol
discord-webhook
Credential
Incoming webhook URL (created under the channel's Integrations → Incoming Webhooks) + optional channel name override.
Payload
Rocket.Chat payload with username, emoji, and an attachment block carrying the monitor name, status, latency, and a link to the endpoint detail page.

What it supports

The grid below describes what the channel itself supports once wired up. All channels are available on the free plan unless the badge says otherwise.

Free planSupportedNo card, no expiry.
Pro planSupportedSame on free and Pro.
InteractiveNot supportedOne-way push only.
Incoming mentionsNot supportedOutbound-only.
Rich attachmentsSupportedCards, embeds, colour-coded status.
TLS in transitSupportedHTTPS / WSS — no plaintext fallback.

When Rocket.Chat is the right pick

You self-host Rocket.Chat and want alerts to land in the same pane as the rest of the team conversation.

Wire Rocket.Chat to ZnowPulse in two minutes.

Free plan. No card. Cancel any time.