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 Automatically Send Daily Vegan Recipes on Telegram Using n8n and Airtable
   
   Meta Description:  
   Learn how to build a no-code Telegram bot using n8n that sends daily vegan recipes to users. This tutorial covers Airtable integration, Spoonacular API, and Telegram automation.
   
   Keywords:  
   n8n automation, Telegram bot, Airtable integration, Spoonacular API, vegan recipe bot, no-code workflow, daily recipe automation, API automation, Telegram API, Airtable API
   
   Third-Party APIs Used:  
   
   - Telegram Bot API  
   - Airtable API  
   - Spoonacular API (https://spoonacular.com/food-api)
   
   Article:
   
   Automating Daily Vegan Recipe Sharing on Telegram with n8n, Spoonacular, and Airtable
   
   Looking for a fun and functional automation project? Want to build a Telegram bot that sends your users a new vegan recipe every single day—without writing a single line of code? With the help of n8n, Airtable, and the Spoonacular recipe API, you can create a powerful, no-code workflow that delivers daily inspiration straight to your users.
   
   In this guide, we’ll break down a fully functional n8n (pronounced “n-eight-n”) workflow that combines Airtable, the Spoonacular API, and Telegram’s Bot API to automatically manage users and send daily vegan recipes via Telegram messages.
   
   What This Workflow Does
   
   Here’s what the final workflow accomplishes:
   
   1. Listens for new users joining the Telegram bot.
   2. Welcomes them with a message and sends a vegan recipe.
   3. Stores their chat ID and name in Airtable.
   4. Every day, fetches all chat IDs from Airtable.
   5. Requests a random vegan recipe from the Spoonacular API.
   6. Sends the recipe’s image and URL to all subscribed users via Telegram.
   
   Let’s walk through how this happens behind the scenes.
   
   Step 1: Capture Telegram Users Automatically
   
   The workflow begins with a Telegram Trigger node called “Telegram Trigger - people join bot.” n8n watches for new messages sent to the bot, which indicates a new user interaction.
   
   Once a user connects:
   
   - A welcome message is sent via the “Telegram - Welcome Message” node.
   - A vegan recipe is fetched using the Spoonacular API through the “Get recipes” node.
   - The recipe’s image and URL are then sent to the user using the “Telegram Recipe Image” and “Telegram Recipe URL” nodes.
   - User data (chat ID and first name) is captured and stored in Airtable using “Set1” and the “Airtable1” node, but only if the user is not already listed. This conditional check is done through the “Airtable” retrieval and the “IF” node.
   
   This ensures that you only store unique users and greet them with immediate value—a delicious vegan recipe!
   
   Step 2: Daily Recipe Delivery via Cron Trigger
   
   The second part of the workflow activates daily using the Cron node, which triggers based on a defined schedule (e.g., once a day).
   
   Here’s how the process flows:
   
   - “Cron” activates the workflow on schedule.
   - “Airtable2” pulls in the list of all subscribed users (chat IDs) from Airtable.
   - The “Set” node extracts chat IDs from Airtable data.
   - A new vegan recipe is fetched using “Get recipes from API,” another HTTP Request node querying the Spoonacular API.
   - The recipe image and title + URL are sent to each user through “Recipe Photo” and “Recipe URL” nodes respectively.
   
   This part of the workflow ensures that every user receives a daily vegan recipe without manual intervention.
   
   Using Airtable as a Lightweight CRM
   
   Why Airtable? It acts as a simple backend user store—holding Telegram chat IDs and corresponding usernames. It’s flexible, easy to use, and integrates seamlessly with n8n.
   
   The “Airtable1” node appends new users, while “Airtable” and “Airtable2” nodes are used to fetch and match data, creating a consistent and structured user management process.
   
   About the Spoonacular API
   
   The Spoonacular API is a powerful food-related endpoint that allows you to search for and retrieve recipes. In this workflow, a simple GET request like:
   
   https://api.spoonacular.com/recipes/random?apiKey=APIKEYHERE&number=1&tags=vegan
   
   is used to fetch a single, random vegan recipe. You can adjust the API call with different tags or keywords for varied results.
   
   About Telegram Bot Integration
   
   Telegram’s Bot API allows sending messages, photos, videos, and more to users via their chat ID. n8n includes built-in Telegram nodes, so no custom HTTP requests are needed. Just authenticate your bot via the Telegram API credentials and reference the chat ID to send media and messages.
   
   Why Use n8n?
   
   n8n is a powerful, open-source automation tool that provides a no-code/low-code alternative for complex workflows by leveraging visual programming. It supports a wide range of native integrations (Telegram, Airtable, HTTP requests, etc.) and logic operators, such as IF nodes, making it easy to build intricate automations like this one.
   
   Final Thoughts
   
   This workflow elegantly demonstrates how you can combine n8n’s automation power with real-world APIs to build a fun, practical tool—like a vegan recipe delivery bot!
   
   By integrating Telegram, Airtable, and Spoonacular, you achieve:
   
   - Full automation with no code.
   - Scalable interaction handling.
   - Always-fresh content via a trusted recipe database.
   
   For hobbyists, makers, or even startup marketers looking to engage an audience daily, this type of dynamic bot can serve as an engaging touchpoint. Expandability is endless—from adding keyboard buttons to customizing recipes based on user preferences.
   
   Start with this workflow, swap in your own API keys and data, and see how automation can deliver flavor daily, automatically.
   
   Happy automating—and bon appétit!

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.