OpenRuna
Sign in
← Workflows

Weekly_Shodan_Query___Report_Accidents__no_function_node_

15 nodes · httpRequest, itemLists, filter, html, markdown, splitInBatches

Engine
n8n
Nodes
15
Trigger
scheduled/triggered
Source file
1751_Filter_Schedule_Automation_Scheduled.json

Workflow flow

IntegrationsHTTPItemListsFilterHtmlMarkdownSplitInBatchesScheduleTheHiveSet
100%
TRIGGER

Every Monday

Schedule

Get watched IPs & Ports

HTTP

For each IP

SplitInBatches

Scan each IP

HTTP

Split out services

ItemLists

Unexpected port?

Filter

Set data to post for each port

Set

Convert to table

Html

Convert to Markdown

Markdown

Create TheHive alert

TheHive

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

Browse by integration

httpRequestitemListsfilterhtmlmarkdownsplitInBatchesscheduletheHive
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

Weekly_Shodan_Query___Report_Accidents__no_function_node_ is a free n8n workflow on OpenRuna — 15 nodes connecting httpRequest, itemLists, filter, html, markdown, splitInBatches, schedule, theHive. Download the JSON, view the flow diagram, and import it into your n8n instance.

What this workflow does

This n8n workflow, "Weekly_Shodan_Query___Report_Accidents__no_function_node_", wires together httpRequest, itemLists, filter, html, markdown, splitInBatches, schedule, theHive in 15 nodes. 15 nodes · httpRequest, itemLists, filter, html, markdown, splitInBatches Execution begins at the scheduled/triggered trigger and flows through the 15 configured nodes. 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 15-node flow from scratch.
  • Benchmark it against your current httpRequest integration to spot missing steps or redundant nodes.
  • Import "Weekly_Shodan_Query___Report_Accidents__no_function_node_" into n8n, reconnect credentials for httpRequest, itemLists, filter, html, markdown, splitInBatches, schedule, theHive, and run the same automation in your own workspace.
  • Use it as a starting template when wiring httpRequest, itemLists, filter, html, markdown, splitInBatches, schedule, theHive — adjust node parameters to your accounts and record IDs.

Example output

Imported into n8n, "Weekly_Shodan_Query___Report_Accidents__no_function_node_" exposes 15 configured nodes. Trigger type: scheduled/triggered. Integrations: httpRequest, itemLists, filter, html, markdown, splitInBatches, schedule, theHive. Set your credentials on the httpRequest node, then verify each downstream node picks them up. 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 "Weekly_Shodan_Query___Report_Accidents__no_function_node_" 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, itemLists, filter, html, markdown, splitInBatches, schedule, theHive. Handy for onboarding teammates new to n8n.

Cursor

In Cursor, ask Agent mode to parameterise "Weekly_Shodan_Query___Report_Accidents__no_function_node_" — extract httpRequest IDs and secrets into environment variables without changing the 15-node structure.

Frequently asked questions

How do I import "Weekly_Shodan_Query___Report_Accidents__no_function_node_" 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 "Weekly_Shodan_Query___Report_Accidents__no_function_node_" use?
It uses: httpRequest, itemLists, filter, html, markdown, splitInBatches, schedule, theHive. The flow diagram above shows how each service connects across the 15 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 itemLists credentials in n8n after import.
What trigger type does "Weekly_Shodan_Query___Report_Accidents__no_function_node_" 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 "Weekly_Shodan_Query___Report_Accidents__no_function_node_" 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, itemLists, filter, html, markdown, splitInBatches, schedule, theHive.

Related resources