{ "workflow": { "id": 6129, "name": "Automate GitHub, JIRA release notes with Google Gemini & notification over email", "views": 1045, "recentViews": 0, "totalViews": 1045, "createdAt": "2025-07-18T09:38:49.318Z", "description": "# This n8n template from [Intuz](https://www.intuz.com/get-started) provides a complete and automated solution for creating and distributing sophisticated release notes. \n\nIt connects to GitHub and JIRA to gather data from recent commits and completed tickets, using specific keywords or labels to identify key features for inclusion. \n\nThis information is then processed by Google Gemini to automatically generate well-written, human-like release notes, which are then distributed via email to stakeholders, creating a complete, end-to-end communication pipeline for every new software release.\n\nThis template is perfect for development teams looking to streamline their release process, ensure consistent communication, and eliminate the manual effort of writing release notes.\n\n\n## How to use\n\n**1. Set up Credentials:**\n\n- GitHub\n- JIRA (Software Cloud API)\n- Google Gemini (or another PaLM/LLM provider)\n- Your SMTP email server.\n\n**2. Configure the GitHub Trigger:**\n\n- Select the Github Trigger node.\n- In the Repository Owner field, enter your GitHub username or organization name.\n- In the Repository Name field, select the repository you want to monitor.\n\n**3. Verify the JIRA Integration:**\n\n- **Important:** This workflow assumes your commit messages contain a JIRA key (e.g., \"PROJ-123: Fix login bug\").\n- Select the first Code node. It uses a regular expression ([A-Z]+-\\\\d+)/i to find JIRA keys. Adjust this expression if your team uses a different format.\n- Select the Get an issue node and ensure your JIRA credentials are correctly configured.\n\n**4. Customize the AI Prompt:**\n\n- Select the Basic LLM Chain node. You can edit the prompt to change the tone, style, or structure of the generated HTML release note to match your company's standards.\n\n\n**5. Configure Email Notifications:**\n\n- Select the Send email node.\n- Update the To Email field with the recipient's email address (e.g., a team distribution list or a stakeholder's email).\n- Customize the From Email and Subject line as needed.\n\n**6. Activate Workflow:**\n\n- Save your changes and activate the workflow. Now, every push to your configured repository will trigger the automated generation and sending of release notes.\n\n\n### Required Tools\n\n- GitHub: To trigger the workflow on code pushes.\n- JIRA: To fetch details about the tasks and bugs included in the release.\n- Google Gemini: To intelligently generate the release note content. (You can swap this for another LLM supported by n8n).\n- SMTP Provider: To send the final release note via email.\n\n\n## Connect with us\n\n- Website: https://www.intuz.com/services\n- Email: getstarted@intuz.com\n- LinkedIn: https://www.linkedin.com/company/intuz\n- Get Started: https://n8n.partnerlinks.io/intuz\n\n## For Custom Worflow Automation\nClick here- [Get Started](https://www.intuz.com/get-started)\n\n", "workflow": { "id": "B9XHO1B8oUR04nOu", "meta": { "instanceId": "1a54c41d9050a8f1fa6f74ca858828ad9fb97b9fafa3e9760e576171c531a787", "templateCredsSetupCompleted": true }, "name": "My workflow 19", "tags": [], "nodes": [ { "id": "d2cc9623-ab49-4a56-8c22-f8a014253179", "name": "Github Trigger", "type": "n8n-nodes-base.githubTrigger", "position": [ -1100, 240 ], "webhookId": "Your_ID", "parameters": { "owner": { "__rl": true, "mode": "name" }, "events": [ "push" ], "options": { "insecureSSL": false }, "repository": { "__rl": true, "mode": "list", "cachedResultUrl": "Your_Github_URL", "cachedResultName": "Your_Repository_Name" } }, "notesInFlow": false, "typeVersion": 1 }, { "id": "240e79d9-9a6d-4fc9-9f46-b681577c54aa", "name": "Code", "type": "n8n-nodes-base.code", "position": [ -880, 240 ], "parameters": { "jsCode": "const inputData = $input.all();\nconst commits = inputData[0].json.body.commits;\n\nreturn commits.map(commit => {\n const message = commit.message;\n const timestamp = commit.timestamp;\n\n // Match something like \"ABC-123\", case-insensitive, from the beginning\n const match = message.match(/([A-Z]+-\\d+)/i);\n\n const jiraId = match ? match[0].toUpperCase() : null;\n\n return {\n json: {\n message,\n timestamp,\n jira_id: jiraId\n }\n };\n});\n" }, "typeVersion": 2 }, { "id": "c4265d41-b0d6-480e-b287-f87fc0dd383f", "name": "Basic LLM Chain", "type": "@n8n/n8n-nodes-langchain.chainLlm", "position": [ -180, 160 ], "parameters": { "text": "=", "batching": {}, "messages": { "messageValues": [ { "type": "HumanMessagePromptTemplate", "message": "=You are a professional technical release manager generating production release notes for CxOs and clients.\n\nGenerate a complete release note in **HTML format**, not plain text. The content is based on the following JIRA items, each having `jira_id`, `jira_summary`, `jira_description`, and `message`.\n\nOutput structure (as HTML):\n\n1. Title and Metadata\n - H2 tag: \"Production Deployment – [Release Date]\"\n - Bold lines: Version, Environment, Deployment Date\n\n2. Overview\n - Short paragraph explaining the goal of this deployment\n\n3. Key Changes\n - Bullet list (