Turn TeamRetro standup blockers into Jira issues with OpenAI and Slack
UnknownWhat this workflow does
This AI workflow has 18 nodes and runs on Team Retro events (standup.completed). Along the way it connects OpenAI Chat Model, Jira Software, Slack and Teamretro (community).
How it runs
Trigger: On Team Retro events (standup.completed).
- Skip Repeat Deliveries (Remove Duplicates): removes duplicate items
- Settings (Edit Fields (Set)): sets 4 fields: jiraUrl, teamChannel, staleAfter…
- Load Open Issues (Data table): get
- Sort the Blockers (Code): runs custom JavaScript code
- New, Carried or Cleared? (Switch): routes items into 3 branches
- Move It to Today (Data table): update
- Forget the Issue (Data table): delete rows
- Triage the Blocker (Basic LLM Chain): sends a prompt to an LLM, with model: OpenAI GPT-5 Mini; output parser: Parse the Result
- Due a Nudge? (If): checks a condition and branches into true / false
- Comment That It Cleared (Jira Software): add (issue comment)
…plus 5 more steps. See the full node list below.
Services it uses
Before you upgrade to n8n 3.0
We can't fully verify this one: it relies on 1 community package, and n8n 3.0 turns unverified community packages off by default (N8N_UNVERIFIED_PACKAGES_ENABLED=false).
- Check that n8n-nodes-teamretro is verified or supports 3.0 (used in When Standup Closes).
Nodes used (12)
- Team Retro Trigger
n8n-nodes-teamretro.teamRetroTrigger - Remove Duplicates
n8n-nodes-base.removeDuplicates - Edit Fields (Set)
n8n-nodes-base.set - Data table
n8n-nodes-base.dataTable - Code
n8n-nodes-base.code - Switch
n8n-nodes-base.switch - Basic LLM Chain
@n8n/n8n-nodes-langchain.chainLlm - OpenAI Chat Model
@n8n/n8n-nodes-langchain.lmChatOpenAi - Structured Output Parser
@n8n/n8n-nodes-langchain.outputParserStructured - If
n8n-nodes-base.if - Jira Software
n8n-nodes-base.jira - Slack
n8n-nodes-base.slack
From the author
Quick overview This workflow triggers when a TeamRetro standup completes, tracks blockers in an n8n Data Table, uses OpenAI to triage new blockers, creates actionable Jira issues, posts them to Slack, and comments on carried-over or cleared blockers until…