Notifications and webhooks
Get a message when something happens in your organization: a server is created or deleted, a backup starts, your balance runs low, a member joins and more. Messages can go to:
| Channel | What you need |
|---|---|
| Webhook | An https:// address on your own server that accepts POST requests. |
| Up to five email addresses. | |
| Slack | An incoming webhook URL for the Slack channel. |
| Discord | A webhook URL for the Discord channel. |
| Telegram | A chat ID, and a bot token unless we provide a bot. |
| A phone number with country code. Only shown once WhatsApp is available on the platform. |
Open Organization › Notifications. Owners and Admins can manage channels; other roles don't see this page.
Add a channel
- Under Add channel, enter a Name you'll recognise, e.g. Ops team on Slack.
- In Send to, choose the channel type and fill in its fields (see below).
- Tick the Events to send. All / none ticks or clears a whole group.
- Leave Enabled ticked and select Add channel.
- Select Send test next to the channel. Within a few seconds the test message should arrive, and Recent messages shows Delivered.
To change a channel, select Edit. Untick Enabled to pause it without losing its settings. Delete removes it and its message history.
Slack
In Slack, open Apps, add Incoming WebHooks, choose the channel and copy the Webhook URL (it starts with https://hooks.slack.com/). Paste it into Slack incoming webhook URL.
Discord
In Discord, open the channel's Edit channel › Integrations › Webhooks › New webhook, then Copy webhook URL (it starts with https://discord.com/api/webhooks/).
The URL works like a password, so after saving it is never shown again. When you edit the channel, leave the field empty to keep it.
Telegram
- If the form says Bot token (optional), you can use our bot: open it in Telegram (its name is shown under the field) and select Start. To post in a group, add the bot to the group.
Otherwise, create your own bot: message @BotFather, send
/newbot, follow the steps and paste the token it gives you (123456789:AA…) into Bot token. Then start a chat with your bot, or add it to your group. - Find the Chat ID:
- For yourself: message @userinfobot; it replies with your ID, e.g.
123456789. - For a group: add @RawDataBot to the group for a moment; the ID starts with
-, e.g.-1001234567890. Remove that bot afterwards. - For a public channel: use its
@usernameand make the bot an admin of the channel.
- For yourself: message @userinfobot; it replies with your ID, e.g.
- Select Send test. Bad Request: chat not found means the bot can't write to that chat yet: start the chat or add the bot first.
Enter your number with its country code, e.g. +919876543210. Messages come from our WhatsApp Business number. If WhatsApp isn't in the Send to list, it hasn't been set up on the platform yet.
Enter up to five addresses separated by commas. Each event is one email.
Events
| Group | Events |
|---|---|
| Instances | Created, deleted, started, shut down, rebooted, powered off, action failed, reinstalled, resized, hostname changed, root password reset, rescue mode started or ended, console opened |
| Backups | Turned on or off, backup started, restore started, backup deleted |
| Billing | Balance running low, instance suspended for balance, instance resumed after payment, funds added, free credit added, coupon redeemed, licence expiring soon |
| Team and access | Member invited, joined, removed or role changed; SSH key added; cloud account connected or disconnected |
Balance running low is sent once when your balance covers less than about three days of your running servers, and again only after it has been topped up and runs low once more. The owner and Billing members also get an email, whether or not you set up a channel.
Recent messages
Recent messages lists what was sent in the last 30 days and whether it arrived:
- Delivered: the service accepted the message.
- Sending or Retrying: if the service is down, answers HTTP 429 or HTTP 5xx, or can't be reached, we try again after 30 seconds, 2 minutes, 10 minutes and 30 minutes.
- Failed: we gave up. The reason is shown, e.g. HTTP 404 (wrong address) or HTTP 401 (the token or URL was revoked). Other HTTP 4xx answers are not retried.
The channel list also shows each channel's last result.
Webhooks for developers
Each event is a POST with a JSON body:
{
"event": "instance.created",
"title": "Instance created",
"text": "web-1 · Rao Labs · by Asha Rao\nSize: Pro",
"url": "https://portal.example.com/instances/42",
"occurred_at": "2026-10-22T10:15:00+00:00",
"organization": {"id": 7, "name": "Rao Labs"},
"subject": {"type": "Instance", "id": 42, "name": "web-1"},
"actor": {"name": "Asha Rao", "email": "[email protected]"},
"details": {"size": "Pro"},
"delivery_id": 1234
}
eventis the event key, e.g.instance.created,instance.stop,billing.low_balance,member.joined. A test message has"event": "test".subject,actorandorganizationcan benull, e.g. for system events such as a low balance.- Answer with any
2xxstatus within 10 seconds. Redirects are not followed. - A message can arrive more than once if your server was slow to answer. Use
delivery_id(also in theX-CMP-Deliveryheader) to ignore repeats.
Check the signature. Each request has an X-CMP-Signature header like t=1761128100,v1=5f2a…. v1 is the HMAC-SHA256, in hex, of t, a dot and the raw request body, keyed with the channel's signing secret. To see the secret, open Signing secret under the channel. Reject requests whose signature doesn't match or whose t is more than five minutes old:
[$t, $v1] = sscanf($_SERVER['HTTP_X_CMP_SIGNATURE'], 't=%d,v1=%s');
$body = file_get_contents('php://input');
$valid = hash_equals(hash_hmac('sha256', "{$t}.{$body}", $secret), $v1) && abs(time() - $t) < 300;
If the secret leaks, select Make a new secret under it and update your server. Messages are signed with the new secret from then on.
The address must be https:// and reachable from the internet. Addresses on private networks (e.g. 10.x.x.x, 192.168.x.x, localhost) are refused.
Manage channels with the API
Everything on this page is also available through the API, under /api/v1/organizations/{id}/notification-channels.