Search and download torrents using transmission-daemon
Needs changesNeeds changes. This template uses 1 thing(s) that n8n 3.0 removes: Function Item (legacy). 1 breaking item(s) found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 8 nodes and runs when an HTTP POST request hits its webhook URL. Along the way it connects Telegram.
How it runs
Trigger: When an HTTP POST request hits its webhook URL.
- SearchTorrent (Function Item): runs custom JavaScript per item (legacy Function Item node)
- If: checks a condition and branches into true / false
- Start download (HTTP Request): calls an HTTP API
- Torrent not found (Telegram): uses Telegram
- If: checks a condition and branches into true / false
- Start download new token (HTTP Request): calls an HTTP API
- Telegram: uses Telegram
Services it uses
Before you upgrade to n8n 3.0
1 thing in this workflow is removed in n8n 3.0. Fix it before you upgrade:
- Function Item (legacy) in SearchTorrent: replace with Code node, mode 'Run Once for Each Item'.
Rather not rewrite it? Many of these flows can be rebuilt in Make (free plan).
| Removed in 3.0 | Replace with |
|---|---|
| Function Item (legacy) SearchTorrent | Code node, mode 'Run Once for Each Item' |
Nodes used (5)
- Webhook
n8n-nodes-base.webhook - Function Item
n8n-nodes-base.functionItem - HTTP Request
n8n-nodes-base.httpRequest - If
n8n-nodes-base.if - Telegram
n8n-nodes-base.telegram
From the author
Ok google download "movie name" I develop this automation to improve my quality of life in handling torrents in my media-center. Goal Automate the search operations of a movie based on its name and trigger a download using your transmission-daemon. Setup…