๐Ÿ”’ Analyze vendor security risk from Jira tickets using Grok, Claude and Slack

โšก 88 views ยท ๐Ÿ”’ SecOps & Security Automation

Description

How it works

When a new vendor ticket is created in Jira, this workflow automatically performs a comprehensive security due-diligence investigation and posts the findings back as a Jira comment plus a Slack notification.

  1. A Jira webhook fires when an issue is created. An AI agent (Grok) extracts the vendor company name, URL, and product from the issue fields.
  2. A Seed Discovery agent (Claude + Perplexity) finds the vendorโ€™s official domains, trust center, privacy policy, and status page URLs โ€” handling domain aliases automatically.
  3. Seven specialized research agents run in parallel, each with a focused persona: Compliance, Data Handling, Privacy & Legal, Security Controls, Availability, Pricing, and Company Intel. All use Perplexity sonar-pro-search for live web research.
  4. A Sanitizer code node strips unpredictable LLM formatting from all 7 outputs.
  5. A Lead Security Analyst agent (Grok) synthesizes all findings into a risk-scored report, generating Jira Wiki Markup and Slack Block Kit JSON simultaneously.
  6. The report is posted as a comment on the original Jira ticket, and a rich Slack notification with a โ€œView Report in Jiraโ€ button is sent to your security channel.

Set up steps

๐Ÿ”— Nodes Used

Slack, Webhook, Jira Software, AI Agent, OpenRouter Chat Model, AI Agent Tool

๐Ÿ“ฅ Import

Download workflow.json and import into n8n: Workflow menu โ†’ Import from File

๐Ÿ“– Importing guide ยท ๐Ÿ”‘ Credential setup