Actions67
- Torrent Actions
- Usenet Actions
- Web Download Actions
- General Actions
- Notification Actions
- User Actions
- RSS Feed Actions
- Integration Actions
- Queued Actions
- Stream Actions
- Search Actions
- Vendor Actions
- Relay Actions
Torrent → Control Torrent
AI-generatedSummary
Control Torrent operation for the TorBox node, enabling users to pause, resume, delete, or reann a torrent by providing its ID and selecting an operation (pause, resume, delete, or reann).
Inputs
- torrent_id (required) — The ID of the torrent to control.
- controlOperation (required) — The control operation to perform. Options: pause, resume, delete, reannounce.
Output shape
POST torrents/controltorrent with torrent_id and operation parameters. Returns the API response. The API likely returns the updated torrent status or a success indicator. I won't guess beyond what's in the source.,... (this is just a placeholder, I need to output actual JSON) ... The actual output JSON should describe the operation concisely, leading with the verb, grounded in the properties and source. I need to figure out the exact JSON schema expected. Since it's not provided, I'll have to infer a standard format for n8n node operation descriptions, or perhaps the user expects a specific JSON schema that's standard in this context. Sometimes these prompts expect a specific JSON schema from the NCNodes directory format. Let me think about common n8n node description schemas. Sometimes they want: `{
...