Lidarr

Lidarr integration enables lifecycle actions on music managed by Lidarr.

Setup

1. Go to Settings → Integrations
2. Under the Lidarr section, click Add Instance
3. Enter:
   • Name: A label for this instance (e.g., “Main Lidarr”)
   • URL: Lidarr’s base URL (e.g., http://192.168.1.100:8686) — the address Librariarr uses to reach Lidarr
   • External URL (optional): The address your browser uses for Lidarr, starting with http:// or https://. Used for “open in Lidarr” links; falls back to URL when empty
   • API Key: Found in Lidarr → Settings → General → API Key
4. Click Test to verify — Save stays disabled until the test passes
5. Save

You can add multiple Lidarr instances. A rule set reads its Lidarr criteria from the instance its action is linked to (see lifecycle rules).

Deleting an instance cancels the pending lifecycle actions bound to it and detaches it from every rule set that used it; those rule sets’ actions are turned off until you pick another instance.

How Matching Works

Librariarr matches music to Lidarr using MusicBrainz IDs:

1. During media sync, Librariarr stores each track’s artist MusicBrainz ID — on Plex from the artist’s own metadata, on Jellyfin and Emby from the track’s album artist (or artist) ID
2. When lifecycle rules need Lidarr data, Librariarr looks the artist up in Lidarr by that ID. An artist MusicBrainz has merged into another is still found under its old ID
3. A track without an artist MusicBrainz ID cannot be matched to Lidarr

Existing libraries pick the artist IDs up on their next full sync.

Available Operations

Once connected, these operations are available via lifecycle rules:

Operation	Description
Delete from Lidarr	Remove the artist from Lidarr and delete its files from disk
Unmonitor & Delete Files	Unmonitor the artist and delete the matched tracks’ files
Monitor & Delete Files	Make sure the artist is monitored, then delete the matched tracks’ files so Lidarr grabs a new copy
Delete Files Only	Delete the matched tracks’ files without changing monitoring
Unmonitor Only	Stop Lidarr from monitoring the artist
Change Quality Profile	Move the artist to another quality profile (skipped if it is already on it)
Search for New Copy	Trigger a Lidarr search, changing nothing else
Do Nothing	Only track the match (and apply tag changes, if configured)

The file deletes act only on the matched tracks — see which files a file delete removes. Every action except Delete from Lidarr (which removes the record and its tags) can also add and remove Lidarr tags, applied before the main action. Delete from Lidarr can also add an import list exclusion so import lists don’t add it back, and the file-delete and quality-profile actions can search after the change. When a destructive action is linked to an instance with no recycle bin configured, the rule editor warns you before saving. See Available Actions.

Data from Lidarr

The following Lidarr metadata is available for lifecycle rule conditions:

• Found in Arr, Monitored, Tag, Quality Profile, Status
• Rating (Lidarr’s artist rating), Size on Disk, Path, Date Added

Security

• API keys are stored securely and never sent to the frontend
• Connection testing uses server-side endpoints
• All integration responses are sanitized

Limitations

• MusicBrainz ID availability depends on your media server’s metadata agent
• Lifecycle actions call Lidarr’s API in real time. Requests time out after 15 seconds; reads are retried up to 3 times, writes are not. If Lidarr is unreachable during a scheduled run, its remaining actions stay pending for the next run; a manual Execute fails them
• Music matching can be less reliable than movie/series matching due to artist name variations