Orchestrate security vulnerability remediation with Port, OpenAI, Jira and Slack
Needs changesWhat this workflow does
This workflow has 12 nodes and runs when an HTTP POST request hits its webhook URL. Along the way it connects Jira Software, Slack and CUSTOM (community). It also calls api.getport.io over HTTP.
How it runs
Trigger: When an HTTP POST request hits its webhook URL.
- Get Context From Port (Port Api Ai): invoke agent
- OpenAI: work with chat
- Check Severity Level (Switch): routes items into 3 branches
- Create Critical Jira Ticket (Jira Software): uses Jira Software
- Create High Jira Ticket (Jira Software): uses Jira Software
- Create Medium/Low Jira Ticket (Jira Software): uses Jira Software
- Is Auto-Fixable? (If): checks a condition and branches into true / false
- Alert High to Slack (Slack): uses Slack
- Trigger Fix via Port AI Agent (HTTP Request): calls api.getport.io (POST)
- Alert Critical (Manual Fix) (Slack): uses Slack
…plus 1 more step. See the full node list below.
Services it uses
HTTP calls to: api.getport.io
Before you upgrade to n8n 3.0
1 thing in this workflow is removed in n8n 3.0. Fix it before you upgrade:
- OpenAI (legacy) in OpenAI Remediation Plan: replace with OpenAI node (AI section).
| Removed in 3.0 | Replace with |
|---|---|
| OpenAI (legacy) OpenAI Remediation Plan | OpenAI node (AI section) |
Nodes used (8)
- Webhook
n8n-nodes-base.webhook - Port Api Ai
CUSTOM.portApiAi - OpenAI
n8n-nodes-base.openAi - Switch
n8n-nodes-base.switch - Jira Software
n8n-nodes-base.jira - If
n8n-nodes-base.if - HTTP Request
n8n-nodes-base.httpRequest - Slack
n8n-nodes-base.slack
From the author
Complete security workflow from vulnerability detection to automated remediation, with severity-based routing and full organizational context from Port's catalog. This template provides end-to-end lifecycle management including automatic Jira ticket creation…