# Vector database as a big data analysis tool: n8n workflow

> Started by an event in a connected app, and works across Google Cloud Storage. 13 steps, 1 branch: a working afternoon to understand properly.

Source: https://millionrounds.com/workflow/vector-database-as-a-big-data-analysis-tool (Millionrounds; every figure on the page links to its filing or article)

[Automation library](https://millionrounds.com/workflows) · [Research and reporting](https://millionrounds.com/workflows?category=Research+and+reporting#library)

# Vector database as a big data analysis tool

Started by an event in a connected app, and works across Google Cloud Storage. 13 steps, 1 branch: a working afternoon to understand properly.

Medium

[Download free](https://millionrounds.com/login?next=%2Fapp%2Fworkflow%2Fvector-database-as-a-big-data-analysis-tool)

**13 steps** Medium: a working afternoon

**1** Branch: places the flow splits

**0** Loops or waits

**1** Service it connects to

## The flow

Starts it 1 Logic 6 Service 6

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

- 1 **When clicking ‘Test workflow’** Manual trigger *Starts it*
- 2 **Qdrant cluster variables** Set *Logic*
- 3 **Check Qdrant Collection Existence** Http Request *Service*
- 4 **If collection exists** If *Logic*
- 5 **Google Cloud Storage** Google Cloud Storage *Service*
- 6 **Create Qdrant Collection** Http Request *Service*
- 7 **Get fields for Qdrant** Set *Logic*
- 8 **Payload index on crop_name** Http Request *Service*
- 9 **Filtering out tomato to test anomalies** Filter *Logic*
- 10 **Split in batches, generate uuids for Qdrant points** Code *Logic*
- 11 **Batches in the API's format** Set *Logic*
- 12 **Embed crop image** Http Request *Service*
- 13 **Batch Upload to Qdrant** Http Request *Service*

## 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.

**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 13 steps before you point it at anything that matters.

## Run it in n8n

- **Create your n8n account** Free to start. n8n is where the workflow runs. [Create an n8n account ↗](https://millionrounds.com/n8n)
- **Download the workflow** Free with a Millionrounds account. [Download free](https://millionrounds.com/login?next=%2Fapp%2Fworkflow%2Fvector-database-as-a-big-data-analysis-tool)
- **Paste it into n8n** Open a new workflow in n8n and paste. Then connect your own accounts.

Stored with the author's traces removed: canvas notes, instance identifiers, saved credential names and any live document they had left behind.

## Connects to

Each opens the other workflows that use it.

[Google Cloud Storage](https://millionrounds.com/workflows?service=Google+Cloud+Storage#library)