Automate Jira Agile Retrospectives with n8n & AI

What This Automation Does

This workflow watches for when a Jira Epic is marked as Done. It then collects all issues in that Epic, grabs comments from each issue, and puts this info together. An AI tool reads all the data and writes a Lessons Learned report in Markdown. The report is sent to a Google Docs file for easy sharing.

It’s made to save time and avoid mistakes by automating creating sprint retrospective reports from Jira data. Teams get clear, fast insights without spending hours manually compiling everything.

Tools and Services Used

• Jira Software Cloud API: Detects Epic status changes; fetches issues and comments.


• OpenAI GPT-4o-mini model: Generates detailed Lessons Learned reports in Markdown.


• Google Docs API: Updates a Google document with the AI report.


• n8n: Runs the entire workflow, connects all parts, and automates the process.

Workflow Input, Processing, and Output

Inputs

• Jira Epic moves to Done status (trigger event).


• Issues linked to the Epic with their descriptions.


• Comments on each issue providing feedback and discussion.

Processing Steps

• Listen for Epic status update to Done using Jira Trigger and confirm with If node.


• Fetch all issues in the completed Epic with Jira Get All Issues.


• For each issue, retrieve comments using Jira Get All Comments.


• Prepare combined fields: Epic name, status, issue titles, descriptions, and latest comments with Edit Fields (Set).


• Concatenate comments and descriptions using Summarize node to build input for AI.


• Run the AI Agent node with OpenAI GPT-4o-mini model to generate a Markdown formatted Lessons Learned report based on the inputs.


• Store AI conversation context with the Simple Memory node for consistent results over repeated runs.


• Send the generated report to Google Docs via the Google Docs node that updates an existing document.

Output

• A well-structured Agile retrospective report in Markdown saved into a Google Docs file.


• The report includes Key Findings, Recommendations, and Metrics sections helpful for team reviews.


• Time saved: Automates 3-4 hours of manual work per sprint for Agile coaches.

Beginner Step-by-Step: How to Use This Workflow in n8n

Importing the Workflow

1. Download the workflow file using the Download button on this page.


2. Open your n8n editor where you manage workflows.


3. Use the “Import from File” option in n8n to load the downloaded workflow.

Configuring Credentials and IDs

1. Add the Jira Software Cloud API credentials in n8n, including API Key and Cloud URL.


2. Insert your OpenAI API Key in the AI Agent node settings.


3. Set up Google Docs OAuth2 credentials and connect them in the Google Docs node.


4. Update any IDs or document URLs for Google Docs if you want to store reports in particular documents or folders.

Testing and Activation

1. Run a test by changing a Jira Epic status to Done in your test environment.


2. Check the workflow logs to confirm issues and comments are fetched and AI produces a report.


3. Verify the Google Docs document is updated with the new report.


4. When confirmed, activate the workflow to run automatically during real sprints.

If you run a self-host n8n instance, make sure your environment allows webhook traffic and scheduled triggers.

Customizations

• Change report format from Markdown to HTML or plain text by editing the AI Agent system message prompt.


• Modify issue fetch query in Jira Get All Issues to select only specific issue types like bugs or stories.


• Add an extra AI node to analyze comment sentiment for deeper team feedback insight.


• Use dynamic Google Docs document selection based on Epic name to better organize reports.

Troubleshooting

Problem: No issues returned from Jira Get All Issues node

Check if the Epic key used is properly extracted from the Jira trigger event. Incorrect input means no issues get fetched.

Problem: AI Agent returns incomplete or error-filled report

Verify all required fields (title, description, comments) are correctly formatted and mapped. Adjust the prompt in the system message if needed.

Problem: Google Docs node cannot update document

OAuth2 credentials might be expired or lack permission. Refresh authentication and confirm sharing settings on the target document.

Pre-Production Checklist

• Confirm Jira API credentials have read permissions for issues and comments.


• Test that the Jira Trigger runs only when an Epic’s status changes to Done.


• Run a sample Epic through the workflow to see if issues and comments get retrieved properly.


• Check the AI Agent prompt input and output for proper formatting.


• Confirm Google Docs updates display the AI-generated report correctly.

Deployment Guide

Activate the workflow in n8n. Ensure Jira webhook settings call the workflow trigger properly on Epic updates.

Watch the execution logs in early runs to catch errors. Set up alerts in n8n if retrospective generation is critical.

The workflow runs on its own once set, no manual steps needed during sprints.

Summary and Results

✓ Saves 3-4 hours per sprint by automating retrospective report creation.
✓ Improves accuracy by eliminating manual copying and errors.
✓ Delivers fast, detailed reports in Markdown automatically saved in Google Docs.
✓ Ensures teams get timely lessons learned to improve future sprints.