Compliance Scan Reporter

ComplianceAWS API - S3JiraSlack

This Flow turns raw compliance-scan output into action the moment a scan completes. A scan tool posts its results to the Flow's webhook, which acknowledges immediately and classifies every finding by severity. Critical findings alert the compliance Slack channel, each critical or high finding gets its own Jira remediation ticket with the full context (tool, target, resource, suggested remediation), and the raw report is archived to S3 for the audit trail. If any of the reporting steps fail, the error is posted to the same Slack channel, so a scan never disappears silently.

The webhook accepts a JSON body with tool, scanId, target, completedAt, and a findings array of {id, title, severity, resource, description, remediation}.

After importing, connect the Flow to your systems: point your scan tool at the /scan-results endpoint, set the Jira project key on the remediation ticket block, the S3 bucket and region on the archive block, and a SLACK_CHANNEL_ID secret with the channel to post to.

HTTP (built-in)Endpoint

Scan Results Webhook

Business logic (built-in)Transform

Classify Findings

Business logic (built-in)Condition

Critical Findings?

Collections (built-in)Explode

Each Remediation Item

Errors (built-in)Handle Error

Catch Reporter Errors

AWS API - S3Put Object

Archive Scan Report

SlackSend Text Message

Post Critical Alert

JiraCreate Issue

Create Remediation Ticket

SlackSend Text Message

Post Reporter Failure