Jira Retrospective
Configured with Agent, Google Docs, Jira, Jira Trigger, and additional nodes. Review the connections and setup before adapting this template.
Node categories in this workflow
- Integration
- AI & models
- Transform
- Files / media
- Trigger
- Routing
- Data store
Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.
Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.
How it works
The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.
| Node | Category | Type | Operation |
|---|---|---|---|
| Jira Get All Issues | Integration | Jira | getAll |
| Jira Get All Comments | Integration | Jira | issueComment / getAll |
| AI Agent | AI & models | Agent | See node parameters |
| OpenAI Chat Model | AI & models | OpenAI Chat Model | See node parameters |
| Edit Fields | Transform | Edit Fields | See node parameters |
| Summarize | Transform | Summarize | See node parameters |
| Google Docs | Files / media | Google Docs | update |
| Jira Trigger | Trigger | Jira Trigger | See node parameters |
| If | Routing | If | See node parameters |
| Simple Memory | Data store | Memory Buffer Window | See node parameters |
Setup
- Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
- Connect your own credentials through n8n’s credential store. Replace
REPLACE_WITH_*values with your resource identifiers. - Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
- Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.
Requirements
An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.
Credential types declared in the source
googleDocsOAuth2ApijiraSoftwareCloudApiopenAiApi
Workflow notes
Epic Done?
Epic Done?
This Node is Triggered on any issue change in Jira. However it only triggers the automation when the Epic status is changed to Done
Fetch issue Description and Comments
Fetch issue Description and Comments
Once the Epic is Done, these nodes fetch issues and comments that fall under the Epic. For further processing the output is bundled.
Summarize and send to Google Docs
Summarize and send to Google Docs
The LLM is summarizing the description / comments and generates a report with a layout defined in the System Message. Finally the output is send to Google Docs.
Jira Retrospective
Jira Retrospective
Purpose and structure
This folder contains the Jira Retrospective workflow. Its executable nodes use agent, googleDocs, if, jira, jiraTrigger, lmChatOpenAi, memoryBufferWindow, set, summarize. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.
Setup
Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.
Entry points
Jira Trigger
Verification
Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.
Attribution
https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Summarize/1706_Summarize_Stickynote_Automation_Triggered.json MIT; preserve source notices.