Get notifications
Your server can tell you when something happens: new books, a new release in a series you hold, new podcast episodes, a failed scan or backup, a new sign-in, an update. You always see these in the bell in the admin console. You can also send them to your phone with ntfy, to a Discord channel, or to a webhook such as Home Assistant. You need to be an admin.
The bell

Click the bell in the top bar to see the newest events. A dot means there is something you haven't seen. Click an event to go where you can deal with it. See all opens Server > Events, with every event from the last 90 days.

Adding a destination

- Open Server > Settings > Notifications.
- Press Add a destination and choose its kind (below).
- Give it a Name and tick what to Send. The problems are ticked for you.
- Press Add destination.
- Press Send test to check it arrives.
The kinds:
- ntfy - push notifications on your phone. Enter the topic's address, like
https://ntfy.sh/your-topic, and subscribe to the same topic in the ntfy app. Anyone who knows a topic's name can read it, so pick one nobody can guess. If your ntfy server needs a sign-in, add its Access token. - Discord - a message in a channel. In Discord, open the channel's settings, then Integrations > Webhooks > Copy webhook URL, and paste that.
- Webhook - AudioSilo sends a JSON message to an address you give. A local address is fine. Add a Signing secret if the receiver should check the messages are really from your server. The message format is in the developer docs.
The list shows whether each destination's last message arrived, or why it failed. The switch turns a destination off without deleting it. To change one, use Edit in its ... menu.
A message that fails for a passing reason is tried up to three times in all. If the server restarts, it carries on with the messages still waiting, in order for each destination. A destination can get a message twice if the server stops just after sending it.
What to send
The What to send table has a row per event and a column per destination. Tick a box to send that event there. It saves as you tick.
| Event | When it happens |
|---|---|
| New books added | A scan found new books. A podcast library's new episodes come as New podcast episodes instead. |
| A scan failed | A library couldn't be scanned. See Health > Jobs. |
| A library went offline | A library's folder can't be read, such as an unmounted drive. Nothing was removed. |
| Someone signed in | A sign-in from a new device or browser, including a household member signed in on someone else's device. |
| An invite was used | A device was set up from an invite. |
| An update is available | A new AudioSilo version is out. Needs Check for new versions on (General). |
| A backup failed | A backup failed, with the reason. |
| A Bridge job finished | The Bridge finished a job, such as characters and recaps or a read-along. |
| A Bridge job failed or needs attention | A Bridge job stopped with an error, or is waiting for you. |
| New releases in your series | A book came out in a series you hold, and you don't have it. Needs Check for upcoming releases on (Community metadata). |
| New podcast episodes | A followed show's feed brought new episodes. One message per show, with a few titles. See Podcasts. |
| A podcast feed is failing | A followed show's feed failed several checks in a row, is gone, or the Bridge lost its private address. |
| A podcast feed is back | A feed reported as failing answered again. |
| Someone is waiting to sign in | Someone signed in with single sign-on and no account took them. Once per waiting row on People, and again every 90 days while they keep trying. A row you dismissed, or one unseen for 30 days, comes back as a new row with a new message when they next try. The message never carries their email. |
Every event shows in the bell whether you send it anywhere or not. When a server update adds a new event, it starts unticked on the destinations you already have.
Podcasts
The podcast events need a podcast library. The server sends them like this:
- New podcast episodes comes when a show's feed brings episodes the server didn't have. A show's first check sends nothing, and neither does restoring an older backup.
- A podcast feed is failing comes after three failed checks in a row. When the feed couldn't be reached at all, such as no answer in time, it waits for six. Such a failure counts only while the Bridge reaches other feeds, so an outage of the Bridge's own internet sends nothing.
- A feed that reports it is gone, and a private feed whose address the Bridge lost, are reported at once, even if the feed was already reported as failing.
- Only the server's own scheduled checks count toward the three or six, never a follower's Check now. An offline Bridge, or a library the Bridge can't write to, never counts as the feed failing.
- Each problem is reported once. When the feed answers again, you get A podcast feed is back, also once.
Only the followers of a private feed can see its show. So its messages say "a private podcast", with no show name and no episode titles.
What a message carries
Messages carry names, book titles, counts and a link into the console (when the server has a public address). They never carry a password, invite code, token, IP address, a folder path on the server or a podcast feed's address. A failing feed's message says what went wrong, such as the HTTP status the feed answered. A waiting sign-in's message has the person's name, never their email. Messages are in English.