The flow
Starts it 1Model 3Logic 2Service 4
The steps in the order they run, from what starts it.
- 1Embeddings Azure OpenAIEmbeddings Azure Open AiModel
- 2Default Data Loader1Document Default Data LoaderModel
- 3Knowledge Base Updated TriggerGoogle Drive triggerStarts it
- 4Insert Data to StoreVector Store In MemoryModel
- 5Download Knowledge DocumentGoogle DriveService
- 6Parse Document via LlamaIndexHttp RequestService
- 7Monitor Document ProcessingHttp RequestService
- 8Check Parsing Completion1IfLogic
- 9Retrieve Parsed ContentHttp RequestService
- 10Wait Before Status RecheckWaitLogic
How it's built
- Starts on
- An event in a connected app
- Steps
- 10, with 1 branch, 1 loop or waits
- Size
- Medium: a working afternoon
- Connects to
- Google Drive, in-memory vectors
- Model
- None. This is plumbing, not judgement
- 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 Google Drive and in-memory vectors accounts. 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?
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. 10 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.
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 10 steps before you point it at anything that matters.