Integration Modes

Delivery is what happens after a discovered title passes a job’s rules. Choose Direct to add movies to Radarr or shows to Sonarr, or Jellyseerr / Seerr to create requests through your request server.

Your discovery source is independent of this choice. A TMDB job can deliver directly or create requests; you do not need Trakt to use either mode.

Mode	Movies go to	Shows go to	What a successful run records
Direct	Radarr	Sonarr	Added
Jellyseerr / Seerr	Request server	Request server	Requested

An addition or request is not proof that a download finished. Your media services handle availability, searching, downloading, and importing.

Set up direct movie delivery

1. Open Settings → Connections → Radarr.
2. Enter the Server URL that Blockbusterr can reach and Radarr’s API key. In a shared Docker network, the URL might be http://radarr:7878; localhost inside a container refers to that container.
3. Select Test connection, then choose the quality profile and root folder from your Radarr setup. The root folder is a path Radarr understands, such as /movies.
4. Review minimum availability and monitoring. These are Radarr delivery settings, not discovery filters.
5. Save your settings. Under Settings → Automation, select the direct delivery mode and save.
6. Open a movie job, preview its matches, and confirm its mode uses the global default or Direct (Radarr/Sonarr).
7. Use Run Now when ready to add the previewed kind of content. Check both Activity → Job Runs and Radarr afterward.

For TV, follow the same process with Settings → Connections → Sonarr, its quality profile and root folder, and a TV Show job. You only need the destination for the media type you use.

Availability, monitoring, and series type

Movie jobs can override Minimum Availability and monitoring under Delivery & schedule. Availability controls when Radarr considers a movie available; it does not restrict the discovery source to released films. Monitoring tells the destination what to follow.

Show jobs can select Sonarr series type standard, anime, or daily. The Anime Discovery recipe selects anime and uses Japanese animation rules. A show must map to the TVDB identity Sonarr recognizes; Blockbusterr reports a mapping failure rather than guessing from the title.

Root folders and quality profiles belong to the configured Radarr or Sonarr connection. Separate jobs do not provide separate Radarr instances or per-job library root folders. You can vary rules and delivery modes by job.

Set up requests through Jellyseerr or Seerr

1. Open Settings → Connections → Jellyseerr / Seerr.
2. Enter the request server’s URL and API key. A Docker-network example is http://seerr:5055.
3. Test the connection and save.
4. For manual approval, expand Request as a specific user and provide that account’s Request email and Request password. Configure Radarr and Sonarr in the request server so it can forward approved requests.
5. Under Settings → Automation, choose Jellyseerr / Seerr as the default delivery mode and save.
6. Preview a job, then run it when ready. A successful submission appears as Requested in Blockbusterr; inspect the request server for its approval status.

Choosing this mode does not guarantee a manual approval queue. API-key-only requests use administrative behavior and auto-approve. The optional Request user ID does not by itself switch to permission-respecting login. To review every suggestion, supply request email/password for an account without auto-approval permissions and verify the behavior with a small first run.

Blockbusterr applies its own rules before submission. The request server controls approval and request limits; Blockbusterr does not send it a score threshold. Both Jellyseerr and Seerr use the configuration key and API mode value jellyseerr.

Use a different mode for one job

For example, automatically add trusted science-fiction matches to Radarr while sending broader discovery through your approval workflow:

1. Configure both Radarr and Jellyseerr / Seerr.
2. Set the global delivery mode to Jellyseerr / Seerr.
3. Open the science-fiction job and expand Delivery & schedule.
4. Set Custom Mode to Direct (Radarr/Sonarr) and save.
5. Leave the other jobs on Use Global Default.
6. Preview each job and check its destination before enabling it.

The override affects future runs. Changing modes does not move or remove existing entries in your media services.

Preview and dry-run before delivery

Preview fetches candidates and explains their decisions without adding or requesting media. It is the easiest way to tune one job.

For testing executions across an installation, start Blockbusterr with BLOCKBUSTERR_DRY_RUN=true. Dry-run performs discovery and evaluation but simulates delivery. Development builds also use dry-run mode. It still needs usable provider connections and can make read-only requests to destination services; it is not an offline demo.

See Jobs for schedules, limits, and how to read outcomes.

When nothing reaches the destination

Observation	What to check
Preview rejects every title	Open the assigned rules and read each rejection reason
Titles already exist	Blockbusterr skips destination duplicates
Titles passed rules but were skipped	Check repeat handling, the job delivery cap, and global delivery ceilings
Run reports simulated delivery	Check the dry-run environment variable and build type
Request is pending	Review approval permissions in Jellyseerr or Seerr
Title is in Radarr/Sonarr but no file appears	Check availability, monitoring, quality profile, indexers, and download client there
Connection test fails in Docker	Use a hostname and port reachable from Blockbusterr’s container

Use Job Runs for execution totals and Activity Entries for the explanation attached to a particular title.