Alerts and shows
Notifications: Gotify and Webhooks for Flow Events
Notifications cover the events you would otherwise have to be looking at the screen for: a flow finished and needs nothing, or an album you requested is now available.
What can notify you
Events include flow and playlist job completion, newly available requested albums, discovery rebuilds and new releases worth knowing about. Each has its own switch, so you can be told about the things you care about and not the rest.
Aurral also accepts Lidarr webhooks, which is how an album becomes available faster than polling would notice.
- Flow and playlist job completion
- Requested albums becoming available
- Discovery rebuild results
- New releases for library artists
Gotify
Gotify is a lightweight self-hosted push server. Point Aurral at your Gotify URL and an application token, and events arrive as notifications on your phone.
Because Gotify is self-hosted, this path keeps your listening activity notifications on infrastructure you control, consistent with the rest of a self-hosted music stack.
Generic webhooks
The webhook option posts the same event payloads to any URL you choose. That is the flexible path if you already run something that accepts webhooks, or if you want to write your own automation against a flow completing.
Add an X-Api-Key header where Aurral needs to authenticate, and remember that the receiving end has to accept requests from wherever Aurral is, which behind a reverse proxy may not be your LAN.
Wiring Lidarr in
For requested albums, add a webhook in Lidarr pointing at /api/webhooks/lidarr on your Aurral address, enable the On Import event, and add an X-Api-Key header carrying the API key from settings.
Other Lidarr events are accepted and ignored. Only the import event updates request history, and only for albums a user actually requested in Aurral.
Frequently asked questions
Do I need Gotify?
No. Gotify and generic webhooks are both optional, and Aurral works fully without either.
Can I be notified only about flows and not downloads?
Yes. Each event type has its own switch, so you enable the ones you want.
Why do requested albums show as available before I notice?
Likely the Lidarr webhook is configured, so Aurral is told at import time rather than waiting for its own check.
Other alerts and shows integrations
Everything else
All integrations
Library
The music manager decides what ends up on disk. Aurral never writes into someone else's library folder.
Downloads
Where the audio actually comes from. Source order decides which client gets asked first.
Playback
Playback stays where it is. Aurral publishes playlists into the server you already run.
Listening history
History is the strongest recommendation signal you already own. Wire it in and the picks improve.
Alerts and shows
Optional signals that turn a static library into something that keeps moving.
Connect Notifications to the rest of your stack
Nothing here requires restarting anything else. Add it when it becomes the piece you were missing.