Periodically send data from HTTP Request node to Telegram
Needs changesNeeds changes. This template uses 1 thing(s) that n8n 3.0 removes: Cron. 1 breaking item(s) found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 3 nodes and runs on a schedule (legacy Cron node). Along the way it connects Telegram. It also calls thecocktaildb.com over HTTP.
How it runs
Trigger: On a schedule (legacy Cron node).
- HTTP Request: calls thecocktaildb.com
- Telegram: send photo
Services it uses
HTTP calls to: thecocktaildb.com
Before you upgrade to n8n 3.0
1 thing in this workflow is removed in n8n 3.0. Fix it before you upgrade:
- Cron: replace with Schedule Trigger.
| Removed in 3.0 | Replace with |
|---|---|
| Cron Cron | Schedule Trigger |
Nodes used (3)
- Telegram
n8n-nodes-base.telegram - Cron
n8n-nodes-base.cron - HTTP Request
n8n-nodes-base.httpRequest