This workflow follows the HTTP Request → Redis recipe pattern — see all workflows that pair these two integrations.
The workflow JSON
Copy or download the full n8n JSON below. Paste it into a new n8n workflow, add your credentials, activate. Full import guide →
Credentials you'll need
Each integration node will prompt for credentials when you import. We strip credential IDs before publishing — you'll add your own.
redistelegramApi
For the full experience including quality scoring and batch install features for each workflow upgrade to Pro
About this workflow
Telegram Meditation Bot (Fixed with State). Uses telegramTrigger, redis, telegram, httpRequest. Event-driven trigger; 26 nodes.
Source: https://gist.github.com/IlgizIlgiz/0087e2de1fd7ba7be65eced419f34b2d — original creator credit. Request a take-down →
Related workflows
Workflows that share integrations, category, or trigger type with this one. All free to copy and import.
Telegram Wait. Uses stickyNote, httpRequest, redis, noOp. Event-driven trigger; 36 nodes.
Telegram Meditation Bot (Fixed with State). Uses telegramTrigger, redis, telegram, httpRequest. Event-driven trigger; 26 nodes.
Telegram Meditation Bot (Fixed with State). Uses telegramTrigger, redis, telegram, httpRequest. Event-driven trigger; 26 nodes.
Telegram Meditation Bot (Fixed with State). Uses telegramTrigger, redis, telegram, httpRequest. Event-driven trigger; 26 nodes.
Telegram Meditation Bot (Fixed with State). Uses telegramTrigger, redis, telegram, httpRequest. Event-driven trigger; 26 nodes.