Alert Channels

Cronitorex can notify you about monitor events (failures, missed runs, timeouts, recoveries) through several channels. You can configure any number of channels and choose which event types each channel receives.

All channels are managed in the panel under Settings -> Notification Channels. Every channel has a Test button that sends a test notification only to that channel, so you can verify the configuration before relying on it.

Channel	Availability
Email	all plans
Telegram	all plans
Discord	all plans
Webhook	plan with webhook alerting
Slack	plan with Slack alerting

Email

The simplest channel. Leave the address field empty to use your account email, or enter a different address (for example a team alias).

Telegram

Telegram alerts are delivered by your own bot, so they are free and instant.

1. Open @BotFather in Telegram and send /newbot. Follow the prompts and copy the bot token (format 123456789:AAF...).
2. Add the bot to the chat or group where you want alerts, or open a direct chat with it, and send any message (for example /start).
3. Get the chat ID: open https://api.telegram.org/bot<TOKEN>/getUpdates in a browser and read chat.id from the response. Group IDs are negative numbers (for example -1001234567890).
4. In the panel, add a channel of type Telegram and paste the bot token and chat ID.
5. Click Test to confirm the message arrives.

Note: the bot token grants control over your bot. Cronitorex stores it for delivery only and never includes it in logs.

Discord

Discord alerts use channel webhooks, no bot required.

1. In Discord, open the target channel settings: Integrations -> Webhooks -> New Webhook.
2. Copy the webhook URL (it starts with https://discord.com/api/webhooks/).
3. In the panel, add a channel of type Discord and paste the URL.
4. Click Test. Alerts arrive as embeds, green for recoveries and red for failures.

Slack

1. Create an incoming webhook in your Slack workspace.
2. In the panel, add a channel of type Slack and paste the webhook URL (starts with https://hooks.slack.com/services/).
3. Click Test.

Webhook

Sends a JSON payload to any HTTP endpoint, useful for integrating with your own systems, on-call tools, or automation.

{
  "id": 123,
  "type": "failed",
  "monitor_name": "db-backup",
  "message": "Monitor db-backup failed",
  "metadata": {},
  "occurred_at": "2026-07-24T18:00:00+00:00"
}

• Method: POST (default) or GET (payload as query parameters).
• Custom headers: one per line as Header-Name: value, for example an Authorization header for your endpoint.
• Slack and Discord webhook URLs are rejected here on purpose: their APIs expect a different payload format. Use the dedicated Slack or Discord channel type instead.

Event types

Each channel subscribes to a subset of event types:

Event	Meaning
Failed	the job reported a failure
Missed	an expected run did not arrive in time
Timeout	the job started but did not complete in time
Degraded	the check is failing intermittently
Recovered	the monitor is healthy again
Still failing	periodic reminder while a failure is ongoing