This article provides a complete, practical walkthrough of the Functionitem Telegram Create Webhook n8n agent. It connects HTTP Request, Webhook across approximately 1 node(s). Expect a Intermediate setup in 15-45 minutes. One‑time purchase: €29.

What This Agent Does

This agent orchestrates a reliable automation between HTTP Request, Webhook, handling triggers, data enrichment, and delivery with guardrails for errors and rate limits.

It streamlines multi‑step processes that would otherwise require manual exports, spreadsheet cleanup, and repeated API requests. By centralizing logic in n8n, it reduces context switching, lowers error rates, and ensures consistent results across teams.

Typical outcomes include faster lead handoffs, automated notifications, accurate data synchronization, and better visibility via execution logs and optional Slack/Email alerts.

How It Works

The workflow uses standard n8n building blocks like Webhook or Schedule triggers, HTTP Request for API calls, and control nodes (IF, Merge, Set) to validate inputs, branch on conditions, and format outputs. Retries and timeouts improve resilience, while credentials keep secrets safe.

Third‑Party Integrations

• HTTP Request
• Webhook

Import and Use in n8n

1. Open n8n and create a new workflow or collection.
2. Choose Import from File or Paste JSON.
3. Paste the JSON below, then click Import.
4. Show n8n JSON

   Title:  
   Automating Torrent Downloads with n8n: A Smart Workflow for Searching & Downloading Movies
   
   Meta Description:  
   Learn how to automate movie torrent searches and downloads using an n8n workflow integrated with TorrentSearchApi and Transmission, complete with Telegram notifications.
   
   Keywords:  
   n8n workflow, torrent automation, Transmission RPC, Telegram bot notification, TorrentSearchApi, automate torrent download, KickassTorrents, RARBG, n8n tutorial, workflow automation
   
   Third-party APIs Used:
   
   - TorrentSearchAPI (JavaScript npm package)
   - Transmission RPC API (via HTTP request)
   - Telegram Bot API (via n8n Telegram node)
   
   Article:
   
   In today’s fast-paced digital environment, automation is transforming how we manage everyday tasks — and yes, even how we download and track media content. If you’ve ever wanted to build an intelligent bot to search for and download torrents based on a single user input, then this article is for you. We'll explore how to use the powerful open-source automation tool n8n to create a seamless workflow that receives a movie title, searches for the torrent, downloads it via Transmission, and notifies you through Telegram. Let’s dive in.
   
   The Goal of the Workflow  
   The end goal is simple: a user submits a movie title (e.g. "Inception") through a webhook. The n8n workflow will then:
   
   - Search for that title across multiple torrent providers.
   - If found, automatically start downloading the torrent using Transmission.
   - If not found, notify the user via Telegram.
   - Handle session errors from Transmission gracefully by reattempting with an updated token.
   
   The Workflow Breakdown
   
   1. Webhook Node – Listening for Requests  
   At the heart of this automation is the Webhook node. It listens for POST requests on a unique endpoint and expects the body to include a key named "title" representing the movie name. The "rawBody" option is set to true, which means we are handling the request as-is, and parsing the content as needed in the next step.
   
   2. SearchTorrent – Scraping Torrent Links  
   Once the title is received, a FunctionItem node named SearchTorrent uses the TorrentSearchApi library to search for the given movie across torrent websites. In this particular configuration, it enables KickassTorrents and RARBG as providers. The function searches for the movie with a maximum of five results, and attaches the torrent data back to the item. If no results are found, it flags the item as not found.
   
   Relevant Code Snippet in the Node:
   ```javascript
   const torrents = await TorrentSearchApi.search(item.title, 'All', 5);
   item.torrents = torrents;
   item.found = !!torrents.length;
   ```
   
   3. IF Node – Result Check  
   This 'IF' node checks whether a torrent was successfully found. If true, the workflow proceeds to initiate the download. If false, it branches to notify the user that no torrents were found.
   
   4. Torrent Not Found – Alert via Telegram  
   In the case where no torrent result is found, the workflow uses the Telegram node to send a custom message to a specified chat ID:  
   “Film [movie title] non trovato.”  
   This simply translates to “Movie [movie title] not found” — a helpful notification that closes the loop for the user.
   
   5. Start Download – Initiate Transmission RPC  
   If a torrent is available, the workflow constructs an HTTP POST request (using the HTTP Request node) to the Transmission RPC API endpoint. The necessary torrent is added with the magnet URI, and the download kicks off. Crucially, this includes proper authentication and a session ID in the headers — a common requirement for interacting with Transmission via API.
   
   6. Handling Transmission Session Errors  
   Transmission often rejects unauthenticated or expired session requests with a status code 409. The workflow is built to handle that. It checks the response of the earlier HTTP request to see if a 409 error was encountered. If it was, a new request is made using the updated session ID returned in the error headers. This ensures your workflow is resilient and adaptive to Transmission’s session handling.
   
   7. Final Confirmation – Success via Telegram  
   Once the torrent has been successfully added to Transmission — either through the initial attempt or after renewing the session token — the automation sends a celebratory message via Telegram:  
   “Scarico Inception! Titolo: Inception.2010.1080p.BluRay.x264…”  
   This message helps the user confirm that the correct torrent (first match) is now downloading.
   
   Why This Workflow Is Awesome
   
   - Zero Manual Torrent Searching: You no longer need to navigate torrent sites manually.
   - Reliable Search with Fallbacks: Utilizing two major providers — KickassTorrents and RARBG — boosts your chances of finding quality torrents.
   - Human-in-the-Loop Notifications: Telegram ensures you’re always updated, whether a torrent was found or not.
   - Robust Error Handling: It accounts for real-world Transmission errors like session invalidation and automatically recovers.
   
   Security & Practical Considerations
   
   - Ensure you never expose your webhook URL publicly to avoid misuse.
   - Use verified and clean torrent sources. Adapt the workflow to add more trusted sources if needed.
   - Keep your Transmission RPC and Telegram bot API credentials secure via n8n’s credentials manager.
   
   Conclusion  
   This powerful workflow is a fantastic showcase of how n8n can orchestrate a variety of services to create an intelligent, responsive automation system with real-world utility. From scraping torrent indexes, retrying failed requests, and integrating with Telegram for status updates — all it takes is a few visual nodes and some JavaScript to build your own digital movie assistant.
   
   Whether you're a developer, power user, or automation enthusiast, this workflow will not only save you time but also demonstrate the incredible flexibility of n8n as a no-code/low-code tool. Happy automating!
   
   Ready to try it yourself? Just copy the workflow JSON in the article, tweak the API tokens, and you're all set. 🚀

5. Set credentials for each API node (keys, OAuth) in Credentials.
6. Run a test via Execute Workflow. Inspect Run Data, then adjust parameters.
7. Enable the workflow to run on schedule, webhook, or triggers as configured.

Tips: keep secrets in credentials, add retries and timeouts on HTTP nodes, implement error notifications, and paginate large API fetches.

Validation: use IF/Code nodes to sanitize inputs and guard against empty payloads.

Why Automate This with AI Agents

AI‑assisted automations offload repetitive, error‑prone tasks to a predictable workflow. Instead of manual copy‑paste and ad‑hoc scripts, your team gets a governed pipeline with versioned state, auditability, and observable runs.

n8n’s node graph makes data flow transparent while AI‑powered enrichment (classification, extraction, summarization) boosts throughput and consistency. Teams reclaim time, reduce operational costs, and standardize best practices without sacrificing flexibility.

Compared to one‑off integrations, an AI agent is easier to extend: swap APIs, add filters, or bolt on notifications without rewriting everything. You get reliability, control, and a faster path from idea to production.

Best Practices

• Credentials: restrict scopes and rotate tokens regularly.
• Resilience: configure retries, timeouts, and backoff for API nodes.
• Data Quality: validate inputs; normalize fields early to reduce downstream branching.
• Performance: batch records and paginate for large datasets.
• Observability: add failure alerts (Email/Slack) and persistent logs for auditing.
• Security: avoid sensitive data in logs; use environment variables and n8n credentials.

FAQs

Can I swap integrations later? Yes. Replace or add nodes and re‑map fields without rebuilding the whole flow.

How do I monitor failures? Use Execution logs and add notifications on the Error Trigger path.

Does it scale? Use queues, batching, and sub‑workflows to split responsibilities and control load.

Is my data safe? Keep secrets in Credentials, restrict token scopes, and review access logs.