OpenRuna
Sign in
← Workflows

[1/3 - anomaly detection] [1/2 - KNN classification] Batch upload dataset to Qdrant (crops dataset)

25 nodes · manual, googleCloudStorage, httpRequest, filter

Engine
n8n
Nodes
25
Trigger
scheduled/triggered
Source file
0341_Code_Filter_Import_Webhook.json

Workflow flow

IntegrationsManualGoogleCloudStorageHTTPFilterSetCodeIF
100%
TRIGGER

When clicking ‘Test workflow’

Manual

Qdrant cluster variables

Set

Check Qdrant Collection Existence

HTTP

If collection exists

IF

Create Qdrant Collection

HTTP

Payload index on crop_name

HTTP

Google Cloud Storage

GoogleCloudStorage

Get fields for Qdrant

Set

Filtering out tomato to test anomalies

Filter

Split in batches, generate uuids for Qdrant points

Code

Batches in the API's format

Set

Embed crop image

HTTP

Batch Upload to Qdrant

HTTP

13 steps · flows top to bottom, branches left to right

Browse by integration

manualgoogleCloudStoragehttpRequestfilter
Browse all integrations →
Download n8n JSONDownload sanitized JSONDownload flow graph

Import into n8n

  1. Download the n8n JSON file (full or sanitized).
  2. In n8n: Workflows → Import from file.
  3. Open each node and reconnect credentials to your accounts.
  4. Test with manual execution before enabling triggers.

Sanitized JSON removes credential IDs — safer for sharing. Flow graph JSON is OpenRuna's lightweight format for diagrams and other tools, not n8n import.

View source corpus ↗

Overview

[1/3 - anomaly detection] [1/2 - KNN classification] Batch upload dataset to Qdrant (crops dataset) is a free n8n workflow on OpenRuna — 25 nodes connecting manual, googleCloudStorage, httpRequest, filter. Download the JSON, view the flow diagram, and import it into your n8n instance.

What this workflow does

"[1/3 - anomaly detection] [1/2 - KNN classification] Batch upload dataset to Qdrant (crops dataset)" automates a manual-to-googleCloudStorage flow in n8n across 25 nodes. 25 nodes · manual, googleCloudStorage, httpRequest, filter A scheduled/triggered entry point kicks it off, and each node passes data to the next until the run completes. On OpenRuna you get the visual graph, the integration list, and a downloadable JSON ready to import into n8n. Use it to learn integration patterns, fork it for your own use case, or deploy it quickly after reconnecting credentials.

Use cases

  • Share it with your team as a documented reference for scheduled/triggered automations in the manual stack.
  • Study how data moves from manual to googleCloudStorage before building your own variant.
  • Use it as a starting template when wiring manual, googleCloudStorage, httpRequest, filter — adjust node parameters to your accounts and record IDs.
  • Import "[1/3 - anomaly detection] [1/2 - KNN classification] Batch upload dataset to Qdrant (crops dataset)" into n8n, reconnect credentials for manual, googleCloudStorage, httpRequest, filter, and run the same automation in your own workspace.

Example output

Imported into n8n, "[1/3 - anomaly detection] [1/2 - KNN classification] Batch upload dataset to Qdrant (crops dataset)" exposes 25 configured nodes. Trigger type: scheduled/triggered. Integrations: manual, googleCloudStorage, httpRequest, filter. Reconnect the manual credential first, then walk the remaining nodes top to bottom. Run it once in test mode to verify any branch logic (Switch/IF nodes) before enabling production triggers.

Tips by platform

Claude

Paste the exported JSON for "[1/3 - anomaly detection] [1/2 - KNN classification] Batch upload dataset to Qdrant (crops dataset)" into Claude and ask it to explain each of the 25 nodes. Claude is good at suggesting credential mappings for manual, googleCloudStorage, httpRequest, filter, plus error-handling and idempotency improvements before you run it in production.

ChatGPT

Have ChatGPT generate a checklist for adapting "[1/3 - anomaly detection] [1/2 - KNN classification] Batch upload dataset to Qdrant (crops dataset)" to your accounts — which manual, googleCloudStorage, httpRequest, filter credentials to create and which node parameters to change first.

Cursor

Open the downloaded JSON in Cursor and use Agent mode to refactor hard-coded URLs into env vars, or to generate tests for any Code nodes. Keep the OpenRuna flow diagram open so you do not break connection order across the 25 nodes.

Frequently asked questions

How do I import "[1/3 - anomaly detection] [1/2 - KNN classification] Batch upload dataset to Qdrant (crops dataset)" into n8n?
Click Download n8n JSON on this page, then in n8n choose Workflows → Import from file and select the downloaded file. Reconnect credentials on each node — the export carries credential IDs from the original author's instance, not working secrets.
Which integrations does "[1/3 - anomaly detection] [1/2 - KNN classification] Batch upload dataset to Qdrant (crops dataset)" use?
It uses: manual, googleCloudStorage, httpRequest, filter. The flow diagram above shows how each service connects across the 25 nodes. Filter OpenRuna by integration to find related workflows and tools.
Can I import a sanitized export without credentials?
Yes. Use "Download sanitized JSON" to strip credential references before sharing internally. You will still add your own manual and googleCloudStorage credentials in n8n after import.
What trigger type does "[1/3 - anomaly detection] [1/2 - KNN classification] Batch upload dataset to Qdrant (crops dataset)" use?
Trigger type: scheduled/triggered. After import, confirm the trigger node (webhook, schedule, or app event) matches your environment, then activate the workflow when you are ready to run it.
Is "[1/3 - anomaly detection] [1/2 - KNN classification] Batch upload dataset to Qdrant (crops dataset)" free to use?
OpenRuna catalogs community n8n workflows under open licenses. Check the source corpus link for the original license; commercial use may require verifying the third-party API terms for manual, googleCloudStorage, httpRequest, filter.

Related resources