OpenRuna
Sign in
← Workflows

[2/3] Set up medoids (2 types) for anomaly detection (crops dataset)

48 nodes · manual, httpRequest, splitOut

Engine
n8n
Nodes
48
Trigger
scheduled/triggered
Source file
1731_Splitout_Code_Automation_Webhook.json

Workflow flow

IntegrationsManualHTTPSplit OutCodeSetMerge
100%
TRIGGER

When clicking ‘Test workflow’

Manual

Qdrant cluster variables

Set

Medoids Variables

Set

Text Medoids Variables

Set

Total Points in Collection

HTTP

Textual (visual) crop descriptions

Set

Split Out1

Split Out

Crop Counts

HTTP

Info About Crop Clusters

Set

Split Out

Split Out

Cluster Distance Matrix

HTTP

Merge

Merge

Scipy Sparse Matrix

Code

Embed text

HTTP

Set medoid id

HTTP

Get Medoid Vector

HTTP

Get Medoid by Text

HTTP

Prepare for Searching Threshold

Set

Set text medoid id

HTTP

Prepare for Searching Threshold1

Set

Searching Score

HTTP

Searching Text Medoid Score

HTTP

Threshold Score

Set

Threshold Score1

Set

Set medoid threshold score

HTTP

Set text medoid threshold score

HTTP

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

Browse by integration

manualhttpRequestsplitOut
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

[2/3] Set up medoids (2 types) for anomaly detection (crops dataset) (48-node n8n automation, manual, httpRequest, splitOut) is free on OpenRuna — view the graph and export the JSON to import into n8n.

What this workflow does

Built in n8n, "[2/3] Set up medoids (2 types) for anomaly detection (crops dataset)" chains 48 nodes to move data between manual, httpRequest, splitOut. 48 nodes · manual, httpRequest, splitOut Execution begins at the scheduled/triggered trigger and flows through the 48 configured nodes. OpenRuna renders the node graph and offers the JSON export so you can import and adapt it in minutes. 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.
  • Import "[2/3] Set up medoids (2 types) for anomaly detection (crops dataset)" into n8n, reconnect credentials for manual, httpRequest, splitOut, and run the same automation in your own workspace.
  • Use it as a starting template when wiring manual, httpRequest, splitOut — adjust node parameters to your accounts and record IDs.
  • Fork it to add error handling, retries, or a notification step without designing the 48-node flow from scratch.

Example output

Imported into n8n, "[2/3] Set up medoids (2 types) for anomaly detection (crops dataset)" exposes 48 configured nodes. Trigger type: scheduled/triggered. Integrations: manual, httpRequest, splitOut. 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

Ask Claude to turn the "[2/3] Set up medoids (2 types) for anomaly detection (crops dataset)" JSON into a plain-English runbook, node by node. It can flag where manual rate limits or missing retries might bite before you go live.

ChatGPT

Drop the workflow JSON or this OpenRuna page URL into ChatGPT and ask for a step-by-step runbook: triggers, branches, and which fields to customise for manual, httpRequest, splitOut. Handy for onboarding teammates new to n8n.

Cursor

In Cursor, ask Agent mode to parameterise "[2/3] Set up medoids (2 types) for anomaly detection (crops dataset)" — extract manual IDs and secrets into environment variables without changing the 48-node structure.

Frequently asked questions

How do I import "[2/3] Set up medoids (2 types) for anomaly detection (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 "[2/3] Set up medoids (2 types) for anomaly detection (crops dataset)" use?
It uses: manual, httpRequest, splitOut. The flow diagram above shows how each service connects across the 48 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 httpRequest credentials in n8n after import.
What trigger type does "[2/3] Set up medoids (2 types) for anomaly detection (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 "[2/3] Set up medoids (2 types) for anomaly detection (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, httpRequest, splitOut.

Related resources