Skip to Workflow Atlas
Playbook AtlasWorkflow Atlas
Workflow blueprintBrowse workflows
ETL PipelineIntermediate

Weekly Shodan IP Scan and Alert

Weekly Shodan IP Scan and Alert is a 10-node automation blueprint connecting Shodan, TheHive. Inspect its trigger, execution graph, branches, and implementation requirements.

ShodanTheHive

Interactive system map

Follow the runtime. Inspect what supports it.

Solid horizontal paths show main-channel execution. Violet dependencies sit beneath the exact step they configure or empower.

10

Nodes

10

Links

1

Run groups

Connected tools

2 integrations

  • Shodan
  • TheHive

Canvas controls

Fit wide systems, then zoom into any run group.

Weekly Shodan IP Scan and Alert execution lanes1 run groups containing 10 workflow nodes and 10 visible links. Solid horizontal lines are main-channel runtime links. Violet dashed lines connect typed dependencies beneath the runtime step they support. Focus any node to inspect its immediate path.Every Monday. trigger node, scheduleTrigger. 0 incoming and 1 outgoing connections.STARTEvery MondayTRIGGERSCHEDULETRIGGER0 IN / 1 OUTGet watched IPs & Ports. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 02Get watched IPs & PortsINTEGRATIONHTTPREQUEST1 IN / 1 OUTFor each IP. integration node, splitInBatches. 2 incoming and 1 outgoing connections.STEP 03For each IPINTEGRATIONSPLITINBATCHES2 IN / 1 OUTScan each IP. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 04Scan each IPINTEGRATIONHTTPREQUEST1 IN / 1 OUTSplit out services. transform node, itemLists. 1 incoming and 1 outgoing connections.STEP 05Split out servicesTRANSFORMITEMLISTS1 IN / 1 OUTUnexpected port?. decision node, filter. 1 incoming and 1 outgoing connections.STEP 06Unexpected port?DECISIONFILTER1 IN / 1 OUTSet data to post for each port. transform node, set. 1 incoming and 1 outgoing connections.STEP 07Set data to post for each…TRANSFORMSET1 IN / 1 OUTConvert to table. integration node, html. 1 incoming and 1 outgoing connections.STEP 08Convert to tableINTEGRATIONHTML1 IN / 1 OUTConvert to Markdown. integration node, markdown. 1 incoming and 1 outgoing connections.STEP 09Convert to MarkdownINTEGRATIONMARKDOWN1 IN / 1 OUTCreate TheHive alert. integration node, theHive. 1 incoming and 1 outgoing connections.OUTCOMECreate TheHive alertINTEGRATIONTHEHIVE1 IN / 1 OUT

Signal inspector

Focus, hover, or select a step to isolate its runtime and support links.

Main-channel runtimeTyped dependencytriggeraidecisiontransformintegration
Scroll horizontally to follow every connected flow.10 connected nodesEnter or click to lock · Escape to clear

Runtime breakdown

Read the execution spine before its dependencies.

Each run group separates main-channel steps from the models, tools, retrievers, and data services that support them. Start and outcome labels apply only to runtime nodes.

01

Run Group

Every Monday

10 Execution Links

  1. Start

    Every Monday

    Trigger

  2. Step 2

    Get watched IPs & Ports

    Integration

  3. Step 3

    For each IP

    Integration

  4. Step 4

    Scan each IP

    Integration

  5. Step 5

    Split out services

    Transform

  6. Step 6

    Unexpected port?

    Decision

  7. Step 7

    Set data to post for each port

    Transform

  8. Step 8

    Convert to table

    Integration

  9. Step 9

    Convert to Markdown

    Integration

  10. Outcome

    Create TheHive alert

    Integration

Turn the map into a plan

Adapt this blueprint to your company.

Bring the system shape into a workspace, then define the production controls, data boundaries, owners, and delivery sequence around your context.

Create a build planReturn to the atlas