Auto-generate GitHub release notes and notify via Slack

Open on n8n.io

$20/month : Unlimited workflows

2500 executions/month

Try free

THE #1 IN WEB SCRAPING

Scrape any website without limits

Try free

HOSTINGER

Early Deal
DISCOUNT 20%

Self-hosted n8n

Unlimited workflows - from $4.99/mo

Try free

#1 hub for scraping, AI & automation

6000+ actors - $5 credits/mo

Try free

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

Auto Generate GitHub Release Notes and Notify via Slack (n8n Workflow) This n8n workflow automates the process of: Generating structured GitHub release notes from merged pull requests since the las...

Best for

DevOps automation workflows
intermediate n8n builders looking for reusable templates

Tools used

n8n-nodes-base.set, n8n-nodes-base.httprequest, n8n-nodes-base.code, n8n-nodes-base.formtrigger, n8n-nodes-base.stickynote

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by WeblineIndia.

Original n8n.io source

1.1 Workflow description

Title: Auto-generate GitHub release notes and notify via Slack
Workflow name: Auto-generate GitHub release notes and notify via Slack

Auto-Generate GitHub Release Notes and Notify via Slack (n8n Workflow)

This n8n workflow automates the process of:

Generating structured GitHub release notes from merged pull requests since the last tag.
Creating a draft GitHub release using the latest tag and PR info.
Sending a formatted summary to a Slack channel.

All of this is triggered manually via a form, where the user inputs the repository, owner and target branch.

Who's It For

This flow is perfect for:

Open-source maintainers looking to automate changelog management.
DevOps engineers handling release cycles.
Engineering teams maintaining structured, consistent GitHub releases.
Technical writers who prepare release notes.

How It Works

Node Summary:

Node No	Node Name	Description
1	GitHub Release Input Form	Takes user inputs (owner, repo, branch).
2	Config	Extracts input and defines PR label grouping config.
3	Get Latest Git Tag	Fetches latest Git tag (used as reference point).
4	Get Commit Date of Latest Tag	Gets the exact timestamp of the latest tag's commit.
5	Fetch All Merged PRs Since Last Tag	Queries GitHub for PRs merged after that timestamp.
6	Group PRs & Generate Release Notes	Organizes PRs by label and generates markdown notes.
7	GitHub Pre-release	Creates a draft GitHub release with those notes.
8	Send Message to Slack	Sends the final release summary to Slack.

How to Set Up

Clone or import this workflow into your n8n instance.
Configure the following credentials:
- GitHub OAuth or PAT (Personal Access Token)
- Slack Webhook URL or OAuth credentials
Open the form node and fill in:
- owner: GitHub username/org
- repo: GitHub repository name
- branch: Base branch (e.g., main)
Run the workflow manually and observe the release note being:
- Created as a draft on GitHub
- Sent to Slack

Requirements

Requirement	Description
n8n version	Cloud or Self-Hosted
GitHub Access	A token with `repo` and `write:repo_hook` permissions
Slack Access	Webhook URL or Slack OAuth app
Git Tags	Semantic versioning tags pushed to the repo
Labels	PRs should be labeled (e.g., `feature`, `bug`, `other`) for grouping

How to Customize

Feature	How to Customize
Label Grouping	Modify the config map in the `Config` node (step 2).
PR Filtering	Adjust the search query in node 5 to fit your repo's conventions.
Markdown Template	Tweak markdown generation logic in node 6.
Slack Message Format	Customize the Slack text in node 8.
Tag Format	Switch from semantic versioning if needed in node 3 logic.
Release Type	Change `draft: true` to `false` in node 7 for immediate publishing.

Add‑ons

You can extend the flow by:

Adding a cron scheduler for periodic releases.
Sending release notes via email (use the Email node).
Publishing directly to Jira or Confluence.
Posting GitHub release links to Discord.

Use Case Examples

Scenario	Description
OSS Team Weekly Releases	Automatically publish weekly release notes summarizing merged PRs.
Sprint Review Reports	Use it at the end of each sprint to generate change summaries.
CI/CD Pipelines	Integrate with GitHub Actions or Jenkins for automated tagging + release.

Common Troubleshooting

Issue	Possible Cause	Solution
`No data found for item-index: "1"`	GitHub Search returned no PRs	Ensure PRs were merged after the last tag and branch name is correct
`Cannot access $node in code`	Wrong script execution context	Ensure JavaScript is selected and variables are accessed properly
`draft must be boolean`	Draft field passed as string	Use `true` (not `"true"`) in JSON input of HTTP node
`PR labels not grouped`	PRs have no matching labels	Update your label config map or ensure labels exist on PRs
Empty Slack message	Slack node not receiving data	Ensure `$json.release_notes` is being passed correctly

Need Help?

Need help setting this up for your team or extending it for more features (e.g., JIRA, auto-tagging, changelog export)? We're here to help you customize, debug and scale this flow.

Feel free to reach out WeblineIndia if you need:

One-on-one setup assistance.
Custom n8n nodes or scripts.
Advanced GitHub/Slack integrations.

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - Config

Type / Role: n8n-nodes-base.set - set
Config choices: Version 3.4

Block 2 - Get Latest Git Tag

Type / Role: n8n-nodes-base.httpRequest - httpRequest
Config choices: Version 4.2

Block 3 - Get Commit Date of Latest Tag

Type / Role: n8n-nodes-base.httpRequest - httpRequest
Config choices: Version 4.2

Block 4 - Fetch All Merged PRs Since Last Tag

Type / Role: n8n-nodes-base.httpRequest - httpRequest
Config choices: Version 4.2

Block 5 - Adjusted: Group PRs & Generate Release Notes

Type / Role: n8n-nodes-base.code - code
Config choices: Version 2

Block 6 - Github Pre Release

Type / Role: n8n-nodes-base.httpRequest - httpRequest
Config choices: Version 4.2

Block 7 - Send message to slack

Type / Role: n8n-nodes-base.httpRequest - httpRequest
Config choices: Version 4.2

Block 8 - GitHub Release Input Form

Type / Role: n8n-nodes-base.formTrigger - formTrigger
Config choices: Version 2.2

Block 9 - Sticky Note

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 10 - Sticky Note1

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

3. Summary Table

Workflow	Auto-generate GitHub release notes and notify via Slack
Complexity	intermediate
Nodes	10
Categories	DevOps
Author	WeblineIndia
Published	01 Aug 2025

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

Use the JSON export at /data/workflows/6763/6763.json as the source template for this automation.
2. Import the template into n8n

Open n8n, import the downloaded JSON, and review each node before activating the workflow.
3. Configure credentials and variables

Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
4. Test with sample data

Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
5. Activate and monitor

Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Download workflow JSON Original n8n.io source DevOps workflows

Frequently asked questions

What does Auto-generate GitHub release notes and notify via Slack do?

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your DevOps use case.

WeblineIndia

216 workflows

Nodes

n8n-nodes-base.set n8n-nodes-base.httprequest n8n-nodes-base.code n8n-nodes-base.formtrigger n8n-nodes-base.stickynote

Complexity

intermediate

Published 01 Aug 2025

Likes 0

View on n8n.io Download Workflow

Install path: /data/workflows/6763/6763.json

Share Your Workflow

Have a useful automation to share? Publish it and help the community.

Submit Your Template How to Submit

Related Workflows

Monitor multi-city courier weather risk with Open-Meteo, GPT-4o, Gemini and Slack

## Quick overview This workflow checks 48-hour forecasts from Open-Meteo for multiple cities on a 6-hour schedule or via an on-demand n8n form, scores conditions against courier-impact thresholds, uses OpenAI (with Google Gemini fallback) to draft Slack-ready alerts, and posts operational updates to a Slack channel. ## How it works 1. Runs every 6 hours on a schedule or starts from an Operations Manager on-demand n8n form submission. 2. Builds a city configuration (all cities for scheduled runs, or a single selected city for on-demand runs) and constructs the Open-Meteo forecast API request. 3. Fetches a 48-hour hourly forecast from Open-Meteo and continues even if the request fails. 4. Scores each city’s forecast against rain, wind, snow, and heat thresholds across multiple time windows, applies 18-hour deduplication for scheduled runs, and flags any city feed failures. 5. Sends the alert candidates to OpenAI to generate a three-sentence, operations-focused message per city (using Google Gemini as the model fallback if configured). 6. Formats each alert as a Slack Block Kit message and posts it to the #ops-weather-alerts channel, and separately posts a Slack error notice if one or more city forecasts could not be fetched. ## Setup 1. Add an OpenAI API credential (used to write the Slack alert messages). 2. Add a Google Gemini (PaLM) API credential if you want the configured fallback model to be available. 3. Add a Slack OAuth2 credential and set or create the target channel (ops-weather-alerts / #ops-weather-alerts) in your Slack workspace. 4. For on-demand checks, share the n8n form URL with your team and update the city dropdown options and the city configuration code if you add or rename cities. 5. Review and adjust the per-city weather thresholds in the city configuration to match your courier operations risk tolerance. ## Requirements - OpenAI API key (GPT-4o / gpt-4o-mini) - Slack OAuth2 credential with chat:write scope - Google Gemini API key (optional, for AI fallback) ## Customization - Add or remove cities by editing the CITIES array in the City config node, no other nodes need to change. - Adjust URGENT/HEADS_UP score thresholds in the Score + dedup node to raise or lower sensitivity per city. - Change the delivery peak windows (default 11:00-14:00 and 17:00-22:00) in the same node to match your market hours. - Swap the Slack channel name in both Slack nodes to route alerts to a different channel. ## Additional info This workflow was built and tested on a self-hosted n8n instance (Oracle Cloud A1 Flex, Ubuntu 24.04) and is fully compatible with n8n Cloud. Weather data is sourced exclusively from Open-Meteo (open-meteo.com), an open-source weather API requiring no authentication. Forecast accuracy follows Open-Meteo's standard model ensemble — verify critical alerts against local meteorological services before operational decisions. Deduplication uses n8n workflow static data (global scope). Clearing static data manually or migrating the workflow to a new instance will reset the deduplication state, causing the next scheduled run to re-evaluate all cities as if no prior alerts have been sent. The GPT-4o prompt includes city-relative climate context so the model understands that an alert in Nairobi means sustained flooding rain, while an alert in Helsinki means genuinely exceptional conditions beyond the Nordic baseline. This prevents generic alert copy across climatically different markets. The form trigger is designed for Operations Managers with no technical background — no n8n access required. Share the webhook URL directly and they can force an immediate check from any browser. Peak delivery windows (11:00-14:00 and 17:00-22:00 local time) are used to escalate severity scoring during high-order-volume periods. Adjust these in the Score + dedup node to match your market's actual peak hours.

View

Notify website downtime via email and Telegram alerts

## Quick overview This workflow runs every minute to check one or more website URLs with HTTP requests and, if a site appears down on two consecutive checks, sends an email alert and a Telegram message. ## How it works 1. Runs on a schedule trigger every minute. 2. Loads a newline-separated list of website URLs plus alert settings (wait time, Telegram chat ID, and email address), then converts the URL list into an array. 3. Splits the array to test each website individually with an HTTP request that captures the full response without failing the workflow on errors. 4. Determines whether the site is up based on the HTTP status code (up if status code is 400 or lower). 5. If the first check indicates the site is down, waits for the configured number of seconds and performs a second HTTP check for the same URL. 6. If the second check also indicates the site is down, sends a “Website Down” email via SMTP and then sends a Telegram message to the configured chat. ## Setup 1. Add SMTP email credentials (for example, Gmail SMTP on port 465) and set the from/to email addresses in the email step. 2. Create a Telegram bot with BotFather, add Telegram Bot API credentials in n8n, and set your Telegram chat ID in the workflow configuration. 3. Update the website URL list and the wait time (seconds) in the workflow configuration to match the sites you want to monitor and your preferred retry delay.

View

Route CI/CD failure alerts with OpenAI, Slack, Linear, Sheets and Gmail

## Quick Overview This workflow receives CI/CD failure webhooks, classifies severity by branch, uses OpenAI to generate a root-cause diagnosis and remediation, then alerts Slack, creates a Linear issue, logs the incident to Google Sheets, and emails a summary via Gmail. ## How it works 1. Receives a POST webhook from your CI/CD system with pipeline run status and metadata. 2. Parses the payload to extract status, pipeline name, branch, commit details, error log, and run URL, and drops malformed events. 3. Filters out non-failure runs and assigns a severity level and Linear priority based on the branch. 4. Sends the error log and context to OpenAI to return a JSON diagnosis, remediation step, and rollback recommendation. 5. Posts a Slack alert to the on-call channel for Critical incidents and posts all incidents to a developer Slack channel. 6. Creates a Linear issue with the failure context and AI diagnosis, appends the incident to a Google Sheets log, and emails a Gmail HTML summary to the engineering lead. ## Setup 1. Copy the workflow’s webhook URL and configure your CI/CD platform (for example GitHub Actions, GitLab CI, or CircleCI) to POST failure events to it. 2. Add credentials for OpenAI, Slack, Google Sheets, and Gmail, and provide a Linear API key for the Linear GraphQL request. 3. Replace placeholders for Slack channel IDs, Linear team ID, Google Sheets spreadsheet ID and sheet name, and the engineering lead email address.

View

Need Custom Automation?

Get help designing a custom n8n workflow that connects your stack and fits your process.

Auto-generate GitHub release notes and notify via Slack

Workflow preview

Important notice

1. Workflow Overview

Best for

Tools used

Source and attribution

1.1 Workflow description

Auto-Generate GitHub Release Notes and Notify via Slack (n8n Workflow)

Who's It For

How It Works

Node Summary:

How to Set Up

Requirements

How to Customize

Add‑ons

Use Case Examples

Common Troubleshooting

Need Help?

1.2 Logical Blocks

2. Block-by-Block Analysis

Block 1 - Config

Block 2 - Get Latest Git Tag

Block 3 - Get Commit Date of Latest Tag

Block 4 - Fetch All Merged PRs Since Last Tag

Block 5 - Adjusted: Group PRs & Generate Release Notes

Block 6 - Github Pre Release

Block 7 - Send message to slack

Block 8 - GitHub Release Input Form

Block 9 - Sticky Note

Block 10 - Sticky Note1

3. Summary Table

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

2. Import the template into n8n

3. Configure credentials and variables

4. Test with sample data

5. Activate and monitor

5. General Notes & Resources

Frequently asked questions