Lidarr Integration: Music Recommendations That Reach Your Files

What connecting Lidarr actually changes

Aurral connects to the Lidarr API and separately reads the files at the paths Lidarr reports. Those are two independent things. The API connection can work while file access fails, and that split is worth internalising because the symptom looks like a broken install rather than a mount problem.

With Lidarr connected, Lidarr adds and monitors artists and downloads albums into its own root folders. Aurral still downloads tracks for playlists, flows and single-track requests into its own Downloads Folder. Aurral never takes an album from Lidarr: it only hands an album over when Lidarr downloads or monitors it.

Mount the same media path in both containers

This is the part that causes the most confusion. Aurral has to be able to read the files at the paths Lidarr reports, which means both containers must mount the same host directory at the same container path. The recommended layout is /data in both, with a Lidarr root folder such as /data/music.

If the paths cannot match — a Windows host with a Linux container is the usual case — add a remote path mapping in settings under Download clients, with Applies to set to Lidarr. The mapping helps Aurral read the files. Note that it does not fix Navidrome playlists on its own, because Navidrome also has to scan the same folder.

Configuration

Enable the integration, set the server URL to an address the Aurral server can reach — in Docker that is usually http://lidarr:8686 rather than localhost — and enter the Lidarr API key. Test the connection before leaving the page.

Then set defaults for new artists: root folder, quality profile, metadata profile, tag, monitoring option and whether to search on add. An optional external URL is used only for links that open Lidarr in your browser, which is genuinely useful when Aurral runs inside a network your browser cannot reach the same way.

Turn Enabled off rather than deleting the connection if you want Aurral to stop sending requests. Indexed Lidarr tracks stay in the library and Aurral stops watching the root folders until you turn it back on.

• Show available music only decides whether the library lists whole Lidarr discographies or only albums with downloaded files. It is on by default.
• Apply recommended settings imports a community guide's quality profiles, custom formats and file naming into Lidarr. This modifies Lidarr settings.
• If Lidarr is configured but unreachable, Aurral shows an error on its actions and does not silently take over.

Custom list feeds: your Flow inside Lidarr

Each Flow can publish a URL that Lidarr reads as a custom list. Open the Flow, open its menu and choose Copy Lidarr import URL. In Lidarr, add a Custom List under Import Lists and paste it.

The feed always matches the Flow's current tracklist. Tracks without a MusicBrainz artist ID are left out, because Lidarr needs that identifier to match anything. Album IDs are included when they are known, and Lidarr versions that support album-level custom lists use them for Specific Album monitoring.

Lidarr has to be able to reach the address in the URL, which is the address from your browser. If Aurral is published on a domain, use that domain rather than an internal hostname.

Request available notifications

To get notified the moment Lidarr imports an album someone requested in Aurral, add a webhook in Lidarr under Settings, Connect. Point the URL at /api/webhooks/lidarr on your Aurral address, turn on the On Import event, and add an X-Api-Key header carrying the API key from Aurral settings.

Other Lidarr webhook events are accepted and ignored. Only the import event updates request history, and only for albums a user actually requested in Aurral.