Automation library · Chat assistants

AI advanced automation agent with Azure OpenAI and Gmail

Started by an incoming Telegram message, and works across Gmail and Telegram. It puts Azure OpenAI behind a retrieval step, so answers are drawn from documents you supply rather than from the model alone. 45 steps, 4 branches: large, and worth reading before you trust it with anything live.

LargeCalls a model: Azure OpenAIRetrieval

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

The flow

Starts it 4Model 9Logic 10Service 22

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

  1. 1Azure OpenAI Chat ModelLm Chat Azure Open AiModel
  2. 2Firecrwal scrape list toolsMcp Client ToolService
  3. 3Firecrawl scrape executeMcp Client ToolService
  4. 4Brave search list toolsMcp Client ToolService
  5. 5Github tool listMcp Client ToolService
  6. 6Github tools executeMcp Client ToolService
  7. 7Brave tool executeMcp Client ToolService
  8. 8Telegram TriggerTelegram triggerStarts it
  9. 9Tweet on TwitterTwitter ToolService
  10. 10Delete A tweetTwitter ToolService
  11. 11Simple MemoryMemory Buffer WindowModel
  12. 12WebhookWebhookStarts it
  13. 13Deep ResearchTool Http RequestModel
  14. 14Translator toolTool Http RequestModel
  15. 15When Executed by Another WorkflowExecute Workflow triggerStarts it
  16. 16Send mailGmail ToolService
  17. 17Get all mailsGmail ToolService
  18. 18Email AgentTool WorkflowModel
  19. 19Webhook1WebhookStarts it
  20. 20Image Genertion toolTool Http RequestModel
  21. 21Youtube transcript and summerizeTool Http RequestModel
  22. 22AI AgentAgentModel
  23. 23AI Agent1AgentModel
  24. 24SwitchSwitchLogic
  25. 25HTTP RequestHttp RequestService
  26. 26Switch2SwitchLogic
  27. 27Telegram5TelegramService
  28. 28CodeCodeLogic
  29. 29Telegram3TelegramService
  30. 30Error ResponseSetLogic
  31. 31Code2CodeLogic
  32. 32If1IfLogic
  33. 33HTTP Request1Http RequestService
  34. 34Telegram4TelegramService
  35. 35HTTP Request3Http RequestService
  36. 36TelegramTelegramService
  37. 37Edit FieldsSetLogic
  38. 38Success ResponseSetLogic
  39. 39Code1CodeLogic
  40. 40Telegram7TelegramService
  41. 41Telegram1TelegramService
  42. 42Telegram6TelegramService
  43. 43IfIfLogic
  44. 44Telegram8TelegramService
  45. 45Telegram2TelegramService

How it's built

Starts on
An incoming Telegram message
Steps
45, with 4 branches
Size
Large: read it before trusting it with anything live
Connects to
Gmail, Telegram
Model
Azure OpenAI
Retrieval
Answers are drawn from documents you supply, not from the model alone

Questions

What does it need to run?

An n8n account, plus your own Gmail and Telegram accounts, and a key for Azure OpenAI. 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?

Yes. It calls Azure OpenAI. Its answers draw on documents you give it, not on the model alone. Model calls are billed by the provider, not by n8n.

How long does it take to set up?

Take your time. At 45 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 45 steps before you point it at anything that matters.