OpenRuna
Sign in
← Workflows

[3/3] Anomaly detection tool (crops dataset)

17 nodes · httpRequest, executeWorkflow

Engine
n8n
Nodes
17
Trigger
scheduled/triggered
Source file
1732_HTTP_Executeworkflow_Automation_Webhook.json

Workflow flow

IntegrationsHTTPExecuteWorkflowCodeSet
100%
TRIGGER

Execute Workflow Trigger

ExecuteWorkflow

Image URL hardcode

Set

Variables for medoids

Set

Total Points in Collection

HTTP

Each Crop Counts

HTTP

Info About Crop Labeled Clusters

Set

Embed image

HTTP

Get similarity of medoids

HTTP

Compare scores

Code

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

Browse by integration

httpRequestexecuteWorkflow
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

[3/3] Anomaly detection tool (crops dataset) (17-node n8n automation, httpRequest, executeWorkflow) is free on OpenRuna — view the graph and export the JSON to import into n8n.

What this workflow does

Built in n8n, "[3/3] Anomaly detection tool (crops dataset)" chains 17 nodes to move data between httpRequest, executeWorkflow. 17 nodes · httpRequest, executeWorkflow 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

  • Fork it to add error handling, retries, or a notification step without designing the 17-node flow from scratch.
  • Benchmark it against your current httpRequest integration to spot missing steps or redundant nodes.
  • Study how data moves from httpRequest to executeWorkflow before building your own variant.
  • Share it with your team as a documented reference for scheduled/triggered automations in the httpRequest stack.

Example output

Imported into n8n, "[3/3] Anomaly detection tool (crops dataset)" exposes 17 configured nodes. Trigger type: scheduled/triggered. Integrations: httpRequest, executeWorkflow. Open each node after import to map credentials to your own httpRequest and executeWorkflow accounts. 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 "[3/3] Anomaly detection tool (crops dataset)" JSON into a plain-English runbook, node by node. It can flag where httpRequest 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 httpRequest, executeWorkflow. Handy for onboarding teammates new to n8n.

Cursor

In Cursor, ask Agent mode to parameterise "[3/3] Anomaly detection tool (crops dataset)" — extract httpRequest IDs and secrets into environment variables without changing the 17-node structure.

Frequently asked questions

How do I import "[3/3] Anomaly detection tool (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 "[3/3] Anomaly detection tool (crops dataset)" use?
It uses: httpRequest, executeWorkflow. The flow diagram above shows how each service connects across the 17 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 httpRequest and executeWorkflow credentials in n8n after import.
What trigger type does "[3/3] Anomaly detection tool (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 "[3/3] Anomaly detection tool (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 httpRequest, executeWorkflow.

Related resources