The flow
Starts it 1Model 2Logic 7Service 6
The steps in the order they run, from what starts it.
- 1Max Trigger1Max triggerStarts it
- 2Simple Memory1Memory Buffer WindowModel
- 3GigaChat Model1Lm Giga ChatService
- 4Check UserIfLogic
- 5AI Agent1AgentModel
- 6Text/AttachmentSwitchLogic
- 7Access DeniedMaxService
- 8Send MessageMaxService
- 9Download AttachmentHttp RequestService
- 10Text to PromptSetLogic
- 11Attachment RouterSwitchLogic
- 12CombineMergeLogic
- 13Get Access TokenHttp RequestService
- 14Merge1MergeLogic
- 15Get ResponseHttp RequestService
- 16Voice to PromptSetLogic
How it's built
- Starts on
- An event in a connected app
- Steps
- 16, with 3 branches
- Size
- Medium: a working afternoon
- Connects to
- Nothing by connector; it calls services over plain HTTP
- Model
- A language model, family not declared
- Retrieval
- Answers are drawn from documents you supply, not from the model alone
Questions
What does it need to run?
An n8n account, and a key for a language model. You connect your own accounts after importing it; none are included.
What starts it?
It starts on an event in a connected app.
Does it use AI?
Yes. It calls a language model. 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?
Plan an afternoon. 16 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 itNothing 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 16 steps before you point it at anything that matters.