Lidarr Webhook Notifications

Configure push notifications for Lidarr events using webhooks (beta feature).

Overview

Webhook notifications provide real-time push notifications when events occur in Lidarr. This feature requires beta access.

Prerequisites

• OmniFetch app with Lidarr configured
• Private beta key from support
• iOS push notifications enabled

Setup Process

Step 1: Enable Beta Access

1. Open OmniFetch
2. Go to Settings → Notification Settings → Push Notifications
3. Enter your Private Beta Key in the designated field
4. Tap Save - look for green confirmation
5. Beta features are now activated
6. Enable the button to on

Step 2: Automatic Webhook Configuration

Once beta access is enabled:

1. Add or Update Lidarr:
2. If adding new: Complete normal setup process

3. If existing: Edit and re-save the service

4. Automatic Process:

5. OmniFetch registers your device for push notifications
6. Creates webhook connection in Lidarr
7. Configures all supported events
8. No manual configuration needed

Step 3: Verify Webhook Creation

1. Open Lidarr web interface
2. Navigate to Settings → Connect → Connections
3. Look for "OmniFetch" connection
4. Verify it shows as enabled

Step 4: Test Notifications

1. In Lidarr connections, find OmniFetch
2. Click Test button
3. You should receive a push notification
4. If successful, setup is complete

Supported Events

Core Events

Download/Import Completed

• Event: Album successfully downloaded and imported
• Includes: Quality upgrades
• Notification: "Artist Name - Album Name downloaded successfully"

Media Grabbed

• Event: Album grabbed from indexer
• Notification: "Artist Name - Album Name grabbed from IndexerName"

Test Notification

• Event: Manual test from Lidarr
• Notification: "Test notification from Lidarr"

File Management Events

Files Renamed

• Event: Music files renamed/organised
• Notification: "Artist Name - Album Name files renamed"

Track File Deleted

• Event: Music file deleted from disk
• Notification: "Artist Name - Track Name deleted"

Library Events

Artist Deleted

• Event: Artist removed from Lidarr
• Notification: "Artist Name removed from library"

Album Deleted

• Event: Album removed from Lidarr
• Notification: "Artist Name - Album Name removed from library"

System Events

Health Issues

• Event: Lidarr detects system problems
• Priority: High
• Examples:
• "Unable to connect to download client"
• "Indexer unavailable"
• "Root folder missing"

Application Updates

• Event: Lidarr update available
• Notification: "Lidarr update available: v1.0.9"

Notification Management

Configure Event Types

1. In OmniFetch, go to Lidarr settings
2. Tap Notification Settings
3. Toggle individual events on/off
4. Save preferences

Recommended Settings

Essential Notifications:

• ✅ Download/Import Completed
• ✅ Health Issues
• ✅ Download Failed

Optional Notifications:

• ⚪ Media Grabbed
• ⚪ Files Renamed
• ⚪ Quality Upgraded

Avoid Overload:

• ❌ Test notifications (after initial test)
• ❌ Verbose file operations

Notification Sounds

Configure custom sounds:

1. iOS Settings → Notifications → OmniFetch
2. Choose notification sound
3. Or set per-service sounds in app

Troubleshooting

No Webhook in Lidarr

Issue: OmniFetch connection not appearing in Lidarr

Solutions:

1. Verify beta key is saved
2. Edit and re-save Lidarr in OmniFetch
3. Check Lidarr API permissions
4. Restart Lidarr service

Test Fails

Issue: Test notification doesn't arrive

Check:

• iOS notification permissions
• Beta key validity
• Internet connectivity
• Lidarr can reach webhook server

Duplicate Notifications

Issue: Receiving multiple notifications for same event

Fix:

1. Remove any manual webhook configurations
2. Ensure only one OmniFetch connection exists
3. Disable Lidarr's built-in notifications

403 Forbidden Error

Issue: Webhook returns authentication error

Solutions:

• Re-enter beta key in OmniFetch
• Generate new webhook (if using manual setup)
• Contact support for key verification

Advanced Configuration

Performance Optimization

Best Practices:

• Limit notifications to essential events
• Use quiet hours for overnight periods
• Group notifications when possible
• Monitor webhook response times

Debug Information

For troubleshooting:

1. Go to Settings → Developer
2. Enable Debug Logging
3. Check webhook status and errors
4. Share logs with support if needed

Beta Limitations

Current beta limitations:

• Webhook URL changes require reconfiguration
• Some events may have delays
• Rate limiting during high activity
• Beta key required for all features

FAQ

Q: Do I need to configure anything in Lidarr? A: No, OmniFetch handles everything automatically once beta key is entered.

Q: Can I customise the webhook URL? A: No, the webhook URL is managed by OmniFetch.

Q: Will webhooks work without beta key? A: No, webhook notifications require beta access.

Q: How do I disable webhooks? A: Remove beta key or disable notifications in settings.