Overview
This node integrates with a qBittorrent instance via its web API to add new torrents for downloading. It is useful in automation workflows where you want to programmatically manage torrent downloads, such as adding multiple torrents from URLs, organizing them into categories, or setting specific download/upload limits without manual intervention.
Practical examples include:
- Automatically adding torrents from RSS feeds or other sources.
- Setting custom download folders and categories for better organization.
- Controlling bandwidth usage by setting upload/download speed limits per torrent.
- Managing seeding behavior by specifying ratio or time limits.
Properties
| Name | Meaning |
|---|---|
| Torrent URL | URLs of the torrent files to add, separated by newlines. |
| Save Path | Folder path where the torrent data will be downloaded. |
| Cookie | Cookie string sent when downloading the .torrent file (useful for authenticated downloads). |
| Category | Category label assigned to the torrent for organizational purposes. |
| Tags | Comma-separated tags associated with the torrent. |
| Skip Hash Checking | Whether to skip hash checking on added torrents; options: "true", "false" (default). |
| Paused | Add the torrent in paused state; options: "true", "false" (default). |
| Create Root Folder | Whether to create a root folder for the torrent; options: "true", "false", unset (default). |
| Rename Torrent | New name to assign to the torrent upon adding. |
| Upload Limit | Upload speed limit for the torrent in bytes per second. |
| Download Limit | Download speed limit for the torrent in bytes per second. |
| Ratio Limit | Share ratio limit after which seeding stops. |
| Seeding Time Limit | Maximum seeding time in minutes before stopping. |
| Automatic Torrent Management | Enable automatic torrent management; boolean true/false. |
| Sequential Download | Enable sequential download; options: "true", "false" (default). |
| First Last Piece Priority | Prioritize downloading the first and last pieces of the torrent; options: "true", "false". |
Output
The node outputs JSON data representing the response from the qBittorrent API after attempting to add the torrent(s). This typically includes status information about the operation, such as success confirmation or error details.
No binary data output is involved in this operation.
Dependencies
- Requires access to a running qBittorrent instance with its Web UI/API enabled.
- Requires an API authentication token or API key credential configured in n8n to authenticate requests.
- The node sends HTTP POST requests with multipart/form-data content type to the qBittorrent API endpoint
/torrents/add.
Troubleshooting
Common issues:
- Invalid or unreachable qBittorrent URL or API endpoint.
- Missing or incorrect API authentication credentials.
- Incorrectly formatted torrent URLs or unsupported torrent file links.
- Network connectivity problems between n8n and the qBittorrent server.
Error messages:
- Authentication errors indicate invalid or missing API credentials; verify and update credentials.
- HTTP 400 or 500 errors may indicate malformed requests or server-side issues; check parameter values and server logs.
- Timeout errors suggest network issues or that the qBittorrent instance is not responding; ensure the service is running and accessible.