Skip to content

Notification channels

Email, in-app and push per category, plus Discord and webhook destinations.

You choose what you are notified about and where, independently. It all lives in Mail → Where they go.

Verification and security emails are always sent and cannot be turned off.

The categories

CategoryFires when
Client went offlineA client disconnected, was kicked, or was banned.
Client could not startA start was refused (no free slot, for example), or one kept failing to connect.
Messages from your flowsYour own flows send something with the notify action.
Flow errorsA flow fails repeatedly, or a trigger has stopped matching.
Dedicated IP stopped workingA dedicated IP stopped responding, so the clients using it cannot connect.
BillingA trial ending, a payment that failed, a scheduled plan change taking effect.
AnnouncementsOccasional product news.
ReceiptsPayment confirmations and invoices.
Flow requestsOffers, deliveries, deadlines and refunds for requests you post or work on.

The grid

Each category has three switches:

Email: to your account address. Announcements by email are always on: service news about outages, migrations and price changes goes to everyone.

In-app: the Mail and the bell.

Push: browser push, or the phone's own notifications in the app, enabled per device. Enable on this device adds the one you are using, and the section says how many other devices have push on. Your browser will ask for permission, and if you refuse, push cannot be turned on until you allow it in the browser. While no device has push on, the Push column does nothing.

Discord and webhook destinations

Under Webhooks, Add destination sends alerts somewhere outside CubeMind:

  • Discord: paste a Discord webhook URL. Optionally add a role id to ping that role, or a thread id to post into a thread.
  • Webhook: your own HTTPS endpoint, for wiring alerts into something else.

Give each destination a name and pick the categories it receives under Send these here. You can add several, so a busy alerts channel and a quiet archive can live side by side. A destination with no categories picked receives nothing.

Only https URLs are accepted. A saved URL is hidden afterwards: when you edit the destination the field reads Leave blank to keep the saved URL. It is not shown back for security.

Send test

Because a saved URL is hidden, Send test is how you confirm a destination works. It sends one notification there and reports the failure detail if the endpoint rejects it. The grid has a Send test for in-app Mail too, and push has one per device.

Do this when you first set up Discord: a wrong or expired webhook URL fails silently otherwise, and you would only find out when a real alert went missing.

A sensible starting point

  • Client went offline and Client could not start → Discord or push. These are the ones you want to know about promptly.
  • Billing → email and in-app.
  • Receipts → email.
  • Announcements → in-app.
Notification channels · CubeMind docs