Clean up watched Jellyfin media and completed torrents with Transmission

Workflow preview

100%

Open on n8n.io

$20/month : Unlimited workflows

2500 executions/month

Try free

THE #1 IN WEB SCRAPING

Scrape any website without limits

Try free

HOSTINGER

Early Deal
DISCOUNT 20%

Self-hosted n8n

Unlimited workflows - from $4.99/mo

Try free

#1 hub for scraping, AI & automation

6000+ actors - $5 credits/mo

Try free

1. Workflow Overview

Quick Overview This scheduled workflow cleans up watched media in Jellyfin and removes completed torrents from Transmission by calling both APIs, deleting played items in Jellyfin, refreshing the J...

Best for

File Management automation workflows
intermediate n8n builders looking for reusable templates

Tools used

n8n-nodes-base.scheduletrigger, n8n-nodes-base.set, n8n-nodes-base.httprequest, n8n-nodes-base.splitout, n8n-nodes-base.if, n8n-nodes-base.stickynote

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by David.

Original n8n.io source

1.1 Workflow description

Title: Clean up watched Jellyfin media and completed torrents with Transmission
Workflow name: Clean up watched Jellyfin media and completed torrents with Transmission

Quick Overview

This scheduled workflow cleans up watched media in Jellyfin and removes completed torrents from Transmission by calling both APIs, deleting played items in Jellyfin, refreshing the Jellyfin library, and deleting torrents (including local data) once they reach the completed status.

How it works

Runs daily on a schedule at the configured hour.
Sets the Jellyfin base URL, Jellyfin user ID, and Transmission base URL used for subsequent API calls.
Fetches played Movies and Episodes from Jellyfin for the configured user, deletes each returned item, and triggers a Jellyfin library refresh.
Calls the Transmission RPC endpoint to retrieve the required X-Transmission-Session-Id, then re-requests the torrent list using that session header.
Splits the Transmission response into individual torrents, filters to those with status 6 (completed), and removes each matching torrent while also deleting its local data.

Setup

Add Jellyfin HTTP Header Auth credentials (for example, an API key header) and fill in the Jellyfin server URL and target Jellyfin user ID in the Variables step.
Add Transmission Bearer Auth credentials and set your Transmission base URL in the Variables step.
Confirm your Transmission instance allows RPC access at /transmission/rpc and that your Jellyfin server exposes the /Users/{userId}/Items, /Items/{id}, and /Library/Refresh endpoints for the provided credentials.

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - Schedule Trigger

Type / Role: n8n-nodes-base.scheduleTrigger - scheduleTrigger
Config choices: Version 1.2

Block 2 - Variables

Type / Role: n8n-nodes-base.set - set
Config choices: Version 3.4

Block 3 - Jellyfin: get items

Type / Role: n8n-nodes-base.httpRequest - httpRequest
Config choices: Version 4.2

Block 4 - Jellyfin: delete item

Type / Role: n8n-nodes-base.httpRequest - httpRequest
Config choices: Version 4.2

Block 5 - Jellyfin: refresh library

Type / Role: n8n-nodes-base.httpRequest - httpRequest
Config choices: Version 4.2

Block 6 - Get session id

Type / Role: n8n-nodes-base.httpRequest - httpRequest
Config choices: Version 4.2

Block 7 - Extract session id

Type / Role: n8n-nodes-base.set - set
Config choices: Version 3.4

Block 8 - Check all torrents

Type / Role: n8n-nodes-base.httpRequest - httpRequest
Config choices: Version 4.2

Block 9 - Split Out

Type / Role: n8n-nodes-base.splitOut - splitOut
Config choices: Version 1

Block 10 - If torrent transferred to Jellyfin

Type / Role: n8n-nodes-base.if - if
Config choices: Version 2.2

Block 11 - Delete torrent

Type / Role: n8n-nodes-base.httpRequest - httpRequest
Config choices: Version 4.2

Block 12 - Overview

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 13 - Section - Jellyfin

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 14 - Section - Transmission

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

3. Summary Table

Workflow	Clean up watched Jellyfin media and completed torrents with Transmission
Complexity	intermediate
Nodes	14
Categories	File Management
Author	David
Published	08 Jun 2026

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

Use the JSON export at /data/workflows/16184/16184.json as the source template for this automation.
2. Import the template into n8n

Open n8n, import the downloaded JSON, and review each node before activating the workflow.
3. Configure credentials and variables

Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
4. Test with sample data

Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
5. Activate and monitor

Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Download workflow JSON Original n8n.io source File Management workflows

Frequently asked questions

What does Clean up watched Jellyfin media and completed torrents with Transmission do?

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your File Management use case.

David

2 workflows

Nodes

n8n-nodes-base.scheduletrigger n8n-nodes-base.set n8n-nodes-base.httprequest n8n-nodes-base.splitout n8n-nodes-base.if n8n-nodes-base.stickynote

Complexity

intermediate

Published 08 Jun 2026

Likes 0

View on n8n.io Download Workflow

Install path: /data/workflows/16184/16184.json

Share Your Workflow

Have a useful automation to share? Publish it and help the community.

Submit Your Template How to Submit

Related Workflows

Export WordPress data to a CSV file

## Quick Overview This workflow manually exports all records from a WordPress site, converts the returned JSON into a CSV file, and saves the CSV to disk on the n8n server. ## How it works 1. Starts when you manually click Execute in n8n. 2. Fetches all available items from your connected WordPress site via the WordPress API. 3. Converts the WordPress JSON response into a CSV file. 4. Writes the generated CSV to the n8n server as `data.csv`. ## Setup 1. Add WordPress API credentials in n8n (site URL, username, and an Application Password). 2. Choose the WordPress resource to export in the WordPress node and confirm the data shape matches what you want in the CSV. 3. Update the output file path/name in the file-writing step and ensure the target directory is writable on your n8n host (for example `/home/node/.n8n/data.csv`).

View

Aggregate shipment tracking statuses with FedEx, UPS and DHL

## Quick Overview This workflow runs every 15 minutes to fetch active shipments from an n8n Data Table, query FedEx, UPS, or DHL tracking APIs with circuit-breaker protection, normalize each response into a shared status schema, and upsert the latest status back into the same table. ## How it works 1. Runs every 15 minutes on a schedule. 2. Loads all rows from the n8n Data Table `shipment_tracking` and filters out shipments already marked as DELIVERED or RETURNED_TO_SENDER. 3. Routes each remaining shipment by `carrier` and marks unsupported carriers with a canonicalStatus of UNKNOWN. 4. For FedEx, UPS, and DHL shipments, checks a per-carrier circuit breaker and either calls the carrier’s tracking API or skips the call when the breaker is open. 5. Normalizes each carrier response (or skip) into a canonical status (for example PRE_TRANSIT, IN_TRANSIT, OUT_FOR_DELIVERY, DELIVERED, EXCEPTION, UNKNOWN) while updating the breaker state based on 429/5xx/network failures. 6. Merges all carrier results and upserts the latest fields back into the `shipment_tracking` Data Table using `trackingNumber` as the match key. ## Setup 1. Create the n8n Data Table named `shipment_tracking` with columns such as `trackingNumber`, `carrier`, `canonicalStatus`, `rawStatus`, `breakerState`, `httpStatus`, and `checkedAt`, and seed it with shipments (use lowercase carriers: `fedex`, `ups`, `dhl`). 2. Add OAuth2 credentials for the FedEx Track API and select them in the FedEx HTTP request step. 3. Add OAuth2 credentials for the UPS Track API and select them in the UPS HTTP request step. 4. Add DHL API authentication (as configured for the DHL request in this template) and select it in the DHL HTTP request step. 5. Activate the workflow so workflow static data persists between runs and the circuit breaker state is maintained.

View

Sync PostgreSQL changes to SharePoint lists via Microsoft Graph with Teams alerts

## Quick overview This workflow runs every 15 minutes and uses a watermark to incrementally sync recently updated rows from PostgreSQL to a Microsoft SharePoint list via the Microsoft Graph $batch API, posting run summaries and deduplicated error alerts to a Microsoft Teams channel. ## How it works 1. Runs every 15 minutes on a schedule and loads SharePoint/Teams configuration plus the last successful sync timestamp stored in n8n static data. 2. Queries PostgreSQL for rows updated since the last watermark timestamp and aggregates the results into a single batchable payload. 3. If no rows are returned, advances the watermark to the current run start time and posts a sync summary to Microsoft Teams. 4. If rows exist, chunks them into Graph-compliant $batch requests (max 20 operations per batch) that create items in the target SharePoint list. 5. Sends each batch to the Microsoft Graph $batch endpoint with retries and classifies per-item results into successes, failures, and 429 throttling. 6. Aggregates results across all batches and, when new failures appear, posts a Microsoft Teams alert listing the failed/throttled source IDs while suppressing repeat alerts for previously seen IDs. 7. Updates the stored watermark only when there are zero failures, then posts a Microsoft Teams sync summary with counts and watermark status. ## Setup 1. Add a PostgreSQL credential, then update the SQL query to use your table name and an indexed updated_at timestamptz column. 2. Add a Microsoft Graph OAuth2 credential with permissions to create SharePoint list items, and set your SharePoint site ID and list ID in the workflow configuration values. 3. Edit the field mapping used for SharePoint list item creation so your PostgreSQL columns map to your SharePoint field internal names. 4. Add Microsoft Teams credentials and set the target Team ID and Channel ID for both the sync summary and error alert messages. ## Requirements - PostgreSQL database with an indexed updated_at timestamptz column on the source table - Microsoft Graph OAuth2 credential with Sites.ReadWrite.All permission for the target SharePoint site - Microsoft SharePoint list with field internal names matching the column mapping in the batch payload builder - Microsoft Teams credential with permission to post to the configured team and channel ## Customization - Change the polling interval in the Every 15 Minutes Trigger node to run more or less frequently depending on your data update volume. - Adjust the batchSize value in the Set Configuration Parameters node — the maximum is 20 per Graph API constraint and is enforced in code regardless of what is set here. - Modify the SQL query in the Query Updated Rows from Postgres node to add filters, joins, or column selections beyond the default updated_at watermark check. - Extend the batch payload builder in the Construct Graph Batch Payloads node to support upsert logic by adding a dependsOn field to chain an existence-check request before each write. - Add a dead-letter table in PostgreSQL and exclude persistently failing rows from the query using AND id NOT IN (SELECT id FROM sync_dead_letter) to break infinite retry cycles.

View

Need Custom Automation?

Get help designing a custom n8n workflow that connects your stack and fits your process.

Clean up watched Jellyfin media and completed torrents with Transmission

Workflow preview

1. Workflow Overview

Best for

Tools used

Source and attribution

1.1 Workflow description

Quick Overview

How it works

Setup

1.2 Logical Blocks

2. Block-by-Block Analysis

Block 1 - Schedule Trigger

Block 2 - Variables

Block 3 - Jellyfin: get items

Block 4 - Jellyfin: delete item

Block 5 - Jellyfin: refresh library

Block 6 - Get session id

Block 7 - Extract session id

Block 8 - Check all torrents

Block 9 - Split Out

Block 10 - If torrent transferred to Jellyfin

Block 11 - Delete torrent

Block 12 - Overview

Block 13 - Section - Jellyfin

Block 14 - Section - Transmission

3. Summary Table

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

2. Import the template into n8n

3. Configure credentials and variables

4. Test with sample data

5. Activate and monitor

5. General Notes & Resources

Frequently asked questions