[FEATURE] Push Pulsarr’s watchlists items into Overseerr

[jenniekims]

Feature Description

Add a new “Overseerr” export in Pulsarr so that whenever Pulsarr picks up an item from my Plex watchlist or any of my friends’ watchlists it automatically sends that item into an existing Overseerr instance as a request.

Use Case

I (like many others) already have a larger media pipeline wired together: notifications, approvals, post-processing, etc. It’s not that I prefer Overseerr, it’s just the glue that holds everything else in my flow. Right now Pulsarr does a fantastic job watching Plex, but I still have to manually re-enter each show or movie into Overseerr to kick off the downstream steps. Automating that hand-off would save me (and others I hope) hours!

Proposed Solution

1. Overseerr Export Settings
   In Pulsarr’s settings, add an “Overseerr” section where you enter the Overseerr base URL and API key.
2. Real-time or Batched Push
   On each new watchlist item (mine or friends) POST a request to Overseerr’s API, including metadata IDs, media type, and mapped quality profile.
   Optionally offer a batch-mode that pushes every X minutes rather than per item.
3. Deduplication
   Before sending, check if the request already exists in Overseerr and skip duplicates.
4. Logs & Feedback
   Surface success/failure messages in Pulsarr’s UI or logs so admins can verify what was forwarded and troubleshoot any issues.

Alternatives Considered

Manual Entry: Tedious and error prone, requiring retyping dozens of series.
Standalone Script: A separate bridge script works but sits outside Pulsarr’s UI and can be fragile to maintain.

Additional Context

This would be an optional feature, Pulsarr’s core watchlist → Sonarr/Radarr functionality remains untouched. It simply streamlines the hand-off into my existing Overseerr based workflow, keeping the whole ecosystem moving without extra clicks.

Thank you so much for all your dedication and hard work, Pulsarr is amazing ♡

[jamcalli]

Hi @jenniekims

Thanks for submitting this feature request.

I would just like to ask some clarifying questions before I start to mull it over.

At which point in the content lifecycle would this need to be sent?

You said that the arrs functionality with Pulsarr remains unchanged.

Do you need just the request being user agnostic? This happens Immediately upon receiving the new item.

Do you need Which user made the request? This happens at a different step in Pulsarr's workflow, approximately 1 minute after the initial request is submitted.

Do you need the Content Available Status? This happens the second the content is imported within the arrs via Pulsarr's auto configured webhooks inside the arrs.

Cheers

[jenniekims]

Hey hey <3

I think Pulsarr would just need to fire immediately when it picks up a new watchlist item (right at the “new item” webhook). No need to wait for import or availability, just that initial event.

For user mapping, Overseerr always registers requests under the API key owner, there’s no field in the POST to send a Plex ID.
Pulsarr can grab the Plex user’s ID from the watchlist event, and on your end you can do a separate lookup to fetch the internal user ID and map the request back to the correct person (if you'd like, totally optional, just QOL).

For content availability status, I don't think it's needed. I think only forwarding initial request would be optimal in this case. Overseerr and Plex have their own "Content is now Available" notifications if users have them enabled.

These are just my thoughts, but you probably know better since you’ve built such an amazing app with great integrations already. 😺

[jamcalli]

Simple enough.

Pulsarr already has it's own method of mapping all watchlist items back to the correct Plex users using a GraphQL call and the admins token.

I'll add it to the docket.

[jamcalli]

Just hashing this out.

Pulsarr automatically routes to multiple instances, or can target specific instances via it's content router.

Would you require the requests to target each instance inside overseerr?

Do you need the requests to mimic the content router's decisions?

Aka, if an Item was sent to 3 instances (4k, Default, and Anime) would you require 3 separate Overseerr requests, targeting each set of specific settings?

[jamcalli]

Another question, perhaps you could enlighten me.

In what ways does Overseerr facilitate your workflow in a way that Pulsarr does not?

[jenniekims]

Actually, with the recent updates and the constant pace of improvements, Pulsarr could probably cover everything Overseerr does and more at this rate. The integration request is starting to feel increasingly redundant. Perhaps the next focus could be on request limits, specifically limiting the number of new watchlist items per user per month distributed to Sonarr/Radarr. Keep up the impressive work and thank you for considering my initial suggestion <3

[jamcalli]

I've been avoiding requests entirely, as I am trying to facilitate a blanket approach.

You can disable specific users, and set up specific content router rules to mitigate large bulk downloads.

For example:

Router Rule 1: IF Season > 2 -> rolling pilot to Sonarr4k
Router Rule 2: IF Season > 2 -> rolling pilot to SonarrHD
Router Rule 3: IF Season > 2 -> rolling pilot to SonarrREMUX

Large shows would then be grabbed, but only the pilot, which would then auto expand and contract as users progress.

Perhaps you could make a more targeted argument as to why approvals is still a needed feature?

[jamcalli]

I will be implementing approvals.

There is too much interest in this feature.

I do need to hash out a flow though and would appreciate your input.

Also, if anyone else reads this and is interested, please join the discussion!