Since Containly 2.7.2 notifications also reach Discord, Telegram, Slack and Pushover, and your phone or browser as web push through the installed app. Free for normal notifications, Pro inside workflows. Setup per service, push on iPhone and Android, filters and security explained.

Containly 2.7.2 adds four channels to the ones from 2.7.1 (ntfy, Gotify, webhook) and web push to your own devices. Both are Free for normal notifications. In workflows the notify step can use them too; like everything in Workflows this needs Pro.

Discord, Telegram, Slack and Pushover

Admins add channels under Settings > Notifications > Channels > Add channel. Every channel has its own minimum severity, an optional event selection and a message language, a Send test button that saves nothing, and a delivery log.

Service	What you need	Where you get it
Discord	Webhook URL	In Discord: Edit channel > Integrations > Webhooks > New webhook > Copy webhook URL
Telegram	Bot token, chat ID, optional topic ID	Create a bot with @BotFather (`/newbot`), add it to your chat, group or channel. Groups and channels have IDs starting with `-100`; public channels can use `@channelname`
Slack	Incoming webhook URL	Create a Slack app, switch on Incoming Webhooks, add a webhook to a channel and copy its URL
Pushover	App token, user key, optional device	On pushover.net: Create an Application (app token); the user key is on your start page (a group key works too)

What the messages look like:

Discord: an embed in the severity colour (blue, amber, red) with the time, the affected object and a link to Containly. Nobody is mentioned.
Telegram: bold title with a severity symbol, the text and an "Open in Containly" link.
Slack: title, text, a context line and an "Open in Containly" button, with a coloured bar.
Pushover: title, text and link. The priority per severity is -2 to 2 (default info -1, warning 0, critical 1). Emergency (2) repeats until you acknowledge it in the Pushover app; it is never a default, and when you pick it you also set how often it repeats and when it stops.

Security

Discord and Slack URLs are only accepted on the official hosts (discord.com/api/webhooks/..., hooks.slack.com/...). Telegram and Pushover messages only go to api.telegram.org and api.pushover.net.
URLs, tokens and keys are stored encrypted and never shown again. The list only shows a masked hint.

Web push to your phone and browser

Every user manages their own devices under Profile > Push notifications.

Open Containly over HTTPS (for example behind a reverse proxy with a certificate). Browsers do not allow push over plain http://.
On iPhone or iPad (iOS 16.4 or later): open Containly in Safari, tap Share > Add to Home Screen, then open Containly from the home screen and sign in. Push only works in this installed app.
On Android, Windows, macOS or Linux: Chrome, Edge, Firefox or Safari work in the browser; installing the app is optional.
Under Profile > Push notifications enter a device name and click Turn on push on this device. Allow notifications when the browser asks.
The device appears under My devices. Send test shows a test message within a few seconds. Clicking a notification opens the matching page in Containly.

Per device you can change the name, the minimum severity and the events (pencil icon), send a test or remove the device. You get the notifications for which you are a recipient under Settings > Notifications, also if you have no e-mail address.

If push cannot be turned on, the page says why: not HTTPS, iPhone not installed to the home screen, browser without push support, or notifications blocked in the browser's site settings.

How push works

Containly needs no extra service or account. It creates its own key pair once (VAPID), encrypts every message for your browser and hands it to your browser's push service (Google, Apple, Mozilla or Microsoft), which only sees encrypted data. When a device is gone (app removed, permission revoked), the push service reports it and Containly deletes the device automatically.

Workflows (Pro)

In the Notify step tick Push to devices to send the alert to the recipients' devices, or pick any saved channel. On Free, workflow messages to channels and push are refused on the server.

Demo

The public demo shows sample Discord, Telegram, Slack and Pushover channels; Send test is simulated and sends nothing. Push is visible but disabled there, because it needs your own instance with HTTPS.