Connect Cleanuparr¶
See Cleanuparr's strikes, removals, cleaned downloads, and download client and arr health on the Downloads page, and stop duplicate stuck-download alerts for items Cleanuparr is already handling.
Beta feature
Available on the 1.4.2-beta line.
Before you begin¶
- Finish Cleanuparr's own setup and confirm its UI loads.
- Sign in to JellyGlance with permission to manage integrations.
- Copy the Cleanuparr API key.
Choose the connection URL¶
Configure JellyGlance¶
- Open Settings → Integrations → 3rd Party Apps. Enable Cleanuparr.
- Enter the base URL.
- Paste the API key. It is sent as
X-Api-Key. - Run the connection test. It reads Cleanuparr's stats API at
/api/v2/stats. - Save the integration.
Send Cleanuparr notifications to JellyGlance¶
The Cleanuparr card shows a Notifications from Cleanuparr panel with a receiver URL and token.
- In Cleanuparr, add a Gotify notification provider.
- Paste the receiver URL and token from the JellyGlance card.
- Enable Failed Import, Stalled, Slow, Errored Strike, Queue Item Deleted, Download Cleaned and Download Stopped.
| Cleanuparr event | In JellyGlance |
|---|---|
| Failed import, errored download, repeated stalls | Raised as alerts, because they need a look |
| Everything else | Shown on the Downloads page |
| Downloads Cleanuparr is handling | Tagged, and skipped by stuck-download alerts |
Treat the token as a secret
Anyone with the token can post events to the receiver. Rotate it from the card if it leaks, then update Cleanuparr.
Verify it works¶
Open Downloads. The Cleanuparr panel should show strike and cleanup counts matching Cleanuparr. Cleanuparr can also be used as a trigger for outbound webhook rules.
Common connection problems¶
| Symptom | Next check |
|---|---|
401 or 403 |
API key from Cleanuparr settings. |
404 on test |
BASE_PATH is missing from the URL. |
| No alerts arrive | Gotify provider URL and token, and that the listed events are enabled. |