This article provides a complete, practical walkthrough of the Http Telegram Automation 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 Daily Affirmations with n8n, Telegram, and an Affirmation API
   
   Meta Description:  
   Learn how to create a simple yet powerful n8n workflow that sends daily motivational affirmations via Telegram using a public API and scheduled automation.
   
   Keywords:  
   n8n, Telegram bot, daily affirmations, automation, no-code workflow, affirmations API, HTTP request, self-improvement, chat automation, API integration
   
   Third-Party APIs Used:
   
   - Affirmation API (https://affirmations.dev) – to retrieve a new affirmation
   - Telegram Bot API – to send messages via Telegram
   
   Article:
   
   A Gentle Boost Every Morning: Automate Daily Affirmations Using n8n and Telegram
   
   In today's fast-paced world, a simple daily affirmation can go a long way in setting a positive tone for the day. What if you could receive one automatically, every morning — without opening an app, or searching the web? Using the no-code/low-code automation tool n8n, a Telegram bot, and a free affirmations API, this becomes not just possible, but easy.
   
   In this guide, we’ll walk you through how an n8n workflow is designed to fetch a motivational message each morning and deliver it straight to your Telegram inbox. Even better, the whole setup is based on open-source tools and publicly available APIs.
   
   The Automation Overview
   
   This n8n workflow, titled "Daily Text Affirmations", is a simple yet effective automation composed of three main steps:
   
   1. Cron Trigger – Schedules the action every day at 9 AM  
   2. HTTP Request – Fetches a fresh affirmation from a public API  
   3. Telegram Node – Sends the affirmation via a Telegram bot  
   
   Let’s break down how each part works.
   
   Step 1: Scheduling the Workflow with Cron
   
   The first node in the workflow is a Cron node, responsible for triggering the workflow at a specific time every day. In this case, the automation is set to run at 9:00 AM daily. You can easily adjust the time according to your preference by modifying the "hour" parameter in the node’s settings.
   
   This ensures that every morning at the set time, n8n wakes up and begins the workflow — no manual action required.
   
   Step 2: Retrieving the Affirmation via HTTP Request
   
   The next node is an HTTP Request to the endpoint https://affirmations.dev — a simple, free API that returns a JSON response with a key named "affirmation" containing a positive message.
   
   Here’s an example of the kind of response you might get:
   
   {
     "affirmation": "You are capable of achieving great things."
   }
   
   The HTTP Request node does not require any additional configuration or authentication, making it perfect for lightweight use cases like this one.
   
   Step 3: Delivering the Message via Telegram
   
   Once the affirmation is received, it’s passed along to the Telegram node. This node is configured to send a customized message to a specific user via Telegram, using a Telegram Bot Token (provided through Telegram’s BotFather).
   
   The message format is set as follows:
   
   Hey Daniel, here's your daily affirmation...
   
   {{ $node["HTTP Request"].json["affirmation"] }}
   
   This simple template allows the Telegram node to dynamically insert the actual affirmation into the outgoing message, providing a personal touch and a seamless experience.
   
   Getting It Running
   
   Although the workflow is listed as "active: false" in the configuration above (which means it won’t run automatically until activated), it only takes one click within the n8n UI to activate it.
   
   You will need the following prerequisites:
   
   - A running instance of n8n (either self-hosted or via n8n.cloud)
   - A Telegram account
   - A Telegram bot token (created using BotFather)
   - Your chat ID or user ID to direct the messages properly
   
   Once your Telegram bot is set up and chats are authenticated, the workflow is fully operational.
   
   Why This Workflow Matters
   
   Using automation tools like n8n to inject small moments of positivity into our lives is a great example of how technology can work harmoniously with wellbeing goals. This setup is:
   
   - Entirely free (thanks to public APIs and Telegram)
   - Customizable (you can change the message, time, or delivery method)
   - Code-free (no complex scripting necessary)
   
   Conclusion
   
   With just three nodes, you can create a meaningful, daily ritual — a moment that reminds you (or someone you care about) to start the day positively. Whether you’re an automation enthusiast or a beginner, this n8n workflow is a perfect mix of simplicity and value.
   
   And who says automation is only for business? Sometimes, it's just about sending a little kindness — on schedule.
   
   Ready to modify or scale it? Why not add a random quote API, incorporate SMS delivery, or store the messages in a Google Sheet for reflection? The possibilities are endless.
   
   Start your day right — automatically.

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.