Free tool

Lidarr custom list builder

Each Flow can publish a URL that Lidarr reads as a custom list. Build the URL shapes here, and get the public-address setting that phone apps need too.

Your Aurral addressFlow ID

URL shapes Lidarr reads as a custom list

Add these in Lidarr under Settings, Import Lists, Custom List.

Custom List (RSS): https://music.example.com/api/feeds/abc123

With format hint: https://music.example.com/api/feeds/abc123.xml

Including album IDs: https://music.example.com/api/feeds/abc123?includeAlbums=true

For reference

# docker-compose.yml
services:
  aurral:
    environment:
      - AURRAL_PUBLIC_URL=https://music.example.com/api/feeds/abc123
    volumes:
      - ./config:/config

Lidarr has to reach that address. If Lidarr runs in a different container or host, the browser address you use here may be unreachable from it. Test it by fetching the URL from inside the Lidarr container before assuming the feed is broken.

Wiring it up in Lidarr

Build the URL above, or copy it straight from the Flow menu with Copy Lidarr import URL.
In Lidarr, open Settings > Import Lists and add a Custom List.
Paste the URL and save.
Run the list. The Flow's current tracks appear as a list in Lidarr.

The easiest route is the Flow menu. In Aurral, open the Flow, open its menu and choose Copy Lidarr import URL, which inserts the address from your browser. This builder is for when you want the variants or the compose snippet.

When the feed is empty

Two causes account for almost all of it. First, reachability: Lidarr has to be able to fetch that URL. If it runs in a different container or host, test the URL from inside the Lidarr container before assuming the feed is broken.

Second, identifiers. The feed leaves out any track without a MusicBrainz artist ID, because Lidarr has nothing to match it against. If a Flow contains several such tracks, that is why.

Why the public address matters beyond Lidarr

Aurral uses its known address to build two things: the URL it hands phone apps during Connect an app, and the URL it copies for a Lidarr custom list. If that address is an internal hostname, both break outside your own network in slightly different ways.

Phone apps receive an address they cannot resolve from outside your LAN, which is why the web UI works but the app does not.
Lidarr may be able to resolve an internal hostname fine, so the feed works locally and fails when Lidarr itself moves.

Setting the public URL to the address you actually use fixes both at once.

Frequently asked questions

What is a Lidarr custom list?

A URL that Lidarr polls as if it were a list of releases. Each Aurral Flow can publish one, so its current tracks show up inside Lidarr as well.

Why does my custom list show nothing?

Either Lidarr cannot reach the address, or the Flow has no tracks with a MusicBrainz artist ID. The feed leaves out tracks without an ID because Lidarr needs it to match anything.

Why do phone apps need the public address?

Aurral builds the connection URL from the address it knows. If that is an internal hostname, your phone outside your network cannot reach it. Setting the public URL fixes both Lidarr and phone apps.

Does the feed include album IDs?

When they are known. Lidarr versions that support album-level custom lists use them for Specific Album monitoring.

Publish Flows where you actually listen

A Flow that stays inside Aurral is a list nobody opens. Publishing it into Navidrome, Plex or Jellyfin is what makes it part of your listening.

How Flows work Lidarr integration