The flow
Starts it 1Model 3Logic 4Service 6
The steps in the order they run, from what starts it.
- 1Embeddings OllamaEmbeddings OllamaModel
- 2Schedule TriggerSchedule triggerStarts it
- 3Default Data LoaderDocument Default Data LoaderModel
- 4Qdrant Vector StoreVector Store QdrantModel
- 5Fetch Latest Commit SHAHttp RequestService
- 6Prepare State PayloadCodeLogic
- 7Fetch Qdrant State SHAHttp RequestService
- 8Write n8n Docs SHAHttp RequestService
- 9Check Commit SHA ChangeCodeLogic
- 10Delete n8n Docs Qdrant Vector StoreHttp RequestService
- 11Fetch n8n Docs TreeHttp RequestService
- 12Parse Doc File ListCodeLogic
- 13Fetch Raw MarkdownHttp RequestService
- 14Markdown Section ChunkerCodeLogic
How it's built
- Starts on
- A clock
- Steps
- 14
- Size
- Medium: a working afternoon
- Connects to
- Qdrant
- 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 Qdrant account. You connect your own accounts after importing it; none are included.
What starts it?
It starts on a clock.
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.
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.