Skip to Workflow Atlas
Playbook AtlasWorkflow Atlas
Workflow blueprintBrowse workflows
Event-Driven AutomationIntermediate

Qualys Scan and Report Automation

Qualys Scan and Report Automation is a 13-node automation blueprint connecting Qualys, Slack. Inspect its trigger, execution graph, branches, and implementation requirements.

QualysSlack

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.

13

Nodes

12

Links

1

Run groups

Connected tools

2 integrations

  • Qualys
  • Slack

Canvas controls

Fit wide systems, then zoom into any run group.

Qualys Scan and Report Automation execution lanes1 run groups containing 13 workflow nodes and 12 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.Webhook. trigger node, webhook. 0 incoming and 1 outgoing connections.STARTWebhookTRIGGERWEBHOOK0 IN / 1 OUTParse Webhook. transform node, set. 1 incoming and 1 outgoing connections.STEP 02Parse WebhookTRANSFORMSET1 IN / 1 OUTRoute Message. decision node, switch. 1 incoming and 3 outgoing connections.STEP 03Route MessageDECISIONSWITCH1 IN / 3 OUTRespond to Slack Webhook - Vulnerability. Slack node, respondToWebhook. 1 incoming and 1 outgoing connections.STEP 04Respond to Slack Webhook …SLACKRESPONDTOWEBHOOK1 IN / 1 OUTRespond to Slack Webhook - Report. Slack node, respondToWebhook. 1 incoming and 1 outgoing connections.STEP 04Respond to Slack Webhook …SLACKRESPONDTOWEBHOOK1 IN / 1 OUTClose Modal Popup. trigger node, respondToWebhook. 1 incoming and 1 outgoing connections.STEP 04Close Modal PopupTRIGGERRESPONDTOWEBHOOK1 IN / 1 OUTVuln Scan Modal. integration node, httpRequest. 1 incoming and 0 outgoing connections.STEP 05Vuln Scan ModalINTEGRATIONHTTPREQUEST1 IN / 0 OUTScan Report Task Modal. integration node, httpRequest. 1 incoming and 0 outgoing connections.STEP 05Scan Report Task ModalINTEGRATIONHTTPREQUEST1 IN / 0 OUTRoute Submission. decision node, switch. 1 incoming and 2 outgoing connections.STEP 05Route SubmissionDECISIONSWITCH1 IN / 2 OUTRequired Scan Variables. transform node, set. 1 incoming and 1 outgoing connections.STEP 06Required Scan VariablesTRANSFORMSET1 IN / 1 OUTRequired Report Variables. transform node, set. 1 incoming and 1 outgoing connections.STEP 06Required Report VariablesTRANSFORMSET1 IN / 1 OUTQualys Start Vulnerability Scan. integration node, executeWorkflow. 1 incoming and 0 outgoing connections.OUTCOMEQualys Start Vulnerabilit…INTEGRATIONEXECUTEWORKFLOW1 IN / 0 OUTQualys Create Report. integration node, executeWorkflow. 1 incoming and 0 outgoing connections.OUTCOMEQualys Create ReportINTEGRATIONEXECUTEWORKFLOW1 IN / 0 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.13 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

Respond to Slack Webhook - Vul…

12 Execution Links

  1. Start

    Webhook

    Trigger

  2. Step 2

    Parse Webhook

    Transform

  3. Step 3

    Route Message

    Decision

  4. Step 4

    Respond to Slack Webhook - Vulnerability

    Trigger

    Respond to Slack Webhook - Report

    Trigger

    Close Modal Popup

    Trigger

  5. Step 5

    Vuln Scan Modal

    Integration

    Scan Report Task Modal

    Integration

    Route Submission

    Decision

  6. Step 6

    Required Scan Variables

    Transform

    Required Report Variables

    Transform

  7. Outcome

    Qualys Start Vulnerability Scan

    Integration

    Qualys Create Report

    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