Notifications

A monitor on its own just watches — to actually hear about a problem, you need to connect somewhere for CuliPulse to send the alert. These are called destinations.

Supported destinations

• Telegram — get alerts as messages from a bot, in a chat or group.
• Slack — get alerts posted into a channel of your choice.
• Webhook — CuliPulse sends the alert as an HTTP request to a URL you control, so you can wire it into your own tools (a custom bot, an incident-management system, and so on).

Connect a destination

1. Go to Notifications.
2. Click Add destination.
3. Choose Telegram, Slack, or Webhook and follow the steps to connect it (for Telegram and Slack this is a quick sign-in/authorize step; for a webhook, you provide the URL to send alerts to).
4. Send a test alert to confirm it arrived, then choose which monitors should alert to this destination.

Once connected, a destination shows up in your list where you can rename it, pause it, send another test alert, change which monitors use it, or remove it.

Need a different channel?

If you need a destination CuliPulse doesn’t support yet (email, Discord, and others are on the roadmap), the Notifications page has a Request a channel form — tell us what you need.

Using notifications from your own code

If you’d rather receive alerts in your own system directly, a webhook destination or the API are the way to integrate CuliPulse with your existing tools.