Back to Catalog

Daily GitHub release notification by email

DionysusDionysus
1980 views
2/3/2026
Official Page

Automating daily notifications of the latest releases from a GitHub repository. This template is ideal for developers and project managers looking to stay up-to-date with software updates.

How it Works:

  • Daily Trigger: The workflow initiates daily using the Schedule Trigger node.
  • Fetch Repository Data: The HTTP Request node retrieves the latest release details from the specified GitHub repository.
  • Check if new: The IF node check if the release was done in the last 24 hours.
  • Split Content: The Split Out node processes the JSON response to extract and structure relevant data.
  • Convert Markdown: The Markdown node converts release notes from Markdown format to HTML, making them ready to use in emails.
  • Send a notification by email

Key Features:

  • Simple to customize by modifying the GitHub URL.
  • Automatically processes and formats release notes for better readability.
  • Modular design, allowing integration with other workflows like Gmail or Slack notifications.

Setup Steps:

  • Modify Repository URL: Update the Sticky Note node with the URL of the repository you want to monitor.
  • Modify SMTP details: Update the Send Email node with your SMTP details.

Daily GitHub Release Notification by Email

This n8n workflow automates the process of checking for new GitHub releases for a specified repository and sending an email notification when new releases are found.

What it does

This workflow simplifies staying updated on new software releases for your monitored GitHub repository.

  1. Schedules Check: The workflow is triggered on a schedule (e.g., daily) to perform its checks.
  2. Fetches GitHub Releases: It makes an HTTP request to the GitHub API to retrieve the latest releases for a configured repository.
  3. Parses Releases: The workflow processes the API response to extract relevant release information.
  4. Checks for New Releases: It compares the fetched releases with previously seen releases (this part is implied, as the If node is present but its condition is not explicitly defined in the provided JSON, suggesting it would compare new data against stored data or a specific criteria).
  5. Formats Email Content: If new releases are detected, it uses a Markdown node to format a human-readable email body with the release details.
  6. Sends Email Notification: Finally, it sends an email to a configured recipient with the formatted release information.

Prerequisites/Requirements

  • n8n Instance: A running n8n instance to host the workflow.
  • Email Sending Credentials: SMTP server details or an email service integration configured in n8n for the "Send Email" node.
  • GitHub Repository URL: The API URL for the GitHub repository you wish to monitor (e.g., https://api.github.com/repos/owner/repo/releases).

Setup/Usage

  1. Import the Workflow: Import the provided JSON into your n8n instance.
  2. Configure GitHub API Request:
    • Locate the "HTTP Request" node.
    • Set the URL to the GitHub API endpoint for releases of your desired repository (e.g., https://api.github.com/repos/n8n-io/n8n/releases).
    • You might need to add authentication headers if you're hitting rate limits or accessing private repositories (though not explicitly configured in this JSON).
  3. Configure Email Sending:
    • Locate the "Send Email" node.
    • Configure your email credentials (SMTP server, username, password, etc.) within n8n.
    • Set the To email address to where you want to receive notifications.
    • Customize the Subject and Body of the email as needed. The "Markdown" node likely provides the content for the email body.
  4. Configure Schedule:
    • Locate the "Schedule Trigger" node.
    • Adjust the schedule (e.g., daily, hourly) according to how frequently you want to check for new releases.
  5. Configure Conditional Logic (If Node):
    • The "If" node is crucial for determining if a new release has occurred. You will need to configure its condition based on your specific needs. This typically involves comparing the id or published_at date of the latest fetched release against a stored value (e.g., from a database, a Google Sheet, or even a simple n8n-nodes-base.keyValueStore node) to identify truly new releases.
  6. Activate the Workflow: Once configured, activate the workflow in n8n.

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

Daniel NkenchoBy Daniel Nkencho
601

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.

higashiyama By higashiyama
90

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.

gotoHumanBy gotoHuman
353