Dependency update risk analysis with GPT-4o, Slack, Jira & Google Sheets
Ready for 3.0What this workflow does
This AI workflow has 12 nodes and runs manually, when you click “Execute workflow”. Along the way it connects Jira Software, Google Sheets, Slack and Azure OpenAI Chat Model.
How it runs
Trigger: Manually, when you click “Execute workflow”.
- Fetch All Active Jira Issues (Jira Software): get many
- Validate Jira Query Response (If): checks a condition and branches into true / false
- Identify Dependency Update Issues (Filter): keeps only the items that match a condition
- Log Jira Query Failures to Error Sheet (Google Sheets): append
- Extract Relevant Issue Metadata (Edit Fields (Set)): sets 7 fields: key, fields.summary, fields.status…
- Alert DevOps Team in Slack (Slack): uses Slack
- AI-Powered Risk Assessment Analyzer (AI Agent): runs an AI agent, with model: GPT-4o Language Model Configuration
- Parse AI Response to Structured Data (Code): runs custom JavaScript code
- Post AI Risk Assessment to Jira Ticket (Jira Software): work with issue comment
- Log Dependency Updates to Tracking Dashboard (Google Sheets): append
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 (10)
- Manual Trigger
n8n-nodes-base.manualTrigger - Jira Software
n8n-nodes-base.jira - If
n8n-nodes-base.if - Google Sheets
n8n-nodes-base.googleSheets - Filter
n8n-nodes-base.filter - Edit Fields (Set)
n8n-nodes-base.set - Slack
n8n-nodes-base.slack - AI Agent
@n8n/n8n-nodes-langchain.agent - Azure OpenAI Chat Model
@n8n/n8n-nodes-langchain.lmChatAzureOpenAi - Code
n8n-nodes-base.code
From the author
📘 Description This workflow automates dependency update risk analysis and reporting using Jira, GPT-4o, Slack, and Google Sheets. It continuously monitors Jira for new package or dependency update tickets, uses AI to assess their risk levels (Low, Medium,…