Clarnix help · Channels
Set up channels for your Clarnix briefings
Channels is where you choose how your briefing reaches you (email, chat, your phone or your own systems) and where you fix one that has stopped working.
The channels you can use
Starter includes email and push notifications. Pro, Team and Team Pro add Telegram, Slack, Microsoft Teams, Google Chat, webhooks and Hook.Notifier. WhatsApp is available on any plan, including Starter, as a separate paid add-on. During the free trial you have the channels of the plan you chose for it. Until you choose a plan, your account has Starter’s channels: email and push.
| Channel | How you set it up |
|---|---|
| On by default. Briefings come from digest@clarnix.app. | |
| Dashboard | Built in: read your briefings in Clarnix itself. |
| Telegram | Clarnix shows a short code. Open our bot at t.me/ClarnixBot and send it the code. The code expires after 10 minutes. |
| Needs the paid add-on, then verify your phone number. See below. | |
| Slack | Add to Slack, choose your workspace, and the bot sends you a direct message. |
| Microsoft Teams | Add Clarnix from the Microsoft Teams Store. It usually connects your account automatically. If it does not, paste the one-time code shown on this page into the Clarnix chat in Teams. |
| Google Chat | A Workspace administrator authorises Clarnix once; after that it is a single click. |
| Webhook | Paste an https:// address and Clarnix posts each briefing to it as signed JSON. |
| Hook.Notifier | Paste your Hook.Notifier address to get briefings as phone notifications without installing anything. |
| Browser push | Grant permission in your browser. One channel per device. See below. |
What the status on each card means
| Status | Meaning |
|---|---|
| Connected | Delivering normally. |
| Paused | You switched it off. Nothing is broken. |
| Unverified | Set up, but no test or delivery has succeeded yet. |
| Disconnected | Something failed: the credential is dead, or the last delivery or test did not go through. |
Only Disconnected is asking you to do something. Reconnect is on every card: for Slack it re-runs the install, for push it re-subscribes this device, and for everything else it revalidates the settings and immediately re-tests. Your schedule and settings survive a reconnect.
WhatsApp delivery is a paid add-on on every plan, enabled from Settings → Billing → Add-ons. Once it is on, WhatsApp appears here and you verify your phone number.
| Plan | Add-on per month | Add-on per year |
|---|---|---|
| Starter | €6 | €72 |
| Pro | €18.50 | €222 |
| Team, per member | €18.50 | €222 |
Unlike the plans themselves, the yearly add-on price is simply twelve times the monthly one. Paying for a year up front does not reduce it, because it is a cost passed straight through. On a team, each member who wants WhatsApp needs the add-on assigned to their seat.
Push notifications, and phones
There is no Clarnix phone app. Push notifications go to your browser, or to Clarnix installed to your home screen as a web app.
- Push is per device, not per account. Enabling it on your laptop does not enable it on your phone. Open Clarnix there and turn it on too. Each device appears as its own entry.
- On iPhone and iPad, Apple only delivers push to a web app added to the Home Screen. Any iOS browser can add it — Share, then Add to Home Screen. That is Apple’s rule, not ours.
- A new phone, a cleared browser or a reinstalled web app counts as a new device. Reconnect on that device re-subscribes it; the old entry can be deleted.
- If you would rather not depend on a browser, Hook.Notifier gives you the same thing as a phone notification.
When a push notification does not appear
Test on a push card reports Sent, and that word is narrower than it looks. It means the push service your browser uses accepted the message for delivery. It is not proof that anything appeared on your screen. Those services answer the same way for a device that will show a notification and for one that will not, so a run of successful sends is not evidence that you saw any of them.
When a notification really is missing, the cause is almost always that the computer decided not to show it. Work through the following in order.
- Turn off Do Not Disturb. On a Mac that means Do Not Disturb or any other Focus, which you switch off in Control Centre. macOS can also turn one on by itself: there is a setting that silences notifications while you are sharing or mirroring your screen, so notifications can disappear during a call and behave normally afterwards. On Windows, look for Do not disturb, which older versions call focus assist.
- Check that your browser is allowed to notify you at all. On a Mac, open System Settings, then Notifications, and find your browser in the list. On Windows, open Settings, then System, then Notifications, and find it there.
- On a Mac, look at the alert style for your browser on that same screen. If it is set to None, macOS accepts every notification and files it in Notification Centre without ever putting anything on the screen. Nothing is broken and nothing is visible, which makes this both the most confusing cause and a common one. Set it to Banners or Alerts.
- Check the browser’s own permission for clarnix.app. Most browsers show it when you click the padlock or the icon at the left of the address bar. If Clarnix is blocked there, no other setting will help.
- Make sure you are testing on the device you set up. A push channel belongs to one browser on one machine. Chrome on your work laptop and Firefox at home are two separate channels with two separate entries, and switching it on in one does nothing for the other.
- On iPhone and iPad, add Clarnix to the Home Screen first. Apple only delivers push to a web app that has been added to the Home Screen, so in an ordinary browser tab there is nothing to switch on.
- If everything above is right and still nothing arrives, press Reconnect on that card, then press Test again.
On macOS, browsers hand their notifications to macOS to draw, which is why the macOS settings are the ones that decide what you actually see. Some versions of Chrome carry their own switch for this, under Notifications in Chrome’s settings; if yours has one, it should be on. The wording and the position of all of these settings move between operating system versions, so search your settings app for notifications rather than following a path that no longer exists.
Reconnect on a push card does something different from Reconnect on every other channel. It discards the subscription this browser is holding, asks the browser for a fresh one, and attaches that to the channel. It is the only repair that helps when the browser has quietly replaced or dropped its subscription, which it does on its own, without telling anyone, and which leaves the card looking perfectly healthy. Your schedule and your settings survive it. The browser may ask for permission again: choose Allow.
Reconnect tells you that notifications are set up again on this device, not that one has arrived. Send a test afterwards and watch for it. If you would rather not depend on a browser at all, Hook.Notifier delivers the same briefing as a notification on your phone.
Webhooks
Clarnix will POST each briefing to an address you control, as JSON, signed so you can verify it came from us. The request carries an X-Clarnix-Event header and an X-Clarnix-Signature header, and the body contains the briefing id, headline, sections, statistics and generation time. The test button sends the same shape.
- The address must be https. Plain http is refused.
- Private, loopback and internal network addresses are refused.
- The signing secret is shown once, when the channel is created. Copy it then. It is not shown again and reconnecting does not change it. If you lose it, create a new channel.