Notifications and alerts
Get told when a post fails, a post needs approval or an account must be reconnected: by email, push or in Slack, Discord and Teams.
What you can be alerted about
| Event | Who gets it | Sent when |
|---|---|---|
| post.failed | The post author, and everyone who manages the workspace | A post failed on at least one account (after retries). |
| approval.requested | People who can approve content (not the author) | A post was sent for approval. |
| account.needs_reconnect | People who manage the workspace | A connection expired or was revoked and must be reconnected. |
| Daily or weekly summary | You, if you turn it on | Published, failed and scheduled counts at 8:00 IST (Mondays for weekly). Nothing is sent when there is nothing to report. |
These events are emitted from the same place as outgoing webhooks, which also receive account.needs_reconnect.
Your preferences
Open Settings > Notifications. For each workspace choose the events you want and whether they arrive by email, by push or both, plus the optional summary. Your choices only affect you.
The approval request email you already receive follows the same switch: turn By email or the event off to stop it.
Push notifications
Press Turn on under "Push notifications on this device" and allow notifications in the browser. Each browser or device is subscribed separately; remove one from the list at any time. Tapping a notification opens the post or page it is about.
- Works in Chrome, Edge and Firefox, and in Safari on iOS 16.4+ after the app is added to the Home Screen.
- Push must be configured by whoever runs the server (VAPID keys). If it is not, the section says so and the other channels keep working.
- Use Send test to check a device.
Slack, Discord and Microsoft Teams
Workspace owners and admins can send alerts to a team channel. Create an incoming webhook in the chat service, paste its URL under Settings > Notifications > Slack, Discord and Microsoft Teams, choose the events and press Send test message.
| Service | URL looks like |
|---|---|
| Slack | https://hooks.slack.com/services/… |
| Discord | https://discord.com/api/webhooks/… |
| Microsoft Teams | A Workflows (Power Automate) webhook URL, or a legacy …webhook.office.com/webhookb2/… connector URL |
- Only https URLs on those services' own hosts are accepted. Anything else, including private or internal addresses, is refused.
- The URL is a secret: it is stored encrypted and is never shown again after you save it.
- Microsoft is retiring the older Office 365 connectors in favour of Workflows; use a Workflows webhook for new Teams channels.
How spam is prevented
- The same post or account triggers at most one alert per window (6 hours for failures, 24 hours for reconnects).
- A burst of failures is merged into one message such as "4 posts failed".
- No one receives more than 10 alerts per hour on one channel; the rest are dropped.
- Failed attempts that will be retried do not alert: only the final failure does.
For people who run the server
Email uses the existing SMTP settings. For push generate keys once with npm run vapid and set VAPID_PUBLIC_KEY, VAPID_PRIVATE_KEY and VAPID_SUBJECT (a mailto: address). Without them push is off and nothing else changes.