Playlists overview

The Playlists page contains flows and imported playlists. Both types use the Aurral folder under aurral-weekly-flow.

Aurral does not write these files to your main music library.

Flows compared with static playlists

	Flows	Static playlists
Tracklist	Regenerates on a schedule	Fixed from import or export
Downloads	Can generate replacement picks	Keeps the exact imported tracks
Controls	Schedule, source mix, focus, deep dive	None of the flow controls
Worker	Shared download worker	Shared download worker

Flows refresh on a schedule and use your flow settings. Static playlists come from Spotify, JSON files, or exported flow tracklists.

If all download sources fail, the track stays in the failed state after an Aurral restart.

Select Re-search missing from the playlist menu to try the track again.

Import and Lidarr sync

Use Import playlist for Spotify (connect in-app) or a JSON tracklist. See Playlist imports.

Flows can expose a Lidarr import URL so Lidarr polls the current flow tracklist as a custom import list. See Lidarr: Import list feeds.

Where files go

Generated playlists go under your Downloads Folder path. Set this path in Settings > Download Clients. Usually, the path is:

/data/downloads/aurral/aurral-weekly-flow/<playlist-id>/

Navidrome can scan that tree and play .m3u playlists. Plex can index the track folders and create playlists for Plexamp.

See Navidrome and Plex for playback setup.

See yt-dlp, slskd, and Usenet for download setup.

See Match Lidarr for storage setup.

Next steps

• Flows: schedule, source mix, focus, and generation behavior
• Playlist imports: Spotify connect, JSON formats, retries, and file reuse