Generate lessons learned reports from Jira epics with AI and Google Docs
Needs changesNeeds changes. This template uses 1 thing(s) that n8n 3.0 removes: AI Agent v1 (old agent modes). 1 breaking item(s) found. Static check, last run 2026-10-19.
What this workflow does
This AI workflow has 10 nodes and runs on Jira events (jira:issue updated). Along the way it connects Jira Software, OpenAI Chat Model and Google Docs.
How it runs
Trigger: On Jira events (jira:issue updated).
- If: checks a condition and branches into true / false
- Jira Get All Issues (Jira Software): get many
- Jira Get All Comments (Jira Software): get many (issue comment)
- Edit Fields (Edit Fields (Set)): sets 5 fields: EpicName, EpicStatus, Title…
- Summarize: summarizes / groups the items
- AI Agent: runs an AI agent, with model: OpenAI Chat Model; memory: Simple Memory
- Google Docs: update
Services it uses
Before you upgrade to n8n 3.0
1 thing in this workflow is removed in n8n 3.0. Fix it before you upgrade:
- AI Agent v1 (old agent modes) in AI Agent (v1.9): replace with Latest AI Agent node (Tools Agent). For SQL Agent, use a Postgres or MySQL tool with a recent AI Agent.
Rather not rewrite it? Many of these flows can be rebuilt in Make (free plan).
| Removed in 3.0 | Replace with |
|---|---|
| AI Agent v1 (old agent modes) AI Agent (v1.9) | Latest AI Agent node (Tools Agent). For SQL Agent, use a Postgres or MySQL tool with a recent AI Agent. |
Nodes used (9)
- Jira Software
n8n-nodes-base.jira - AI Agent
@n8n/n8n-nodes-langchain.agent - OpenAI Chat Model
@n8n/n8n-nodes-langchain.lmChatOpenAi - Edit Fields (Set)
n8n-nodes-base.set - Summarize
n8n-nodes-base.summarize - Google Docs
n8n-nodes-base.googleDocs - Jira Trigger
n8n-nodes-base.jiraTrigger - If
n8n-nodes-base.if - Simple Memory
@n8n/n8n-nodes-langchain.memoryBufferWindow
From the author
Who is this for? Jira users who want to automate the generation of a Lessons Learned or Retrospective report after an Epic is Done. What problem is this workflow solving? / use case Lessons Learned / Retrospective reports are often omitted in Agile teams…