The flow
Starts it 1Logic 6Service 6
The steps in the order they run, from what starts it.
- 1When clicking ‘Test workflow’Manual triggerStarts it
- 2Qdrant cluster variablesSetLogic
- 3Check Qdrant Collection ExistenceHttp RequestService
- 4If collection existsIfLogic
- 5Google Cloud StorageGoogle Cloud StorageService
- 6Create Qdrant CollectionHttp RequestService
- 7Get fields for QdrantSetLogic
- 8Payload index on crop_nameHttp RequestService
- 9Filtering out tomato to test anomaliesFilterLogic
- 10Split in batches, generate uuids for Qdrant pointsCodeLogic
- 11Batches in the API's formatSetLogic
- 12Embed crop imageHttp RequestService
- 13Batch Upload to QdrantHttp RequestService
How it's built
- Starts on
- An event in a connected app
- Steps
- 13, with 1 branch
- Size
- Medium: a working afternoon
- Connects to
- Google Cloud Storage
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Google Cloud Storage account. 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. 13 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 13 steps before you point it at anything that matters.