Qualys vulnerability trigger scan subWorkflow
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 19 nodes and runs manually, when you click “Execute workflow” (plus 1 other trigger). Along the way it connects Slack.
How it runs
Trigger: Manually, when you click “Execute workflow” (plus 1 other trigger).
- Demo Data (Edit Fields (Set)): sets 3 fields: option_title, scan_title, asset_groups
- Global Variables & Slack Channel (Edit Fields (Set)): sets 2 fields: slackChannelId, platformurl
- Merge: merges the data from its input branches
- Post Receipt (Slack): uses Slack
- Start VM Scan in Qualys (HTTP Request): calls an HTTP API (POST)
- Save receipt message timestamp (Edit Fields (Set)): sets 1 field: ts
- Convert XML to JSON (XML): converts between XML and JSON
- Confirm Waiting (Slack): update
- Merge: merges the data from its input branches
- Loop Over Items (Loop Over Items (Split in Batches)): loops over the items in batches
…plus 6 more steps. See the full node list below.
Services it uses
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 (11)
- HTTP Request
n8n-nodes-base.httpRequest - XML
n8n-nodes-base.xml - Loop Over Items (Split in Batches)
n8n-nodes-base.splitInBatches - Wait
n8n-nodes-base.wait - If
n8n-nodes-base.if - Execute Workflow Trigger
n8n-nodes-base.executeWorkflowTrigger - Slack
n8n-nodes-base.slack - Edit Fields (Set)
n8n-nodes-base.set - Merge
n8n-nodes-base.merge - Manual Trigger
n8n-nodes-base.manualTrigger - No Operation, do nothing
n8n-nodes-base.noOp
From the author
This workflow is triggered by a parent workflow initiated via a Slack shortcut. Upon activation, it collects input from a modal window in Slack and initiates a vulnerability scan using the Qualys API. Key Features - Trigger: Launched by a parent workflow…