Templates / Manage User Authentication with Telegram, Redis Cache and Google Sheets

Manage User Authentication with Telegram, Redis Cache and Google Sheets

Ready for 3.0

by Archit Jain ✓ · 376 views · created 2025-06-01 · Engineering

Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.

What 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).

  1. Get User (Google Sheets): uses Google Sheets
  2. Edit Fields (Edit Fields (Set)): sets or maps fields
  3. Edit Fields (Edit Fields (Set)): sets or maps fields
  4. Merge: merges the data from its input branches
  5. Find Cached User (Redis): uses Redis
  6. Is Cached (Switch): routes items into branches
  7. Find User (Google Sheets): uses Google Sheets
  8. UserId (Merge): merges the data from its input branches
  9. Is New User (Switch): routes items into branches
  10. Cache User (Redis): uses Redis

…plus 2 more steps. See the full node list below.

Services it uses

TelegramGoogle SheetsRedis

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)

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…

Excerpt from Archit Jain's description on n8n.io.

View the original on n8n.io → Check your own copy

Get the weekly “what broke” email

New templates, newly broken ones, and n8n release changes. One short email a week.

Form not loading? Subscribe here.