Automation library · Alerts and monitoring

Onboard frontline workers with Telegram and DeepSeek

Started by an incoming Telegram message, and works across Notion and Telegram. 35 steps, 3 branches: large, and worth reading before you trust it with anything live.

Large

Download free
35 stepsLarge: read it before trusting it with anything live
3Branches: places the flow splits
0Loops or waits
2Services it connects to

The flow

Starts it 2Logic 12Service 21

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

  1. 1When New Telegram MessageTelegram triggerStarts it
  2. 2Schedule Daily Compliance CheckSchedule triggerStarts it
  3. 3Route by Message TypeSwitchLogic
  4. 4Fetch Pending Onboarding RecordsNotionService
  5. 5Set Employee FieldsSetLogic
  6. 6Download Document from TelegramTelegramService
  7. 7Find Policy Page in NotionNotionService
  8. 8Send Help MessageTelegramService
  9. 9Filter Overdue Records (48hrs)FilterLogic
  10. 10Find Existing Record in NotionNotionService
  11. 11Check Document File TypeIfLogic
  12. 12Update Notion Policy StatusNotionService
  13. 13Send Reminder to EmployeeTelegramService
  14. 14Alert Manager of Overdue DocsTelegramService
  15. 15Normalize Existing Record CheckCodeLogic
  16. 16Extract Text from PDFExtract From FileService
  17. 17Convert Doc to Base64CodeLogic
  18. 18Send Shift ScheduleTelegramService
  19. 19Check If Returning EmployeeIfLogic
  20. 20Prepare Text for DeepSeek ExtractionCodeLogic
  21. 21Post to DeepSeek APIHttp RequestService
  22. 22Notify Manager of ProgressTelegramService
  23. 23Send Welcome Back TelegramTelegramService
  24. 24Create Notion Onboarding RecordNotionService
  25. 25Parse DeepSeek ResponseCodeLogic
  26. 26Send Welcome and ChecklistTelegramService
  27. 27Find Notion Page Using ChatIdNotionService
  28. 28Update Notion Status to SubmittedNotionService
  29. 29Create File Upload RequestCodeLogic
  30. 30Send Doc Received ConfirmationTelegramService
  31. 31Post File Upload to NotionHttp RequestService
  32. 32Attach Binary Data for UploadCodeLogic
  33. 33Post File Content to NotionHttp RequestService
  34. 34Build Notion Attach BlockCodeLogic
  35. 35Attach File Block to NotionHttp RequestService

How it's built

Starts on
An incoming Telegram message
Steps
35, with 3 branches
Size
Large: read it before trusting it with anything live
Connects to
Notion, Telegram
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account, plus your own Notion 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?

Take your time. At 35 steps it is large: read it before trusting it with anything live.

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 35 steps before you point it at anything that matters.