Automated Technical Release Note Generator (GitHub, JIRA, Gemini) - n8n Workflow

• DevOps and Engineering Managers seeking continuous documentation solutions.


• Technical Project Managers needing instant, audience-specific release communication.


• Users looking for advanced n8n templates integrating version control and project management.


• Organizations requiring automated compliance documentation following code deployment.

Manually synthesizing commit messages and JIRA tickets into polished, client-facing release notes is time-consuming and prone to human error. This specialized n8n workflow completely automates this critical documentation step. Utilizing an n8n trigger listening for GitHub push events, the process starts immediately upon code deployment. The workflow intelligently extracts associated JIRA keys from commit messages, retrieves detailed ticket descriptions, and then feeds this complex data set into the Google Gemini large language model (LLM). The LLM follows strict prompt instructions to generate clean, structured HTML release notes suitable for CxOs and non-technical stakeholders. This powerful combination demonstrates how n8n node flexibility drastically improves the efficiency of modern CI/CD pipelines, saving hours of manual work and ensuring high-quality, timely communication.

This comprehensive n8n workflow follows a sequential, data-enrichment process:

1. Trigger on Push: The Github Trigger n8n node initiates the workflow upon a push event to a specified branch in your repository.


2. Extract JIRA Keys: The first Code n8n node iterates through the commit messages provided by the trigger, using a regular expression to extract JIRA issue IDs (e.g., ABC-123).


3. Fetch JIRA Details: Each extracted JIRA ID is processed by the Get an issue JIRA n8n node, which fetches the corresponding summary, description, and status.


4. Clean and Merge Data: The Code2 node cleans up the bulky JIRA output, keeping only essential fields (jiraid, jirasummary, jira_description). The Merge n8n node then combines this cleaned JIRA data with the original commit message data.


5. Prepare for LLM: The Code3 n8n node aggregates all enriched data items into a single, structured array, ready for insertion into the LLM prompt. This preparation is crucial for effective generative AI processing.


6. Generate Release Notes: The Basic LLM Chain uses the Google Gemini Chat Model (gemini-2.5-pro) and a highly specific system prompt. The prompt instructs the LLM to act as a technical release manager and generate the entire release note in HTML format, synthesizing the technical JIRA/commit data into business-friendly bullet points.


7. Email Stakeholders: Finally, the Send email n8n node delivers the LLM-generated HTML content to the specified recipients via SMTP. This completes the automated documentation cycle using this advanced n8n workflow.

To deploy this n8n template, follow these steps:

1. Import: Copy the provided JSON data and import it directly into your n8n instance as a new n8n workflow.


2. GitHub Credentials: Set up or select your GitHub API credentials in the Github Trigger n8n node. Configure the trigger to monitor the correct repository and event type (default is push).


3. JIRA Credentials: Connect your JIRA Software Cloud account credentials to the Get an issue n8n node.


4. Google Gemini Setup: Set up or select your Google Gemini (PaLM) API credentials for the Google Gemini Chat Model n8n node. Ensure the model selection is compatible with the prompt requirements (e.g., models/gemini-2.5-pro).


5. SMTP Setup: Configure your SMTP credentials for the Send email n8n node. Update the To Email and From Email fields with your desired sender and recipient addresses.


6. Activate: Save and activate the n8n workflow. It is now ready to execute automatically upon a GitHub push.

• Github Trigger: This is the core n8n trigger. It listens for push events on the configured repository, providing raw commit data that kicks off the documentation process.


• Code (Extract JIRA IDs): A custom n8n node using JavaScript to parse commit messages and extract strings matching the JIRA ID pattern (e.g., [A-Z]+-\d+).


• Get an issue (JIRA): A JIRA n8n node configured to fetch detailed fields (summary, description) for each individual JIRA key derived from the commits.


• Merge: An essential flow control n8n node that combines the original commit metadata and the newly fetched JIRA data for structured input into the LLM.


• Code3 (Prepare for LLM): This n8n node restructures the merged data into a single object containing an array of items, optimizing the payload for the large language model input context.


• Google Gemini Chat Model: The AI service provider n8n node, configured here with the powerful gemini-2.5-pro model to handle complex generation tasks.


• Basic LLM Chain: This orchestration n8n node uses a detailed HumanMessage prompt to direct the Gemini model to produce highly structured, HTML-formatted release notes based on the combined technical input data.


• Send email: The final action n8n node, responsible for dispatching the generated HTML document via SMTP to the specified email addresses.