Automation library · Alerts and monitoring

Manage User Authentication with Telegram and Redis Cache

Started by an incoming Telegram message, and works across Google Sheets, Redis and Telegram. 14 steps, 2 branches: a working afternoon to understand properly.

Medium

14 stepsMedium: a working afternoon
2Branches: places the flow splits
0Loops or waits
3Services it connects to

The flow

Starts it 2Logic 7Service 5

The steps in the order they run, from what starts it.

  1. 1Get MessageTelegram triggerStarts it
  2. 2When Executed by Another WorkflowExecute Workflow triggerStarts it
  3. 3Edit FieldsSetLogic
  4. 4Get UserGoogle SheetsService
  5. 5MergeMergeLogic
  6. 6Edit Fields2SetLogic
  7. 7Find Cached UserRedisService
  8. 8Is CachedSwitchLogic
  9. 9Find UserGoogle SheetsService
  10. 10UserIdMergeLogic
  11. 11Is New UserSwitchLogic
  12. 12Cache UserRedisService
  13. 13Get UserIdCodeLogic
  14. 14Create UserGoogle SheetsService

How it's built

Starts on
An incoming Telegram message
Steps
14, with 2 branches
Size
Medium: a working afternoon
Connects to
Google Sheets, Redis, Telegram
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account, plus your own Google Sheets, Redis and Telegram accounts. You connect your own accounts after importing it; none are included.

What starts it?

It starts on an incoming Telegram message.

Does it use AI?

No. Every step is fixed logic or a call to a service, so it does the same thing every time.

How long does it take to set up?

Plan an afternoon. 14 steps is enough that you should read each one before running it.

How do I import it?

Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.

Before you run it

Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 14 steps before you point it at anything that matters.