Turn TeamRetro Standup Blockers into Jira Issues with AI + Slack

Turn TeamRetro standup blockers into Jira issues automatically—powered by AI and delivered to Slack

This n8n workflow watches for completed TeamRetro Standup updates, uses OpenAI to triage new blockers, and then creates actionable Jira issues. It also keeps teams synced in Slack—including follow-up comments for blockers that carry over until they’re resolved.

What this workflow does

• Triggers on Standup Completed from TeamRetro, and prevents duplicates by checking the TeamRetro deliveryId.
• Loads existing mappings from an n8n Data Table named standup_blockers (tracked by updateId and issueKey).
• Classifies blocker updates as new, carried over, or cleared by matching against previously tracked updates and the user who posted.
• Carried-over blockers: updates the stored mapping to the latest update and posts a Jira comment every set number of standups until the blocker is resolved.
• Cleared blockers: deletes the stored mapping and adds a Jira comment stating the blocker has cleared.
• New blockers: sends the blocker text to OpenAI to determine whether it’s actionable and to generate a category and a Jira-ready title.
• Creates Jira issues for actionable blockers, stores the new issueKey + updateId mapping, and posts the ticket link to a configured Slack channel.

Use cases

• Convert recurring standup blocker notes into consistent Jira tickets without manual copy/paste.
• Automatically remind Jira owners as blockers carry over across multiple TeamRetro standups.
• Mark blockers as cleared in Jira the moment they disappear from standup updates.

Technical details

• Integrations/nodes: TeamRetro Trigger, OpenAI, Jira, Slack, plus logic nodes such as if, switch, code, and set.
• Data storage: n8n Data Table standup_blockers with columns including updateId and issueKey.
• Setup: In TeamRetro, add a webhook for “Standup Completed”, use the workflow’s production webhook URL, and paste the signing secret into the TeamRetro Trigger node.