Vector database as a big data analysis tool for AI agents [2/3 - anomaly]
Ready for 3.0What this workflow does
This workflow has 26 nodes and runs manually, when you click “Execute workflow”. It uses only n8n's built-in nodes. It also calls api.voyageai.com over HTTP.
How it runs
Trigger: Manually, when you click “Execute workflow”.
- Qdrant cluster variables (Edit Fields (Set)): sets 2 fields: qdrantCloudURL, collectionName
- Medoids Variables (Edit Fields (Set)): sets 1 field: furthestFromCenter
- Text Medoids Variables (Edit Fields (Set)): sets 1 field: furthestFromCenter
- Total Points in Collection (HTTP Request): calls an HTTP API (POST)
- Textual (visual) crop descriptions (Edit Fields (Set)): sets or maps fields
- Crop Counts (HTTP Request): calls an HTTP API (POST)
- Split Out: splits a list into separate items
- Info About Crop Clusters (Edit Fields (Set)): sets 2 fields: maxClusterSize, cropNames
- Merge: merges the data from its input branches
- Split Out: splits a list into separate items
…plus 15 more steps. See the full node list below.
HTTP calls to: api.voyageai.com
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (6)
- Manual Trigger
n8n-nodes-base.manualTrigger - HTTP Request
n8n-nodes-base.httpRequest - Code
n8n-nodes-base.code - Edit Fields (Set)
n8n-nodes-base.set - Split Out
n8n-nodes-base.splitOut - Merge
n8n-nodes-base.merge
From the author
Vector Database as a Big Data Analysis Tool for AI Agents Workflows from the webinar "Build production-ready AI Agents with Qdrant and n8n". This series of workflows shows how to build big data analysis tools for production-ready AI agents with the help of…