Manage User Authentication with Telegram, Redis Cache and Google Sheets
Ready for 3.0What this workflow does
This workflow has 14 nodes and runs when another workflow calls it (plus 1 other trigger). Along the way it connects Telegram, Google Sheets and Redis.
How it runs
Trigger: When another workflow calls it (plus 1 other trigger).
- Get User (Google Sheets): uses Google Sheets
- Edit Fields (Edit Fields (Set)): sets or maps fields
- Edit Fields (Edit Fields (Set)): sets or maps fields
- Merge: merges the data from its input branches
- Find Cached User (Redis): uses Redis
- Is Cached (Switch): routes items into branches
- Find User (Google Sheets): uses Google Sheets
- UserId (Merge): merges the data from its input branches
- Is New User (Switch): routes items into branches
- Cache User (Redis): uses Redis
…plus 2 more steps. See the full node list below.
Services it uses
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (8)
- Telegram Trigger
n8n-nodes-base.telegramTrigger - Google Sheets
n8n-nodes-base.googleSheets - Switch
n8n-nodes-base.switch - Code
n8n-nodes-base.code - Merge
n8n-nodes-base.merge - Redis
n8n-nodes-base.redis - Execute Workflow Trigger
n8n-nodes-base.executeWorkflowTrigger - Edit Fields (Set)
n8n-nodes-base.set
From the author
How It Works - Telegram bot listens for messages and uses chat ID as the unique user identifier. - Checks Google Sheets for existing users; registers new users if not found. - Caches active sessions in Redis for fast lookup and login-state handling. - Stores…