Notifications

Cloud tells you about two kinds of thing. Notices about your account and your organizations' bills are always emailed to your account's address. Updates about deployments, domains and backups go wherever you choose, through channels you add. Both are under Settings, then Notifications, and both are yours rather than an organization's: they cover every organization you own.

The Automatic account emails card shows the address they go to, which is the email address of the Cahaves account you sign in with. "Billing and account safety notices are always sent by Cahaves Cloud.": they cannot be turned off, redirected or sent to a channel.

An email about an organization's bill links to that organization's billing, and opening the link moves the console to it; the archived, expiring and deleted emails link to the Archived tab of its Storage instead, where the final backups are; the suspension email links to Support and the reactivation email to the Dashboard. Billing explains each one, and Archived for billing the four about an archive. Paddle sends its own receipt for a card charge, and an invoice comes from Cahaves' invoicing service. These deliveries appear in Delivery history under the channel "Account email", marked Automatic.

A channel is one destination with the events it should receive. Add as many as you need, for example failures to a chat room and every deployment to a webhook.

A channel is yours, so it receives its events from every organization you own. A message names the service, the domain or the backup, not the organization, and its link opens in the organization the event belongs to, moving the console to it first.

Every webhook address, for a webhook, Slack or Discord channel, must be HTTPS on port 443, with no user name, password or #fragment in it. At delivery Cloud also checks that the host resolves only to public internet addresses, and it does not follow redirects.

1. Open the dialog

   Under Service notifications, press Add channel.

2. Describe the channel

   Choose a Channel type, give it a Name (up to 80 characters), leave Delivery on Enabled, and tick the Events it should receive. Deployment failed is ticked for you; at least one event is needed.

3. Connect it

   Fill in the fields for its type from the table above, then press Save channel.

Connection details are stored encrypted and never displayed again, in the console or anywhere else. The channel's card shows its name, Enabled or Paused, its type and its events.

Send test on a channel's card sends one real notification down the same path every event takes, under the event name test, with the subject "Cahaves Cloud test notification" and the message "This is a test notification from Cahaves Cloud. If it reached you, this channel is configured correctly." It is signed, retried and listed in Delivery history as "Test notification", so a test that arrives proves the channel works end to end.

The button is disabled on a paused channel ("Turn this channel on to send a test."), and a channel takes one test at a time: a second is refused with "A test to this channel is still being sent. Wait for it to finish." until the first is answered.

• Edit channel changes the name, the delivery setting and the events. The type cannot change. Connection details stays on Keep saved configuration unless you choose Replace configuration and enter new ones.

• Setting Delivery to Paused stops the channel receiving anything. Events that happen while it is paused are not sent later.

• Archive removes the channel after "Archive this channel?" and Archive channel. It stops receiving updates, its connection details are erased, and its delivery history is kept.

Delivery history lists every notification, newest first, 25 to a page with Previous and Next: its Event, Channel, Time (in UTC) and Status, with a sentence under the status when something went wrong. While a delivery is queued or sending, the page refreshes itself every 15 seconds.

Cloud makes up to five attempts, 2, 4, 8 and 16 minutes apart, and only when the answer says to try again: a 429 or 5xx status, or a destination whose name did not resolve. Any other refusal fails at once. A request that timed out or lost its connection may have arrived, so it becomes Outcome unknown straight away rather than risk sending the same message twice.

Email carries the subject, the message, the service or domain it concerns and when it happened, with a link to the page in the console. Slack, Discord and Telegram receive three lines of plain text: "Cahaves Cloud", the message, and the link. Discord posts under the name Cahaves Cloud with mentions turned off, and Slack and Telegram show no link previews.

A webhook channel receives a POST with a JSON body (Content-Type: application/json) for each event:

{
  "source": "cahaves_cloud",
  "event": "deployment.succeeded",
  "occurred_at": "2026-09-23T08:30:00Z",
  "resource": { "type": "Deployment", "id": "9d2c7e1b-4a6f-4b3e-8e0d-5f1a2c3b4d6e", "label": "web" },
  "subject": "Deployment succeeded for web",
  "message": "Cahaves Cloud deployed web successfully.",
  "url": "https://cloud.cahaves.com/projects/shop/services/0b9e4d2a-7c13-4f6e-a8d5-3e1c9b7f2a40/deployments/9d2c7e1b-4a6f-4b3e-8e0d-5f1a2c3b4d6e",
  "id": "e1f2a3b4-c5d6-4e7f-8a9b-0c1d2e3f4a5b"
}

Two headers come with it:

Answer with any 2xx status as soon as you have the request. Cloud waits at most ten seconds for the answer, reads no more than 32 KB of it, and treats a slower answer as Outcome unknown. A 3xx is not followed and counts as a refusal.

The console asks for a signing secret when you add a webhook channel. Check the signature against the exact bytes you received, before parsing them:

import { createHmac, timingSafeEqual } from "node:crypto";

export function isFromCloud(rawBody, header, secret) {
  const expected = "sha256=" + createHmac("sha256", secret).update(rawBody).digest("hex");
  const given = Buffer.from(header ?? "");
  const wanted = Buffer.from(expected);
  return given.length === wanted.length && timingSafeEqual(given, wanted);
}

A test delivery has the same shape, with event set to test, so Send test is the way to check your receiver.