Lidarr
Lidarr integration enables lifecycle actions on music managed by Lidarr.
- Go to Settings → Integrations
- Under the Lidarr section, click Add Instance
- Enter:
- Name: A label for this instance (e.g., “Main Lidarr”)
- URL: Lidarr’s base URL (e.g.,
http://192.168.1.100:8686) - API Key: Found in Lidarr → Settings → General → API Key
- Click Test Connection to verify
- Save
You can add multiple Lidarr instances.
How Matching Works
Section titled “How Matching Works”Librariarr matches music to Lidarr using MusicBrainz IDs:
- During media sync, external IDs are fetched from your media server
- When lifecycle rules need Lidarr data, Librariarr queries Lidarr by MusicBrainz artist ID
- Fallback: artist name matching
Available Operations
Section titled “Available Operations”Once connected, these operations are available via lifecycle rules:
| Operation | Description |
|---|---|
| Delete | Remove the artist/album from Lidarr (optionally delete files) |
| Unmonitor | Stop Lidarr from monitoring for upgrades |
| Tag | Add a custom tag to the artist in Lidarr |
Data from Lidarr
Section titled “Data from Lidarr”The following Lidarr metadata is available for lifecycle rule conditions:
- Quality profile: The assigned quality profile name
- Monitored status: Whether the artist is monitored
- Tags: Current tags on the artist
Security
Section titled “Security”- API keys are stored securely and never sent to the frontend
- Connection testing uses server-side endpoints
- All integration responses are sanitized
Limitations
Section titled “Limitations”- MusicBrainz ID availability depends on your media server’s metadata agent
- Lifecycle actions require Lidarr to be reachable at execution time
- Music matching can be less reliable than movie/series matching due to artist name variations