This article provides a complete, practical walkthrough of the Http Telegram Send 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:
   How to Send a Daily Cocktail Recipe on Telegram Using n8n and TheCocktailDB
   
   Meta Description:
   Learn how to automate daily cocktail recipe delivery to a Telegram channel using n8n, HTTP requests, and TheCocktailDB API in just a few simple steps. No programming knowledge needed!
   
   Keywords:
   n8n, Telegram bot, TheCocktailDB, cocktail automation, automate Telegram, n8n Telegram workflow, cocktail recipe API, workflow automation, HTTP request n8n, no-code automation
   
   Third-Party APIs Used:
   1. TheCocktailDB API – https://www.thecocktaildb.com/api/
   2. Telegram Bot API – https://core.telegram.org/bots/api
   
   Article:
   
   Automate Your Happy Hour: How to Send a Daily Cocktail Recipe via Telegram Using n8n
   
   If you're someone who enjoys discovering new cocktails and want to share that passion with friends or a community, automating the delivery of daily drink recipes can be a fun and engaging experience. Using the no-code/low-code automation platform n8n (pronounced “n-eight-n”), combined with TheCocktailDB API and Telegram Bot API, you can create a workflow that sends a brand-new cocktail recipe every evening to a Telegram group or channel—all without writing a single line of complex code.
   
   In this article, we’ll break down how a simple n8n workflow fetches a random cocktail from the web and sends the image and instructions to a Telegram chat at the same time each day.
   
   Understanding the Components of the Workflow
   
   This n8n workflow consists of three key nodes:
   
   1. Cron: Triggers the workflow daily at 8 PM.
   2. HTTP Request: Fetches a random cocktail recipe from TheCocktailDB API.
   3. Telegram: Sends the cocktail photo and instructions to a targeted Telegram chat.
   
   Let's look at how each piece contributes to the overall workflow.
   
   Step 1: Schedule the Trigger with Cron
   
   The first node in the workflow is a Cron trigger. This allows you to automate the workflow execution at a specific time. In our case, the Cron trigger is set to fire every day at 20:00 (8 PM local server time), making it the ideal time to inspire your audience with an evening drink suggestion.
   
   This is configured via the Cron node, where the hour field is set to '20':
   
   "parameters": {
     "triggerTimes": {
       "item": [
         {
           "hour": 20
         }
       ]
     }
   }
   
   Once triggered, the workflow immediately moves into the next stage.
   
   Step 2: Fetch a Random Recipe with an HTTP Request
   
   The next node is an HTTP Request, which pulls data from TheCocktailDB—a free, open-source API for cocktail recipes and drink images. The request is made to the endpoint:
   
   https://www.thecocktaildb.com/api/json/v1/1/random.php
   
   Every time this URL is called, it returns a random cocktail recipe in JSON format. This includes the name of the drink, a photo URL, the list of ingredients, and detailed instructions on how to prepare it.
   
   This ensures that every day, your audience gets a fresh and different recipe, helping keep engagement and curiosity high.
   
   Step 3: Send the Recipe to Telegram
   
   Once the recipe is retrieved, it’s passed along to the Telegram node. This node uses the Telegram Bot API to send a message to a specific chat (group, channel, or individual).
   
   To make this work, you need to provide:
   - A valid bot token via the Telegram credential.
   - A chat ID (e.g., “-485396236” for a group).
   - The photo of the cocktail (strDrinkThumb returned from the HTTP request).
   - A caption text, here filled with the cocktail’s preparation instructions (strInstructions).
   
   Example of the Telegram node’s parameters:
   
   "parameters": {
     "file": "={{$node[\"HTTP Request\"].json[\"drinks\"][0][\"strDrinkThumb\"]}}",
     "chatId": "-485396236",
     "operation": "sendPhoto",
     "additionalFields": {
       "caption": "={{$node[\"HTTP Request\"].json[\"drinks\"][0][\"strInstructions\"]}}"
     }
   }
   
   The result? Every day at 8 PM, a beautiful cocktail picture along with easy-to-follow preparation instructions lands in your Telegram chat. Just sit back and let the bots take care of the rest!
   
   Bonus Tips for Customization
   
   - Add @username mentions or hashtags in the caption to encourage sharing or to tag participants.
   - Store previous cocktails in a database node to avoid duplicates.
   - Combine multiple nodes to include cocktail ingredients or even a link to a video preparation demo.
   
   Why Use n8n for This?
   
   n8n is a powerful tool for automating workflows without the need to deploy or manage custom scripts. With over 300+ integrations, it allows you to seamlessly communicate between APIs with visual drag-and-drop functionality. This makes it ideal for hobby projects like cocktail bots, or business-grade workflows that save time and resources.
   
   Conclusion
   
   Creating a Telegram bot that sends out daily cocktail recipes is not only a fantastic way to engage an audience, but a practical learning experience in using no-code tools like n8n. This workflow demonstrates how you can leverage free APIs and simple logic to automate content creation in just minutes.
   
   Whether it's for personal fun, hosting a virtual happy hour, or adding personality to a Telegram community, this automation can brighten up evenings with a splash of creativity—and a twist of lime.
   
   So go ahead, deploy this workflow, and enjoy a new drink every day. Cheers to automation!
   
   —End—

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.