Predict sprint slip risk in Jira with OpenAI via OpenRouter and Slack alerts
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This AI workflow has 14 nodes and runs manually, when you click “Execute workflow” (plus 1 other trigger). Along the way it connects Slack and OpenRouter Chat Model.
How it runs
Trigger: Manually, when you click “Execute workflow” (plus 1 other trigger).
- Config (Edit Fields (Set)): sets 7 fields: JIRA_DOMAIN, JIRA_BOARD_ID, STORY_POINTS_FIELD…
- Fetch Active Sprint (HTTP Request): calls an HTTP API
- Fetch Sprint Issues (HTTP Request): calls an HTTP API
- Compute Sprint Metrics Code (Code): runs custom JavaScript code
- Slip Predictor Agent (AI Agent): runs an AI agent, with model: OpenAI Slip Predictor
- Parse Prediction Code (Code): runs custom JavaScript code
- If: checks a condition and branches into true / false
- Team Notifier Agent (AI Agent): runs an AI agent, with model: OpenAI Team Notifier; 1 tool (Send a message in Slack)
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 - Schedule Trigger
n8n-nodes-base.scheduleTrigger - Edit Fields (Set)
n8n-nodes-base.set - HTTP Request
n8n-nodes-base.httpRequest - Code
n8n-nodes-base.code - If
n8n-nodes-base.if - No Operation, do nothing
n8n-nodes-base.noOp - Slack Tool
n8n-nodes-base.slackTool - AI Agent
@n8n/n8n-nodes-langchain.agent - OpenRouter Chat Model
@n8n/n8n-nodes-langchain.lmChatOpenRouter
From the author
Quick Overview This workflow runs on a weekday morning schedule (or manually) to pull the active Jira sprint and its issues, compute sprint health metrics, use an OpenRouter-hosted OpenAI model to assess slip risk, and post a motivating alert to a Slack…