Send Slack notifications when a new release is published for public GitHub repos
This workflow checks a configured list of Github repositories daily to see if a new release has been published.
How it works:
- Workflow has a daily trigger
RepoConfignode is a JSON array that defines a list of repositories to check releases for- For each of the configured repos it fetches the latest release
- If the release was published within the last 24 hours it is output
- The release is sent as a Slack message showing the repo name, release name and link
Setup
- Update the JSON in the RepoConfig node to the Github repos you wish to get notifications for
- Setup your Slack connection (or replace with your choice of notification)
Send Slack Notifications for New GitHub Releases
This n8n workflow automates the process of checking for new releases in public GitHub repositories and sending notifications to a specified Slack channel. It simplifies staying updated on your favorite open-source projects or critical dependencies.
What it does
- Triggers on a schedule: The workflow runs at regular intervals (e.g., every 5 minutes, hourly, daily) to check for updates.
- Fetches GitHub repository data: It makes an HTTP request to the GitHub API to retrieve information about a specific public repository.
- Parses release information: It extracts the latest release tag name from the API response.
- Compares with previous release: It uses a "Sticky Note" to store the last known release tag and compares it with the newly fetched tag.
- Filters for new releases: If a new release is detected (i.e., the current release tag is different from the stored one), the workflow proceeds.
- Updates stored release tag: The "Sticky Note" is updated with the new release tag.
- Sends Slack notification: A message is posted to a designated Slack channel, announcing the new release with its tag name.
Prerequisites/Requirements
- n8n Instance: A running n8n instance.
- Slack Account: A Slack workspace where you want to post notifications.
- Slack Credential: An n8n credential for your Slack workspace (e.g., a Slack API token or webhook URL).
- GitHub Repository URL: The URL of the public GitHub repository you wish to monitor.
Setup/Usage
- Import the workflow: Import the provided JSON into your n8n instance.
- Configure the Schedule Trigger:
- Open the "Schedule Trigger" node.
- Set your desired interval for checking new releases (e.g., "Every 5 minutes" for frequent checks).
- Configure the HTTP Request node:
- Open the "HTTP Request" node.
- In the "URL" field, replace
https://api.github.com/repos/n8n-io/n8n/releases/latestwith the API endpoint for your desired GitHub repository. The format is typicallyhttps://api.github.com/repos/OWNER/REPO_NAME/releases/latest.
- Configure the Slack node:
- Open the "Slack" node.
- Select or create a Slack credential.
- Specify the "Channel" where you want the notifications to be sent (e.g.,
#general,#dev-releases). - Customize the "Text" field for the message if desired. The current setup uses an expression to include the release tag:
New release published: {{ $('Code').item.json.releaseTag }}.
- Activate the workflow: Once configured, activate the workflow to start monitoring for new releases.
This workflow is designed to be easily adaptable for monitoring multiple GitHub repositories by duplicating and configuring the "HTTP Request" and "Slack" nodes for each repository.
Related Templates
Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax
Spark your creativity instantly in any chat—turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. 📋 What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing 🔧 Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation 🔑 Required Credentials OpenAI API Setup Go to platform.openai.com → API keys (sidebar) Click "Create new secret key" → Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai → Dashboard → API Keys Generate a new API key → Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) ⚙️ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflow—chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions
AI-powered code review with linting, red-marked corrections in Google Sheets & Slack
Advanced Code Review Automation (AI + Lint + Slack) Who’s it for For software engineers, QA teams, and tech leads who want to automate intelligent code reviews with both AI-driven suggestions and rule-based linting — all managed in Google Sheets with instant Slack summaries. How it works This workflow performs a two-layer review system: Lint Check: Runs a lightweight static analysis to find common issues (e.g., use of var, console.log, unbalanced braces). AI Review: Sends valid code to Gemini AI, which provides human-like review feedback with severity classification (Critical, Major, Minor) and visual highlights (red/orange tags). Formatter: Combines lint and AI results, calculating an overall score (0–10). Aggregator: Summarizes results for quick comparison. Google Sheets Writer: Appends results to your review log. Slack Notification: Posts a concise summary (e.g., number of issues and average score) to your team’s channel. How to set up Connect Google Sheets and Slack credentials in n8n. Replace placeholders (<YOURSPREADSHEETID>, <YOURSHEETGIDORNAME>, <YOURSLACKCHANNEL_ID>). Adjust the AI review prompt or lint rules as needed. Activate the workflow — reviews will start automatically whenever new code is added to the sheet. Requirements Google Sheets and Slack integrations enabled A configured AI node (Gemini, OpenAI, or compatible) Proper permissions to write to your target Google Sheet How to customize Add more linting rules (naming conventions, spacing, forbidden APIs) Extend the AI prompt for project-specific guidelines Customize the Slack message formatting Export analytics to a dashboard (e.g., Notion or Data Studio) Why it’s valuable This workflow brings realistic, team-oriented AI-assisted code review to n8n — combining the speed of automated linting with the nuance of human-style feedback. It saves time, improves code quality, and keeps your team’s review history transparent and centralized.
Auto-reply & create Linear tickets from Gmail with GPT-5, gotoHuman & human review
This workflow automatically classifies every new email from your linked mailbox, drafts a personalized reply, and creates Linear tickets for bugs or feature requests. It uses a human-in-the-loop with gotoHuman and continuously improves itself by learning from approved examples. How it works The workflow triggers on every new email from your linked mailbox. Self-learning Email Classifier: an AI model categorizes the email into defined categories (e.g., Bug Report, Feature Request, Sales Opportunity, etc.). It fetches previously approved classification examples from gotoHuman to refine decisions. Self-learning Email Writer: the AI drafts a reply to the email. It learns over time by using previously approved replies from gotoHuman, with per-classification context to tailor tone and style (e.g., different style for sales vs. bug reports). Human Review in gotoHuman: review the classification and the drafted reply. Drafts can be edited or retried. Approved values are used to train the self-learning agents. Send approved Reply: the approved response is sent as a reply to the email thread. Create ticket: if the classification is Bug or Feature Request, a ticket is created by another AI agent in Linear. Human Review in gotoHuman: How to set up Most importantly, install the gotoHuman node before importing this template! (Just add the node to a blank canvas before importing) Set up credentials for gotoHuman, OpenAI, your email provider (e.g. Gmail), and Linear. In gotoHuman, select and create the pre-built review template "Support email agent" or import the ID: 6fzuCJlFYJtlu9mGYcVT. Select this template in the gotoHuman node. In the "gotoHuman: Fetch approved examples" http nodes you need to add your formId. It is the ID of the review template that you just created/imported in gotoHuman. Requirements gotoHuman (human supervision, memory for self-learning) OpenAI (classification, drafting) Gmail or your preferred email provider (for email trigger+replies) Linear (ticketing) How to customize Expand or refine the categories used by the classifier. Update the prompt to reflect your own taxonomy. Filter fetched training data from gotoHuman by reviewer so the writer adapts to their personalized tone and preferences. Add more context to the AI email writer (calendar events, FAQs, product docs) to improve reply quality.