Can GitHub connect with HTTP Request?

Yes, GitHub can connect with HTTP Request using n8n.io. With n8n, you can create workflows that automate tasks and transfer data between GitHub and HTTP Request. Configure nodes for GitHub and HTTP Request in the n8n interface, specifying actions and triggers to set up their connection.

Can I use GitHub’s API with n8n?

Yes, with n8n, you can programmatically interact with GitHub’s API via pre-defined supported actions or raw HTTP requests. With the HTTP Request node, you create a REST API call. You need to understand basic API terminology and concepts.

Can I use HTTP Request’s API with n8n?

Yes, with n8n, you can programmatically interact with HTTP Request’s API via pre-defined supported actions or raw HTTP requests. With the HTTP Request node, you create a REST API call. You need to understand basic API terminology and concepts.

Is n8n secure for integrating GitHub and HTTP Request?

Yes, it is safe to use n8n to integrate GitHub and HTTP Request. n8n offers various features to ensure the safe handling of your data. These include encrypted data transfers, secure credential storage, RBAC functionality, and compliance with industry-standard security practices (SOC2 compliant). For hosted plans, data is stored within the EU on servers located in Frankfurt, Germany. You can also host it on your own infrastructure for added control. Learn more about n8n’s security practices here.

How to get started with GitHub and HTTP Request integration in n8n.io?

To start integrating GitHub and HTTP Request in n8n, you have different options depending on how you intend to use it: n8n Cloud: hosted solution, no need to install anything. Self-host: recommended method for full-control or customized use cases. Unlike other platforms that charge per operation, step, or task, n8n charges only for full workflow executions. This approach guarantees predictable costs and scalability, no matter the complexity or volume of your workflows.

GitHub and HTTP Request: Automate Workflows with n8n

Daily Workflow Backups to GitHub with Slack Notifications

Who is this for? This workflow is ideal for n8n self-hosted users, DevOps engineers, and automation developers who want to automatically back up their n8n workflows to GitHub on a regular basis. What problem is this workflow solving Manually backing up n8n workflows can be time-consuming and prone to human error. This workflow automates the backup process, ensuring that all workflows are safely stored in a version-controlled GitHub repository every 24 hours. What this workflow does This automation runs daily to back up all workflows from your n8n instance to a specified GitHub repository. Each workflow is saved as a .json file using its unique ID, organized into a folder path defined by repo_path. The workflow is designed to manage memory usage efficiently by recursively calling itself. Once the backup is complete, it optionally sends a Slack notification to confirm success. Setup Configure the Config node in the subworkflow to set: GitHub Repo Owner GitHub Repo Name Main folder path (repo_path) Connect your GitHub and (optionally) Slack credentials. Set the workflow to run on a daily cron schedule. Test the workflow manually to confirm the GitHub integration works. Sign up for a free consultation and find out how n8n can help you.

+2

AI Timesheet Generator with Gmail, Calendar & GitHub to Google Sheets

AI-Powered Automatic Timesheet Generator for Google Sheets Stop wasting billable hours on manual time-tracking. AutoTimesheet Pro uses AI to collect emails, meetings, and GitHub work, then writes a clean timesheet straight into Google Sheets. Perfect for developers, consultants, agencies, and remote teams. Get Started with n8n now! 🚀 Key Features Automated Google Sheets time-tracking** — zero spreadsheet prep. AI-generated activity summaries** (≤ 120 chars) via OpenAI GPT-4o-mini. Gmail integration** — logs only important emails, skipping newsletters & no-replies. Google Calendar time logger** — captures confirmed events, duration, and attendees. GitHub commit & PR tracker** — records your commits plus opened/closed PRs. Daily 7 PM cron trigger** (easily adjustable). Month-based sheet creation** — new tab spins up on the first run each month. No-code n8n template* — just connect credentials and tweak one Set Variables* node. 🔌 Easily extensible** — drag-and-drop extra n8n nodes to add Slack, Jira, Notion, Asana, Trello, Toggl, or any other data source you need. 🔍 How It Works Collect — n8n pulls data from Gmail, Google Calendar, and chosen GitHub repos. Clean — filters remove noise (newsletters, irrelevant commits, etc.). Condense — OpenAI rewrites each item into a concise, SEO-friendly description. Write — workflow appends Date, Type, and Description to your Timesheet Google Sheet. Extend — simply insert new n8n nodes (e.g., Slack, Notion, Jira) and merge them into the same pipeline. 📈 Benefits for SEO-Minded Professionals Keyword-rich activity log** improves internal search and reporting. Structured data** in Sheets simplifies export to accounting or PM tools. Consistent naming** (CALENDAR_EVENT, EMAIL, COMMIT, PR) makes analytics easy. ✅ Why Choose AutoTimesheet Pro? Zero manual entry — just open the sheet and bill clients. Immediate visibility into where your hours went. Works with any GitHub repo list and any inbox you own. 100 % no-code setup — activate in minutes. Built on n8n, so you can customize and scale without limits. 📥 Get Started Ready to replace manual time-tracking with smart automation? https://n8n.partnerlinks.io/ds9podzjls6d Join N8N now, connect your Google & GitHub accounts, and let AI handle your daily log.

+6

Personalize Resumes & Cover Letters with AI, GitHub Pages and Google Drive

🧠 Automated Resume & Cover Letter Generator This project is an automation workflow that generates a personalized resume and cover letter for each job listing. 🚀 Features Automated Resume Crafting Generates an HTML resume from your data. Hosts it live on GitHub Pages. Converts it to PDF using Gotenberg and saves it to Google Drive. Automated Cover Letter Generation Uses an LLM to create a tailored cover letter for each job listing. Simple Input Database Agent Stores your experience in an n8n Data Table with the following fields: role, summary, task, skills, tools, industry. The main agent pulls this data using RAG (Retrieval-Augmented Generation) to personalize the outputs. One-Time GitHub Setup Initializes a blank GitHub repository to host HTML files online, allowing Gotenberg to access and convert them. 🧩 Tech Stack Gotenberg** – Converts HTML to PDF GitHub Pages** – Hosts live HTML files n8n** – Handles data tables and workflow automation LLM (OpenAI / Cohere / etc.)** – Generates cover letters Google Drive** – Stores the final PDFs ⚙️ Installation & Setup Create a GitHub Repository This repo will host your HTML resume through GitHub Pages. Set the Webhook URL In the notify-n8n.yml file, replace: role | summary | task | skills | tools | industry Create the n8n Data Table Add the following columns: role | summary | task | skills | tools | industry Create a Google Spreadsheet Add these columns: company | cover_letter | resume Install Gotenberg Follow the installation instructions on the Gotenberg GitHub repository: https://github.com/thecodingmachine/gotenberg Customize the HTML Template Modify the HTML resume to your liking. You can use an LLM to locate and edit specific sections. Add Authentication and Link Your GitHub Repo Ensure your workflow has permission to push updates to your GitHub Pages branch. Run the Workflow Once everything is connected, trigger the workflow to automatically generate and save personalized resumes and cover letters. 📝 How to Use Copy and paste the job listing description into the Telegram bot. Wait for the "Done" notification before submitting another job. Do not use the bot again until the notification appears. The process usually takes a few minutes to complete. ✅ Notes This workflow is designed to save time and personalize your job applications efficiently. By combining n8n automation, LLMs, and open-source tools like Gotenberg, you can maintain full control over your data while generating high-quality resumes and cover letters for every job opportunity.

Automatic Typebot Flows Two-Way Sync with GitHub using Typebot API

Remixed Backup your workflows to GitHub from Solomon's work. Check out his templates. How it works This workflow will backup your typebots to GitHub. It uses the Typebot API to export all typebots. It then loops over the data, checks in GitHub to see if a file exists that uses the credential's ID. Once checked it will: update the file on GitHub if it exists; create a new file if it doesn't exist; ignore if it's the same. In addition, it also checks if any flow have been deleted from typebot workspace. If a flow no longer exists in workspace, the corresponding file will be removed from the repository to keep everything in sync. Who is this for? People wanting to backup their typebots(flows) outside the server for safety purposes or to migrate to another server.

Automated n8n Workflow Backup to GitHub with Deletion Tracking

Remixed Backup your workflows to GitHub from Solomon's work. Check out his templates. How it works This workflow will backup your workflows to GitHub. It uses the n8n API node to export all workflows. It then loops over the data, checks in GitHub to see if a file exists that uses the credential's ID. Once checked it will: update the file on GitHub if it exists; create a new file if it doesn't exist; ignore if it's the same. In addition, it also checks if any workflows have been deleted from n8n. If a workflow no longer exists in n8n, the corresponding file will be removed from the repository to keep everything in sync. Who is this for? People wanting to backup their workflows outside the server for safety purposes or to migrate to another server.

Create Character-Consistent Images with FLUX Kontext & Post to Social via Upload Post

Create, iterate, and share! Transform a single image through multiple scenes while maintaining consistency. ✨ What this workflow does This template showcases FLUX.1 Kontext - Black Forest Labs' in-context image generation model that excels at maintaining character features across multiple transformations. Combined with the Upload Post community node for effortless multi-platform social media posting, you can create and share compelling visual stories instantly. The workflow demonstrates FLUX Kontext's core strength: character consistency across multiple image generations. Starting with a single input image, it: 🖼️ Loads an initial character image (example: a cute animal mascot) 📝 Defines multiple scene transformation prompts 🔄 Iteratively generates new scenes while preserving exact character features 🎯 Maintains visual consistency by reusing binary data from previous generations 📱 Auto-posts the complete transformation series to multiple social platforms simultaneously 🚀 Key Features: The Consistency Advantage Character Preservation**: FLUX Kontext's signature feature - maintains character features and style across transformations (requires specific prompting techniques) Iterative Context Building**: Each generation uses the previous image as context, creating visual continuity Binary Data Reuse**: Smart workflow design that feeds output from one generation as input to the next Multi-Scene Storytelling**: Transform your character across different environments while keeping them recognizable One-Click Multi-Platform Posting*: Upload Post eliminates the tedious process of posting to each platform individually 📱 Why use Upload Post? Posting the same content to TikTok, Instagram, LinkedIn, YouTube, Facebook, X (Twitter), and Threads individually is time-consuming and error-prone. The Upload Post service* simplifies this process: ✅ Connect once, post everywhere: Link all your social media accounts to Upload Post ✅ Single API call: Post to multiple platforms with one simple node ✅ No more platform juggling: Skip the endless switching between apps and dashboards ✅ Consistent timing: All platforms get your content simultaneously ✅ Trusted by 3,751+ users: Proven solution for content creators and marketers Instead of spending 30+ minutes manually posting to each platform, Upload Post does it all in seconds with a single n8n node! 🛠️ Prerequisites Required Accounts: Black Forest Labs API: Create account at dashboard.bfl.ai Get your API key for FLUX Kontext Pro access Upload Post Account: Sign up at upload-post.com* Connect your social media profiles (TikTok, Instagram, LinkedIn, YouTube, Facebook, X/Twitter, Threads) Get API credentials for automated posting Free tier available: 10 uploads/month 💡 Perfect For: Character Designers** maintaining brand character integrity across scenes Social Media Managers** creating engaging visual story series without manual posting Brand Marketers** ensuring character consistency across campaigns Storytellers** building visual narratives with consistent protagonists Agencies** managing multiple client accounts efficiently 🔧 Customization Options: Modify transformation prompts** to create your own character journey Adjust iteration steps** Change initial character image** Configure social platform targeting** (choose which platforms to post to) Customize post content** and formatting Experiment with different consistency scenarios** \ Affiliate link*

Automated PR Code Reviews with GitHub, GPT-4, and Google Sheets Best Practices

AI-Agent Code Review for GitHub Pull Requests Description: This n8n workflow automates the process of reviewing code changes in GitHub pull requests using an OpenAI-powered agent. It connects your GitHub repo, extracts modified files, analyzes diffs, and uses an AI agent to generate a code review based on your internal code best practices (fed from a Google Sheet). It ends by posting the review as a comment on the PR and tagging it with a visual label like ✅ Reviewed by AI. 🔧 What It Does Triggered on PR creation Extracts code diffs from the PR Formats and feeds them into an OpenAI prompt Enriches the prompt using a Google Sheet of Swift best practices Posts an AI-generated review as a comment on the PR Applies a PR label to visually mark reviewed PRs ✅ Prerequisites Before deploying this workflow, ensure you have the following: n8n Instance (Self-hosted or Cloud) GitHub Repository with PR activity OpenAI API Key** for GPT-4o, GPT-4-turbo, or GPT-3.5 GitHub OAuth App** (or PAT) connected to n8n to post comments and access PR diffs (Optional) Google Sheets API credentials if using the code best practices lookup node. ⚙️ Setup Instructions Import the Workflow in n8n, click on Workflows → Import from file or JSON Paste or upload the JSON code of this template Configure Triggers and Connections 🔁 GitHub Trigger Node**: PR Trigger Repository**: Select the GitHub repo(s) to monitor Events**: Set to pull_request Auth**: Use GitHub OAuth2 credentials 📥 HTTP Request Node: Get file's Diffs from PR No authentication needed; it uses dynamic path from trigger 🧠 OpenAI Model Node**: OpenAI Chat Model Model**: Select gpt-4o, gpt-4-turbo, or gpt-3.5-turbo Credential**: Provide your OpenAI API Key 🧑‍💻 Code Review Agent Node : Code Review Agent Connected to OpenAI and optionally to tools like Google Sheets 💬 GitHub Comment Poster Uses GitHub API to post review comments back on PR Node: GitHub Robot Credential: Use the agent Github account (OAuth or PAT) Repo : Pick your owen Github Repository 🏷️ PR Labeler (optional) Adds label ReviewedByAI after successful comment Node: Add Label to PR Label : you ca customize the label text of your owen tag. 📊 Google Sheet Best Practices config (optional) Connects to a Google Sheet for coding guideline lookups, we can replace Google sheet by another tool or data base First prepare your best practices list with the clear description and the code bad/good examples Add al the best practices in your Google Sheet Configure* the Code Best Practices node* in the template : Credential : Use your Google Sheet account by OAuth2 URL : Add your Google Sheet document URL Sheet : Add the name of the best practices sheet

Detect Team Burnout with Groq AI Analysis of GitHub Activity for Wellness Reports

Team Wellness - AI Burnout Detector Agent devex github 🎯 Demo sample report github action code alternative How it works 🎯 Overview A comprehensive n8n workflow that analyzes developer workload patterns from GitHub repositories to detect potential software engineering team burnout risks and provide actionable team wellness recommendations. This workflow automatically monitors team activity patterns, analyzes them using AI, and provides professional wellness reports with actionable recommendations which will automate GitHub issue creation and do email notifications for critical alerts. ✨ Features Automated Data Collection**: Fetches commits, pull requests, and workflow data from GitHub Pattern Analysis**: Identifies late-night work, weekend activity, and workload distribution AI-Powered Analysis**: Uses Groq's LLM for professional burnout risk assessment Automated Actions**: Creates GitHub issues and sends email alerts based on criticality Professional Guardrails**: Ensures objective, evidence-based analysis with privacy protection Scheduled Monitoring**: Weekly automated wellness checks 🏗️ Architecture Data Collection Layer GitHub Commits API**: Fetches commit history and timing data GitHub Pull Requests API**: Analyzes collaboration patterns GitHub Workflows API**: Monitors CI/CD pipeline health Pattern Analysis Engine Work Pattern Signals**: Late-night commits, weekend activity Developer Activity**: Individual contribution analysis Workflow Health**: Pipeline success/failure rates Collaboration Metrics**: PR review patterns and merge frequency AI Analysis Layer Professional Guardrails**: Objective, evidence-based assessments Risk Assessment**: Burnout risk classification (Low/Medium/High) Health Scoring**: Team wellness score (0-100) Recommendation Engine**: Actionable suggestions for improvement 📊 Sample Output 📊 Team Health Report 📝 Summary Overall, the team is maintaining a healthy delivery pace, but there are emerging signs of workload imbalance due to increased after-hours activity. 🔢 Health Score Value:** 68 / 100 Confidence:** 87% Limitations:** Based solely on commit and PR activity; meeting load and non-code tasks not captured. 🔍 Observed Patterns ⏰ After-hours activity 29% of commits occurred between 10pm–1am (baseline: 12%). Confidence: 0.90 ⚠️ Systemic Risks Sustained after-hours work may indicate creeping burnout risk. Evidence: 3 consecutive weeks of elevated late-night commits. Confidence: 0.85 ✅ Recommendations 📌 Facilitate a team discussion on workload distribution and sprint commitments. (Priority: Medium) 🔔 Introduce automated nudges discouraging late-night commits. (Priority: Low) 🛠️ Rotate PR review responsibilities or adopt lightweight review guidelines. (Priority: High) 🚀 Quick Start Prerequisites n8n instance (cloud or self-hosted) GitHub repository with API access Groq API key Gmail account (optional, for email notifications) Setup Instructions Import Workflow Import the workflow JSON file into your n8n instance Configure Credentials GitHub API: Create a personal access token with repo access Groq API: Get your API key from Groq Console Gmail OAuth2: Set up OAuth2 credentials for email notifications Update Configuration { "repoowner": "your-github-username", "reponame": "your-repository-name", "period": 7, "emailreport": "[email protected]" } Test Workflow Run the workflow manually to verify all connections Check that data is being fetched correctly Verify AI analysis is working Schedule Automation Enable the schedule trigger for weekly reports Set up monitoring for critical alerts 🔧 Configuration Configuration Node Settings repoowner: GitHub username or organization reponame: Repository name period: Analysis period in days (default: 7) emailreport: Email address for critical alerts AI Model Settings Model**: openai/gpt-oss-120b (Groq) Temperature**: 0.3 (for consistent analysis) Max Tokens**: 2000 Safety Settings**: Professional content filtering 📈 Metrics Analyzed Repository-Level Metrics Total commits count Pull requests opened/closed Workflow runs and success rate Failed workflow percentage Work Pattern Signals Late-night commits (10PM-6AM) Weekend commits (Saturday-Sunday) Work intensity patterns Collaboration bottlenecks Developer-Level Activity Individual commit counts Late-night activity per developer Weekend activity per developer Workload distribution fairness 🛡️ Privacy & Ethics Professional Guardrails Never makes personal judgments about individual developers Only analyzes observable patterns in code activity data Always provides evidence-based reasoning for assessments Never suggests disciplinary actions or performance reviews Focuses on systemic issues and team-level recommendations Respects privacy and confidentiality of team members Data Protection No personal information is stored or transmitted Analysis is based solely on public repository data and public data All recommendations are constructive and team-focused Confidence scores indicate analysis reliability There is added redaction prompt. Note that LLM is not deterministic and usually, you will need to refine your own prompt to enhance difference level of criticality of privacy you need censored or displayed. In some cases ,you will need the engineer account names to help identify f2f conversation. 🔄 Workflow Nodes Core Nodes Schedule Trigger: Weekly automation (configurable) Config: Repository and email configuration Github Get Commits: Fetches commit history Github Get Workflows: Retrieves workflow runs Get Prs: Pulls pull request data Analyze Patterns Developer: JavaScript pattern analysis AI Agent: Groq-powered analysis with guardrails Update Github Issue: Creates wellness tracking issues Send a message in Gmail: Email notifications Data Flow Schedule Trigger → Config → Github APIs → Pattern Analysis → AI Agent → Actions 🚨 Alert Levels (Optional and Prompt configurable) Critical Alerts (Health Score < 90) GitHub Issue**: Automatic issue creation with detailed analysis Email Notification**: Immediate alert to team leads Slack Integration**: Critical team notifications Warning Alerts (Health Score 90-95) GitHub Issue**: Tracking issue for monitoring Slack Notification**: Team awareness message Normal Reports (Health Score > 95) Weekly Report**: Comprehensive team health summary Slack Summary**: Positive reinforcement message 🔧 Troubleshooting Common Issues GitHub API Rate Limits Solution: Use authenticated requests, implement rate limiting Check: API token permissions and repository access AI Analysis Failures Solution: Verify Groq API key, check model availability Check: Input data format and prompt structure Email Notifications Not Sending Solution: Verify Gmail OAuth2 setup, check email permissions Check: SMTP settings and authentication Workflow Execution Errors Solution: Check node connections, verify data flow Check: Error logs and execution history 🤝 Contributing Development Setup Fork the repository link above demo part Create a feature branch Make your changes Test thoroughly Submit a pull request Testing Test with different repository types Verify AI analysis accuracy Check alert threshold sensitivity Validate email and GitHub integrations 📄 License This project is licensed under the MIT License 🙏 Acknowledgments Groq**: For providing the AI analysis capabilities GitHub**: For the comprehensive API ecosystem n8n**: For the powerful workflow automation platform Community**: For feedback and contributions 📞 Support Getting Help Issues**: Create a GitHub issue for bugs or feature requests Discussions**: Use GitHub Discussions for questions Documentation**: Check the comprehensive setup guides Contact Email**:[email protected] LinkedIn**: SeanLon ⚠️ Important: This tool is designed for team wellness monitoring and should be used responsibly. Always respect team privacy and use the insights constructively to improve team health and productivity.

Create Evergreen Content with GitHub Dynamic Images & URL Redirects

Transform static digital assets into dynamic, self-updating powerhouses that stay relevant for years to come! This workflow solves a common problem: once you publish forms, emails, or templates, their content becomes frozen in time. Users discovering them months later see outdated information, missed opportunities, and stale offers. Stop losing opportunities to stale content – make your digital assets work harder and stay fresher, automatically! Here's how it works: 🔗 Stable embed links mean your original assets never need updating 🔄 Dynamic URL redirects that automatically point to the latest pages 🖼️ Auto-updating images that showcase fresh offers or content 📅 Scheduled updates keep everything current without manual intervention Perfect for: Workflow sticky notes that become evergreen marketing billboards Registration forms with current promotions Email signatures with latest offers Website banners that stay seasonally relevant Any digital asset you want to "future-proof" The magic: Set it up once, embed the stable URLs/images in your content, then forget about it. Years later, users will still see fresh, as current information automatically pulled from your workflow. Requirements: Free accounts with GitHub (image storage) and shorten.rest (URL redirects). Both can be swapped for your preferred services. Follow me on LinkedIn for more tips on AI automation and n8n workflows!

Sync GitHub Workflows to n8n After Pull Request Merges

Who is this for? This template is ideal for developers, DevOps engineers, and automation managers who manage their n8n workflows using GitHub. It helps teams streamline their CI/CD automation by syncing changes from GitHub directly into n8n after a pull request (PR) is merged. What problem is this workflow solving? Manually restoring workflows after reviewing and merging code in GitHub can be tedious and error-prone. This workflow solves that by automating the restore process, ensuring that any new or updated workflow committed to your GitHub repo is automatically imported into your n8n environment. What this workflow does Triggers when a GitHub pull request is closed and merged. Fetches the details of the merge commit. Retrieves the list of added and modified workflow files. Downloads and decodes each workflow file. Creates or updates** the corresponding workflow in your n8n instance automatically. Setup Connect GitHub: Use the GitHub Trigger node and configure GitHub API credentials. Note: I'd recommended to use GitHub PAT (Personal Access Token) classic with repo and admin:repo_hook permission scopes enabled. Connect n8n API: Provide your n8n API credentials in the n8n nodes. - Check this doc Set repository variables: Update github_owner and repo_name in the Define Local Variables node. Enable webhook: Make sure your GitHub repository has a webhook for pull_request events pointing to this workflow. How to customize this workflow to your needs Modify filters to handle only certain branches or file paths. Add Slack or email notifications to confirm successful imports. Insert logging or version tagging for better traceability. Extend with conditional logic for workflow testing before applying changes. This automated flow provides a seamless CI/CD loop between GitHub and n8n, empowering teams to manage workflow versioning efficiently and securely.

WordPress context backup to github

This template can backup WordPress context github。

+5

Building RAG Chatbot for Movie Recommendations with Qdrant and Open AI

Create a recommendation tool without hallucinations based on RAG with the Qdrant Vector database. This example is based on movie recommendations on the IMDB-top1000 dataset. You can provide your wishes and your "big no's" to the chatbot, for example: "A movie about wizards but not Harry Potter", and get top-3 recommendations. How it works a video with the full design process Upload IMDB-1000 dataset to Qdrant Vector Store, embedding movie descriptions with OpenAI; Set up an AI agent with a chat. This agent will call a workflow tool to get movie recommendations based on a request written in the chat; Create a workflow which calls Qdrant's Recommendation API to retrieve top-3 recommendations of movies based on your positive and negative examples. Set Up Steps You'll need to create a free tier Qdrant Cluster (Qdrant can also be used locally; it's open-sourced) and set up API credentials You'll OpenAI credentials You'll need GitHub credentials & to upload the IMDB Kaggle dataset to your GitHub.

Build your own Github MCP server

This n8n demonstrates how to build your own Github MCP server to personalise it to your organisation's repositories, issues and pull requests. This n8n implementation, though not as fully featured as the official MCP server offered by Github, allows you to control precisely what access and/or functionality is granted to users which can make MCP use simpler and in some cases, more secure. The use-case in this template is to simply view and comment on issues within a specific repository but can be extended to meet the needs of your team. This MCP example is based off an official MCP reference implementation which can be found here https://github.com/modelcontextprotocol/servers/tree/main/src/github How it works A MCP server trigger is used and connected to 3 custom workflow tools. We're using custom workflow tools as there is quite a few nodes required for each task. Behind these tools are regular Github nodes although preconfigured with credentials and targeted repository. The "Get Issue Comments" and "Create Issue Comment" tools depend on obtaining an Issue Number first. The agent should call the "Get Latest Issues" tool for this. How to use This Github MCP server allows any compatible MCP client to view and comment on Github Issues. You will need to have a Github account and repository access available before you can use this server. Connect your MCP client by following the n8n guidelines here - https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-langchain.mcptrigger/#integrating-with-claude-desktop Try the following queries in your MCP client: "Can you get me the latest issues about MCP?" "What is the current progress on Issue 12345?" "Please can you add a comment to Issue 12345 that they should try installing the latest version and see if that works?" Requirements Github for account and repository access. The repository need not be your own but you'll still need to ensure you have the correct permissions. MCP Client or Agent for usage such as Claude Desktop - https://claude.ai/download Customising this workflow Extend this template to interactive with pull requests or workflows within your own company's Github repositories. Alternatively, pull in metrics and generate reports for programme managers. Remember to set the MCP server to require credentials before going to production and sharing this MCP server with others!

+5

Create a Code Assistant that Learns from your GitHub Repository using OpenAI

AI Agent for GitHub AI Agent to learn directly from your GitHub repository. It automatically syncs source files, converts them into vectorized knowledge How It Works Provide your GitHub repository — the workflow will automatically pull your source files and update the knowledge base (vectorstore) for the AI Agent. This allows the AI Agent to answer questions directly based on your repository’s content. How to Use Commit your files to your GitHub repository. Trigger the Sync Data workflow. Ask questions to the AI Agent — it will respond using your repository knowledge. Requirements A valid GitHub account An existing repository with accessible content Customization Options Customize the prompt for specific or detailed tasks Replace or connect to your own vector database provider

AI-Powered Knowledge Assistant using Google Sheets, OpenAI, and Supabase Vector Search

AI-Powered GitHub Commit Reviewer Overview Workflow Name: AI-Powered GitHub Commit Reviewer Author: Akhil Purpose: This n8n workflow triggers on a GitHub push event, fetches commit diffs, formats them into HTML, runs an AI-powered code review using Groq LLM, and sends a detailed review via email. How It Works (Step-by-Step) GitHub Trigger Node Type**: n8n-nodes-base.githubTrigger Purpose**: Initiates the workflow on GitHub push events. Repo**: akhilv77/relevance Output**: JSON with commit and repo details. Parser Node Type**: n8n-nodes-base.set Purpose**: Extracts key info (repo ID, name, commit SHA, file changes). HTTP Request Node Type**: n8n-nodes-base.httpRequest Purpose**: Fetches commit diff details using GitHub API. Auth**: GitHub OAuth2 API. Code (HTML Formatter) Node Type**: n8n-nodes-base.code Purpose**: Formats commit info and diffs into styled HTML. Output**: HTML report of commit details. Groq Chat Model Node Type**: @n8n/n8n-nodes-langchain.lmChatGroq Purpose**: Provides the AI model (llama-3.1-8b-instant). Simple Memory Node Type**: @n8n/n8n-nodes-langchain.memoryBufferWindow Purpose**: Maintains memory context for AI agent. AI Agent Node Type**: @n8n/n8n-nodes-langchain.agent Purpose**: Executes AI-based code review. Prompt**: Reviews for bugs, style, grammar, and security. Outputs styled HTML. Output Parser Node Type**: n8n-nodes-base.code Purpose**: Combines commit HTML with AI review into one HTML block. Gmail Node Type**: n8n-nodes-base.gmail Purpose**: Sends review report via email. Recipient**: [email protected] End Workflow Node Type**: n8n-nodes-base.noOp Purpose**: Marks the end. Customization Tips GitHub Trigger**: Change repo/owner or trigger events. HTTP Request**: Modify endpoint to get specific data. AI Agent**: Update the prompt to focus on different review aspects. Groq Model**: Swap for other supported LLMs if needed. Memory**: Use dynamic session key for per-commit reviews. Email**: Change recipient or email styling. Error Handling Use Error Trigger nodes to handle failures in: GitHub API requests LLM generation Email delivery Use Cases Instant AI-powered feedback on code pushes. Pre-human review suggestions. Security and standards enforcement. Developer onboarding assistance. Required Credentials | Credential | Used By | Notes | |-----------|---------|-------| | GitHub API (ID PSygiwMjdjFDImYb) | GitHub Trigger | PAT with repo and admin:repo_hook | | GitHub OAuth2 API | HTTP Request | OAuth2 token with repo scope | | Groq - Akhil (ID HJl5cdJzjhf727zW) | Groq Chat Model | API Key from GroqCloud | | Gmail OAuth2 - Akhil (ID wqFUFuFpF5eRAp4E) | Gmail | Gmail OAuth2 for sending email | Final Note Made with ❤️ using n8n by Akhil.

Automated Workflow Backups to GitHub with PR Creation & Slack Notifications

Who is this for? This template is ideal for DevOps engineers, automation specialists, and n8n users who manage multiple workflows and want a reliable version control system for backups. It’s especially useful for teams collaborating via GitHub. What problem is this workflow solving? Manually backing up n8n workflows to GitHub can be time-consuming and error-prone. This workflow solves that by automating the backup of new and updated n8n workflows, ensuring your GitHub repository always reflects the latest changes. What this workflow does Retrieves all workflows from your local n8n instance. Decodes their content and compares it with existing GitHub files. Detects newly created or updated workflows. Creates a new Git branch and commits changes. Opens a pull request (PR) to the main branch. Sends a Slack notification when the PR is created. The system uses GitHub API, n8n, Merge, Set, and Slack nodes for full automation. Setup GitHub credentials: Add your GitHub API credentials in n8n. Slack integration: Connect your Slack Bot token if you want PR notifications. Repository details: Update github_owner, repo_name, and workflow directory path in the “Define Local Variables” node. n8n API key - Check this doc How to customize this workflow to your needs Change the workflow directory from workflows/ to a custom path. Modify the Slack message or add email notification support. Add filters to back up only specific workflows based on naming or tags. Adjust branch naming conventions or use different GitHub base branches. This workflow provides a seamless backup and versioning pipeline, minimizing manual Git interactions and supporting collaborative automation development.

Automatically document and backup N8N workflows

Automatically backs up your workflows to Github and generates documentation in a Notion database. Weekly run, uses the "internal-infra" tag to look for new or recently modified workflows Uses a Notion database page to hold the workflow summary, last updated date, and a link to the workflow Uses OpenAI's 4o-mini to generate a summarization of what the workflow does Stores a backup of the workflow in GitHub (recommend a private repo) Sends notification to Slack channel for new or updated workflows Who is this for Anyone seeking backup of their most important workflows Anyone seeking version control for their most important workflows Credentials required N8N: You will need an N8N credential created so the workflow can query the N8N instance to find all active workflows with the "internal-infra" tag Notion: You will need an Notion credential created OpenAI: You will need an OpenAI credential, unless you intend on rewiring this with your AI of choice (ollama, openrouter, etc.) GitHub: You will need an GitHub credential Slack: You will require an Slack credential, recommend a Bot / access token configuration Setup Notion Create a database with the following columns. Column type is specified in [type]. Workflow Name [text] isActive (dev) [checkbox] Error workflow setup [checkbox] AI Summary [text] Record last update [date/time] URL (dev) [text/url] Workflow created at [date/time] Workflow updated at [date/time] Slack Create a channel for updates to be posted into Github Create a private repo for your workflows to be exported into N8N Download & install the template Configure the blocks to use your N8N, Notion, OpenAI & Slack credentials for your own Edit the "Set Fields" block and change the URL to that of your N8N instance (cloud or self-hosted) Edit the "Add to Notion" action and specify the Database page you wish to update Edit the Slack actions to specify the Channel you want slack notifications posted to Edit the GitHub actions to specify the Repository Owner & Repository Name Sample output in Notion Workflow diagram

Backup your workflows to GitHub -- in (subfolders)

Based on Jonathan & Solomon work. > The only addition I've made is a Set node. This node organizes workflows into subfolders within the GitHub repository based on their respective tags. How it works This workflow will backup your workflows to GitHub. It uses the n8n API node to export all workflows. It then loops over the data, checks in GitHub to see if a file exists that uses the credential's ID. Once checked it will: update the file on GitHub if it exists; create a new file if it doesn't exist; ignore if it's the same. Who is this for? People wanting to backup their workflows outside the server for safety purposes or to migrate to another server.

Backup your workflows to GitHub

Based on Jonathan's work. Check out his templates. How it works This workflow will backup your workflows to GitHub. It uses the n8n API node to export all workflows. It then loops over the data, checks in GitHub to see if a file exists that uses the credential's ID. Once checked it will: update the file on GitHub if it exists; create a new file if it doesn't exist; ignore if it's the same. Who is this for? People wanting to backup their workflows outside the server for safety purposes or to migrate to another server. Check out my other templates 👉 https://n8n.io/creators/solomon/

Back up and restore n8n workflows with GitHub sync

n8n Workflows GitHub Manager > A comprehensive n8n workflow that provides complete bidirectional sync between your n8n instance and GitHub - automatically backs up all your workflows with intelligent change detection AND restores them when needed. This workflow combines two powerful features in one: Backup**: Automatically detects new, edited, renamed, and deleted workflows in your n8n instance, then syncs them to GitHub with smart commit messages and an index tracking system. Restore**: Easily restore all workflows from your GitHub repository back to n8n - perfect for disaster recovery, new instance setup, or environment cloning. How It Works 🔄 Backup Mode (Automatic) Trigger: Runs automatically every day at 7 PM UTC (or manually when triggered via the Schedule Trigger). Get/Create Index: Attempts to fetch index.json from your GitHub repository. If found → Downloads and parses it. If not found → Creates a new empty index file and waits 3 seconds for GitHub to process. Fetch All Workflows: Retrieves all workflows from your n8n instance via the n8n API. Smart Comparison: The "C,E,D Checker" (Create, Edit, Delete) analyzes differences: CREATE → New workflow not in index. RENAME → Workflow name changed (deletes old file, creates new one). EDIT → Existing workflow (flagged for content comparison). DELETE → Workflow removed from n8n but still in GitHub. INDEX UPDATE → Triggered if any changes detected. Route Actions: Switch node routes each action to the appropriate branch: Create Branch → Creates new workflow files in GitHub. Edit Branch → Performs smart edit detection: Fetches current file from GitHub. Compares GitHub version vs. n8n version (normalized JSON). Only commits if content actually changed (avoids timestamp-only updates). Delete Branch → Removes workflow files from GitHub. Update Index Branch → Updates index.json with latest mappings. Commit Messages: Auto-generated with format: [Workflow Name] (Action) YYYY-MM-DD ⬇️ Restore Mode (Manual) Trigger: Manually execute via the "When clicking 'Execute workflow'" manual trigger. Set GitHub Details: Configure your repository owner and name. List Workflow Files: Fetches all workflow JSON files from the workflows/ folder in your GitHub repository. If folder not found → Workflow stops gracefully (ensure backup ran at least once first). Loop Through Files: Sequentially processes each workflow file: Downloads the JSON content from GitHub. Creates the workflow in your n8n instance via the n8n API. Sequential Processing: Handles one workflow at a time to prevent conflicts and respect rate limits. Result: All workflows from GitHub are restored to your n8n instance. Requirements GitHub OAuth2 Credentials**: Go to GitHub Developer Settings → OAuth Apps → New OAuth App. Set Authorization callback URL to your n8n instance URL (e.g., https://your-n8n.com/rest/oauth2-credential/callback). Copy Client ID and Client Secret. Add as OAuth2 credential in n8n (Credentials → New → GitHub OAuth2). GitHub Repository**: Create a new repository (public or private). Note your username (repo owner) and repository name. n8n API Credentials**: In your n8n instance → Settings → API → Create new API key. Add as n8n API credential in the workflow. How to Use Initial Setup Import the Workflow: Copy the provided JSON file. In your n8n instance → click Import Workflow → paste or upload the JSON. Create GitHub Repository: Go to GitHub → Create a new repository (e.g., n8n-workflows-manager). Leave it empty (no README, no .gitignore). Set Up GitHub OAuth2: In n8n → Credentials → New → GitHub OAuth2. Fill in: Client ID → from GitHub OAuth App. Client Secret → from GitHub OAuth App. Click Connect my account and authorize. Set Up n8n API Credentials: In n8n → Settings → API → Create new API key. Copy the key. In workflow → Credentials → New → n8n API → paste the key. Set Base URL to your n8n instance (e.g., https://your-n8n.com). Configure Repository Details: Find both "Set Github Data" nodes in the workflow (one for backup, one for restore). Edit the assignments in each: repo_owner: Replace "your-github-username" with your GitHub username. repo_name: Replace "your-github-repository-name" with your repository name. Connect Credentials to Nodes: Open each GitHub node (there are 8 total): Backup section: Create Index File, Get Download Url for Index File, Create New Files, Update Index File, Get Download Url for Github File, Delete Files, Edit Files Restore section: List Workflow Files Set Credential for GitHub OAuth2 to the one you created. Open the n8n API nodes (Get All Workflows, Create Workflow) → Set Credential for n8n API to the one you created. Using Backup Mode Test Backup: Click the "Schedule Trigger" node at the top of the workflow. Click "Test workflow". Monitor execution → All nodes in the backup section should turn green. Check your GitHub repository → Should see index.json and workflows/ folder with your workflows. Activate for Auto Backup: Once tested successfully, toggle the workflow to Active. It will now run automatically every day at 7 PM UTC. Using Restore Mode Test Restore (only after you have backups in GitHub): Click the "When clicking 'Execute workflow'" manual trigger node at the bottom. Click "Test workflow". Monitor execution → All nodes in the restore section should turn green. Check your n8n workflows list → All workflows from GitHub should now be present. When to Use Restore: Setting up a new n8n instance. Recovering after data loss. Cloning workflows to another environment. Rolling back to a previous state (manually download older commits from GitHub first). Important Notes Smart Edit Detection**: Uses normalized JSON comparison to avoid unnecessary commits when only timestamps change. Credentials**: Credential IDs are included but not actual secrets. You must reconnect credentials after restore. Restored Workflows: Created as new workflows with new IDs in **inactive state by default. File Structure**: index.json tracks all workflows; workflows/ folder contains individual workflow files. Security**: Use a private repository if workflows contain sensitive data. Credential secrets are never backed up. Customization Change Schedule**: Edit "Schedule Trigger" node → modify triggerAtHour (default: 19 = 7 PM UTC) File Path**: Modify filePath in GitHub nodes to change storage location Notifications**: Add email/notification nodes to get alerts on backup completion Selective Restore**: Add IF nodes to filter which workflows to restore Multiple Repos**: Duplicate workflow for separate prod/dev backups Author: Muhammad Anas Farooq

Automated Website Uptime Monitor with Email Alerts & GitHub Status Page Update

🖥️ Automated Website Uptime Monitor with Email Alerts & GitHub Status Page Update This n8n workflow continuously monitors your website’s availability, sends email alerts when the server goes down, and automatically updates a status page (index.html) in your GitHub repository to reflect the live status. 📌 Good to Know The workflow checks your website every 2 minutes (interval configurable). If the website is down (503, bad response, or error) → it sends an email alert and updates the GitHub-hosted status page to show Down. If the website is up (200) → it updates the GitHub-hosted status page to show Up. The email notification includes an HTML-formatted alert page. You can use GitHub Pages to host the status page publicly. ℹ️ What is GitHub Pages? GitHub Pages is a free hosting service provided by GitHub that lets you publish static websites (HTML, CSS, JS) directly from a GitHub repository. You can use it to make your index.html status page publicly accessible with a URL like: ⚡ How to Set Up GitHub Pages for Your Status Page Create a new repository on GitHub (recommended name: status). Add a blank index.html file (n8n workflow will later update this file). Go to your repository → Settings → Pages. Under Source, select the branch (main or master) and folder (/root). Save changes. Your status page will now be live at: https://<USERNAME>.github.io/status ✅ Prerequisites An n8n instance (self-hosted or cloud). A GitHub account & repository (to host the status page). A Gmail account (or any email service supported by n8n – example uses Gmail). Access to the target website URL you want to monitor. ⚙️ How it Works Schedule Trigger → Runs every 2 minutes. HTTP Request → Pings your website URL. Switch Node → Evaluates the response status (200 OK vs error/503). Code Node → Generates a dynamic HTML status page (Up/Down). GitHub Repo & File → Github Repo Name Should be https://github.com/<OWNER_NAME>/status (recommended) & Must have(required) a blank file named as index.html before triggering this flow. GitHub Node → Updates/commits the index.html file in your repository. Gmail Node → Sends an email alert if the site is down. 🚀 How to Use Import the workflow JSON into your n8n instance. Configure credentials for: GitHub (Personal Access Token with repo permissions). Gmail (or your preferred email service). Replace the following: https://app.yourdomain.com/health → with your own website URL. [email protected] → with your email address (or distribution list). GitHub repo details → with your repository where index.html will live. Deploy the workflow. (Optional) Enable GitHub Pages on your repo to serve index.html as a live status page. 🛠 Requirements n8n v1.0+ GitHub personal access token Gmail API credentials (or SMTP/email service of your choice) 🎨 Customising this Workflow Interval** → Change schedule from 2 minutes to any desired frequency. Email Content** → Modify HTML alert template in the Gmail node. Status Page Styling** → Edit the HTML/CSS in the Code node to match your branding. Error Handling** → Extend Switch node for other status codes (e.g., 404, 500). Multiple Websites** → Duplicate HTTP Request + Switch nodes for multiple URLs. 👤 Who Can Use It? DevOps & SRE Engineers** → For automated uptime monitoring. Freelancers/Developers** → To monitor client websites. Startups & SMEs** → For a free, lightweight status page without paid tools. Educators/Students** → As a hands-on learning project with n8n. 🌟 Key Features 🔄 Automated uptime checks (configurable interval). 📧 Email notifications on downtime. 📝 Dynamic HTML status page generation. 🌍 GitHub Pages integration for public visibility. ⚡ Lightweight & cost-effective (no paid monitoring tool needed). 🔗 Tools Integration n8n** – Orchestration & automation. GitHub** – Version control + hosting of status page. Gmail** – Email notifications. HTTP Request** – Website availability check. 📈 Example Use Cases Personal website monitoring with public status page. Monitoring SaaS apps & notifying support teams. Internal company services uptime dashboard.

GitHub Fork Status Monitor

This workflow helps you keep an eye on your GitHub forks, notifying you when they fall behind or pull ahead of their upstream repositories. How It Works Fetches All Your Repos: The workflow starts by grabbing a list of all repositories owned by your GitHub account. Filters for Forks: It then intelligently filters this list to identify only your forked repositories. Compares Branches: For each identified fork, it compares its default branch against the upstream repository's default branch to find out how many commits it's ahead or behind. Filters for Changes: Only forks that are either ahead or behind their upstream (i.e., not perfectly in sync) are processed further. Generates Report: A concise, well-formatted report is compiled, highlighting the status and commit differences for each relevant fork. Sends Telegram Notification: Finally, this report is sent directly to your Telegram chat, keeping you informed in real-time. Setup Steps Copy the template Update triggers ( optional ) Update the credentials Prerequisites GitHub Credentials**: You'll need to provide your GitHub personal access token for the "Get All Repositories" and "Compare Branches API Call" nodes. Telegram Bot Setup**: Configure a Telegram Bot and obtain its API token and your chat ID for the "Send Report" node. Github Owner Username**: Update the "Get All Repositories" node with the GitHub username of the repository owner whose forks you want to monitor. Explore & Fine-Tune: All detailed instructions and explanations, including how to adjust the filtering logic or output formatting, are provided in sticky notes directly within the workflow canvas.

Restore your credentials from GitHub

This workflow restores all n8n instance credentials from GitHub backups using the n8n API node. It complements the Backup Your Credentials to GitHub template by allowing users to seamlessly restore previously saved credentials. How It Works The workflow fetches credentials stored in a GitHub repository and imports them into your n8n instance. Setup Instructions To configure the workflow, update the Globals node with the following values: repo.owner** – Your GitHub username repo.name** – The name of your GitHub repository storing the credentials repo.path** – The folder path within the repository where credentials are stored For example, if your GitHub username is john-doe, your repository is named n8n-backups, and credentials are stored in a credentials/ folder, you would set: repo.owner → john-doe repo.name → n8n-backups repo.path → credentials/ Required Credentials GitHub API** – Access to your repository n8n API** – To import credentials into your n8n instance Who Is This For? This template is ideal for users who want to restore their credentials from GitHub backups, ensuring easy migration and recovery in case of data loss. Check out my other templates: 👉 My n8n Templates

Restore your workflows from GitHub

This workflow restores all n8n instance workflows from GitHub backups using the n8n API node. It complements the Backup Your Workflows to GitHub template by allowing users to seamlessly restore previously saved workflows. How It Works The workflow fetches workflows stored in a GitHub repository and imports them into your n8n instance. Setup Instructions To configure the workflow, update the Globals node with the following values: repo.owner** – Your GitHub username repo.name** – The name of your GitHub repository storing the workflows repo.path** – The folder path within the repository where workflows are stored For example, if your GitHub username is john-doe, your repository is named n8n-backups, and workflows are stored in a workflows/ folder, you would set: repo.owner → john-doe repo.name → n8n-backups repo.path → workflows/ Required Credentials GitHub API** – Access to your repository n8n API** – To import workflows into your n8n instance Who Is This For? This template is ideal for users who want to restore their workflows from GitHub backups, ensuring easy migration and recovery in case of data loss. Check out my other templates: 👉 My n8n Templates

Backup your credentials to GitHub

Based on Jonathan's work. Check out his templates. This workflow will backup your credentials to GitHub. It uses a CLI command to export all credentials. It then loops over the data, checks in GitHub to see if a file exists that uses the credential's ID. Once checked it will: update the file on GitHub if it exists; create a new file if it doesn't exist; ignore if it's the same. Config Options repo.owner - Github owner repo.name - Github repository name repo.path - Path within the Github repository ⚠ The credentials are all decrypted. Make sure you save them safely or tweak the CLI command to store them encrypted.== Check out my other templates 👉 https://n8n.io/creators/solomon/

Back Up Your n8n Workflows To Github

This workflow will backup your workflows to Github. It uses the public api to export all of the workflow data using the n8n node. It then loops over the data checks in Github to see if a file exists that uses the workflow name. Once checked it will then update the file on Github if it exists, Create a new file if it doesn't exist and if it's the same it will ignore the file. Config Options repo_owner - Github owner repo_name - Github repository name repo_path - Path within the Github repository >This workflow has been updated to use the n8n node and the code node so requires at least version 0.198.0 of n8n

Review GitHub pull requests with AI and log results to PostgreSQL and Slack

Automatically detects new GitHub Pull Requests, analyzes changed code with AI, generates detailed review comments (quality, security, performance, best practices), posts suggestions back to the PR, stores results in a database, and sends notifications. Good to Know Triggers automatically on new/updated GitHub Pull Requests via webhook (or manual test) Fetches only changed files/diffs — no need to clone full repo Uses AI (Grok, OpenAI, Claude, Gemini, etc.) to provide intelligent, context-aware feedback Covers multiple dimensions: code quality, bugs, security vulnerabilities, performance issues, maintainability, style/best practices Posts formatted review comments directly on the GitHub PR (with severity levels, suggestions, code snippets) Stores review history & scores in PostgreSQL (or other DB) for auditing, metrics, team dashboards Sends real-time notifications (Slack, Discord, email, etc.) for high-severity findings Saves developers hours on initial reviews and catches issues early How It Works Trigger PR Detection GitHub Webhook** node — listens for pull_request events (opened, synchronize, reopened, ready_for_review) Optional: Filter node to ignore drafts, dependabot PRs, or specific branches Manual trigger available for testing Fetch & Analyze Code GitHub** node — retrieves PR details (title, body, number, repo, base/head commits) GitHub* or HTTP Request* — fetches list of changed files + diffs (using GitHub API /pulls/{number}/files and diff content) Merge PR Details & Extract Diffs** — combines metadata + code changes into structured format Prepares payload: file paths, diff hunks, full file content if needed (truncated for large files) AI Review & Score Sends prepared diff data + context (language, repo conventions, custom guidelines) to AI model Prompt engineering focuses on: Code correctness & bugs Security vulnerabilities (OWASP, secrets, injection risks) Performance optimizations Readability, maintainability, SOLID principles Best practices & style (specific to language/framework) Refactoring suggestions with examples AI returns structured output: severity (low/medium/high/critical), category, comment text, suggested fix (with code block) Optional: Score node — assigns overall PR quality score (0–100) based on findings Post Review & Notify Route** by severity / issue count (e.g. critical → immediate Slack) GitHub** node — posts detailed review comments on the PR (as bot user) Supports threaded replies, line-specific comments (if hunk positions available) Adds label e.g. ai-reviewed, needs-changes Store Results in PostgreSQL** — logs full review (PR link, timestamp, AI output JSON, score, issues list) Send Summary to Slack** (or Discord/Email/Telegram) — concise message with key findings, link to PR, severity highlights Log Completion** — records successful execution for monitoring Data Sources GitHub** — Pull Requests, diffs, comments, labels (via webhook + API) AI Model** — Grok (xAI), OpenAI GPT-4o / o1, Anthropic Claude, Google Gemini, or local LLM Storage** — PostgreSQL (recommended for structured querying), or Supabase, Airtable, Google Sheets Notifications** — Slack, Discord, Microsoft Teams, Email (SMTP), Telegram How to Use Import the workflow JSON into your n8n instance Configure credentials: GitHub OAuth / Personal Access Token (with repo scope) AI provider API key (Grok/OpenAI/etc.) PostgreSQL database connection Slack/Discord/Email credentials Set up GitHub Webhook: In repo Settings → Webhooks → Add webhook Payload URL = your n8n webhook URL Content type: application/json Events: Pull requests Customize AI prompt — add repo-specific rules, coding standards, ignored patterns Tune filters — minimum severity to post, files to skip (e.g. lock files, generated code) Test — create/open a small PR or use Execute Workflow with sample payload Activate — turn on the workflow and monitor Executions + Logs Requirements n8n (self-hosted preferred for webhooks) GitHub repo with admin access to add webhook & bot token AI API access with sufficient token limit (large PRs = large prompts) PostgreSQL database (or alternative) for persistent storage Notification service account (Slack app, Discord bot, etc.) Customizing This Workflow Add custom best practices** — load from Google Sheets/Notion/Airtable and inject into prompt Support multi-file analysis** — chunk very large PRs or summarize per-file first Auto-approve low-risk PRs** — add approval action if score > 90 and no critical issues Security focus** — integrate with tools like Semgrep/Trivy results Comment on specific lines** — use GitHub API position/hunk data for inline comments Team routing** — notify language-specific experts via Slack channels Metrics dashboard** — connect DB to Grafana/Metabase for review trends Ignore patterns** — skip vendor/, node_modules/, tests/, etc. Multiple AI models** — fallback or ensemble (e.g. Claude for reasoning + Grok for speed)

Send pre-meeting Slack briefings using Google Calendar, Notion, GitHub, and Jira

This n8n template from Intuz provides a complete and automated solution for preparing and delivering context-rich briefings directly to attendees before every meeting. It acts as an AI-powered executive assistant, gathering relevant information from all your key work tools to ensure everyone arrives prepared and aligned. Who's this workflow for? Engineering Managers & Team Leads Product Managers & Project Managers Scrum Masters & Agile Coaches Any team that holds regular status, planning, or technical meetings. How it works Trigger on New Calendar Event: The workflow starts automatically whenever a new meeting is created in a designated Google Calendar. Fetch Previous Context: It immediately connects to Notion to retrieve the notes from the most recent past meeting, ensuring continuity. Wait for the Right Moment: The workflow calculates a time 15 minutes before the meeting's scheduled start and pauses its execution until then. Gather Real-Time Project Data: Just before the meeting, the workflow wakes up and: Extracts keywords from the meeting title. Searches GitHub for recent Pull Requests (PRs) relevant to those keywords. Searches Jira for any tickets or issues that match the meeting's topic. Build the Intelligent Briefing: It assembles all the gathered information—previous notes from Notion, current PRs from GitHub, and relevant tickets from Jira—into a single, beautifully formatted Slack message. Deliver to Each Attendee: The workflow identifies all attendees from the Google Calendar invite, finds their corresponding Slack profiles via email, and sends the personalized briefing as a Direct Message (DM) to each one, ensuring everyone is prepared just in time. Key Requirements to Use This Template n8n Instance: An active n8n account (Cloud or self-hosted). Google Calendar Account: To trigger the workflow on new events. Notion Account: With a dedicated database for storing meeting notes. GitHub Account: To search for relevant pull requests. Jira Cloud Account: To search for relevant project tickets. Slack Workspace & App: A Slack workspace where you have permission to install an app. You will need a Bot Token with the necessary permissions. Setup Instructions Google Calendar Trigger: In the "Capture New Google Calendar Event" node, connect your Google Calendar account and select the calendar you want to monitor. Notion Connection: In the "Get Last Meeting Notes" node, connect your Notion account. Select the Notion Database ID that contains your meeting notes. GitHub & Jira Connections: In the "Get PRs from Repo" node, connect your GitHub account and select the repository to search. In the "Get Jira Issues Related to Meeting" node, connect your Jira Cloud account. You can customize the JQL query if needed. Slack Configuration (Crucial Step): Create a Slack App: Go to api.slack.com/apps, create a new app, and install it to your workspace. Set Permissions: In your app's "OAuth & Permissions" settings, add the following Bot Token Scopes: chat:write (to send messages) and users:read.email (this is critical for looking up attendees). Reinstall the app to your workspace. Get Bot Token: Copy the "Bot User OAuth Token" (it starts with xoxb-). Connect in n8n: In the "Get User Slack Info from Email" node, click "Header Parameters" and replace {{ slack oauth token }} with your actual Bot Token. In the "Send Meeting Context in Slack DM" node, connect your Slack credentials using the same Bot Token. Activate the Workflow: Save the workflow and toggle the "Active" switch to ON. Your automated pre-meeting bot is now live! Connect with us Website: https://www.intuz.com/n8n-workflow-automation-templates Email: [email protected] LinkedIn: https://www.linkedin.com/company/intuz Get Started: https://n8n.partnerlinks.io/intuz For Custom Workflow Automation Click here: Get Started

Process incoming files and notify via email with GitHub storage

File Processing Pipeline with Email and GitHub This workflow automatically ingests newly-uploaded files, validates and transforms their contents, stores the processed files in a GitHub repository, and sends email notifications upon completion. It is ideal for teams that regularly receive data drops and need an auditable, automated pipeline to clean, version, and distribute those files. Pre-conditions/Requirements Prerequisites n8n instance (self-hosted or n8n cloud) GitHub and SMTP credentials with appropriate permissions Basic understanding of JavaScript for custom validation/transform code Required Credentials | Credential | Purpose | Minimum Scope | |------------|---------|---------------| | GitHub OAuth2 | Commit transformed files to a repository | repo | | SMTP (Email Send) | Dispatch success/failure notifications | send | Repository & Email Setup Requirements | Item | Example | Notes | |------|---------|-------| | GitHub Repository | [email protected]:org/data-pipeline.git | Branch must exist (default: main) | | Email Recipients | [email protected], [email protected] | Comma-separated list | How it works This workflow automatically ingests newly-uploaded files, validates and transforms their contents, stores the processed files in a GitHub repository, and sends email notifications upon completion. It is ideal for teams that regularly receive data drops and need an auditable, automated pipeline to clean, version, and distribute those files. Key Steps: Schedule Trigger**: Executes the pipeline on a defined schedule (e.g., hourly). HTTP Request**: Pulls a file manifest or fetches file blobs from an upstream service. SplitInBatches**: Iterates over each file individually for isolated processing. Code (Validate)**: Runs custom JavaScript to ensure file integrity and schema compliance. If (Validation Pass?)**: Routes good files forward and diverts failures. Code (Transform)**: Performs any data re-formatting, enrichment, or cleansing. Set**: Prepares commit metadata (file path, commit message). GitHub**: Creates or updates a file in the target repository/branch. Email Send**: Notifies stakeholders of overall job status, including summary metrics. Set up steps Setup Time: 10-15 minutes Clone the Workflow: Import the JSON file or copy from the n8n community templates gallery. Configure Schedule Trigger: Set your desired cron expression (e.g., 0 * * * * for hourly). HTTP Request Node: Enter the endpoint that lists or returns your new uploads. Add authentication headers if required. Adjust Validation Code: Open the first Code node and replace the schema rules with your own logic. Modify Transformation Logic: In the second Code node, apply formatting (e.g., CSV → JSON) or enrichment steps. GitHub Node: Select your GitHub OAuth2 credential. Specify repository, branch, and file path template (e.g., processed/{{ $json.filename }}). Email Send Node: Set SMTP credential. Add recipients and customize subject/body with variables. Test Run: Click “Execute Workflow” to ensure end-to-end success. Activate: Toggle workflow to “Active” for autonomous execution. Node Descriptions Core Workflow Nodes: Sticky Note** – Documentation and inline comments for maintainers. Schedule Trigger** – Initiates the automation on a fixed timetable. HTTP Request** – Retrieves incoming file list or contents. SplitInBatches** – Paginates large manifests to conserve memory. Code (Validate / Transform)** – Custom JS powering data quality checks and format conversion. If** – Branching logic for pass/fail handling. Set** – Crafts commit metadata and email summaries. GitHub** – Commits each transformed file to the repository. Email Send** – Dispatches completion notices or error alerts. Data Flow: Schedule Trigger → HTTP Request → SplitInBatches → Code (Validate) → If true → Code (Transform) → Set → GitHub false → Set (Error) Both branches converge → Email Send Customization Examples Custom Validation Rule // Reject files larger than 5 MB or missing required columns if (items[0].binary.data.size > 5 * 1024 * 1024) { throw new Error('File exceeds 5MB limit'); } const required = ['id', 'email', 'created_at']; required.forEach(col => { if (!items[0].json.headers.includes(col)) { throw new Error(Missing column: ${col}); } }); return items; Dynamic Commit Path Based on Date const date = new Date().toISOString().split('T')[0]; // YYYY-MM-DD item.json.gitPath = archive/${date}/${item.json.filename}; return item; Data Output Format The workflow outputs structured JSON data: { "filename": "orders_2023-10-01.csv", "status": "committed", "commitSha": "a1b2c3d4", "linesProcessed": 523, "errors": [] } Troubleshooting Common Issues GitHub authentication error – Ensure OAuth app is approved and the token has repo scope. Email not delivered – Verify SMTP host, port, and that “less secure apps” are allowed (if using Gmail). Performance Tips Batch large manifests (e.g., 100 records) to avoid memory spikes. Enable n8n queue mode for parallel processing on self-hosted instances. Pro Tips: Use environment variables ({{ $env["VAR_NAME"] }}) for endpoints and secrets. Configure branch protection in GitHub to enforce pull requests instead of direct commits. Aggregate success vs. failure counts in the Email body for quick health checks. This is a community n8n workflow template provided “as-is.” Always review and adapt the workflow to meet your security, compliance, and operational requirements.

Monitor backup and sync logs with Google Cloud Storage, GitHub, Gmail, OpenAI, and GLPI

Reliable Backup & Sync Execution Validation (Log-Driven) This workflow monitors filesystem sync and backup jobs by validating their execution logs, not by running or inspecting the jobs themselves. After purchase, you will receive a complete package including: workflow.json** – ready to be imported into n8n Shell script templates (.sh)** – reference sync job templates designed to generate structured logs fully compatible with the workflow Complete setup documentation** – step-by-step guide covering configuration, deployment, and operational requirements How it works (high level) Sync jobs are executed externally using standardized shell templates: rsync_job-Template.sh rclone_job-Template.sh Each job produces one deterministic log file per run Logs are uploaded daily to Google Cloud Storage This workflow runs on a schedule and: Verifies that all expected logs exist for the day (UTC) Optionally inspects their contents Sends alerts if logs are missing or report failures Key design principles Log-driven monitoring** (evidence-based, not assumption-based) One job = one log = one source of truth** No SSH, no server access, no execution coupling** Safe to run in untrusted or restricted environments Logging contract (required) Each log file must contain the following lifecycle events, in order: event=START event=RSYNC_END or event=RCLONE_END event=SUMMARY event=END If the END event is missing, the job is considered failed or interrupted. Configuration Expected jobs and log filenames are defined in sync-jobs.json. This workflow only validates presence and state of logs — it never assumes job success.

Sync Android env config to Gradle files with GitHub and Slack alerts

Environment Config Diff & Propagate for Android Builds This workflow automatically detects changes in the .env.staging file in a GitHub repository and keeps Android configuration files (build.gradle and gradle.properties) in sync.It creates a new Git branch, applies updates safely, opens a pull request and notifies the team on Slack — all without manual effort. Whenever .env.staging changes: The workflow detects the change via GitHub webhook Compares ENV values with Android config files Automatically updates build.gradle and gradle.properties Creates a new Git branch Opens a pull request Sends a Slack notification You get: Automatic Android config synchronization** Safe updates via pull requests** Zero manual copying of ENV values** Instant Slack visibility for the team** Ideal for teams managing Android app configuration across environments without mistakes. What It Does This workflow automates Android configuration updates end-to-end: Listens for GitHub push events. Checks if .env.staging was modified. Stops execution if ENV file was not changed. Fetches .env.staging and gradle.properties from main. Converts both files into easy-to-compare key-value pairs. Compares ENV values against Gradle values. Creates a new Git branch for changes. Fetches files from the new branch. Identifies which variables must be updated. Applies ENV values to: build.gradle gradle.properties Commits the changes. Creates a pull request. Sends a Slack notification with PR details. This ensures Android configs are always aligned with ENV files. Who’s It For This workflow is ideal for: Android development teams DevOps & platform engineers CI/CD automation teams Teams managing multiple environments (staging / prod) Organizations avoiding manual config drift Anyone tired of copy-pasting ENV values Requirements to Use This Workflow To run this workflow, you need: n8n instance** (cloud or self-hosted) GitHub repository** with: .env.staging app/build.gradle gradle.properties GitHub Personal Access Token** Slack workspace** + API credentials Basic understanding of Android config files How It Works GitHub Webhook TriggerListens for commits pushed to the repository. ENV Change CheckWorkflow continues only if .env.staging changed. Fetch & Parse FilesReads ENV and Gradle files and converts them into key-value format. Compare Config ValuesFinds missing or mismatched variables. Create Safe BranchGenerates a timestamp-based branch from main. Apply UpdatesUpdates only the required values in: build.gradle gradle.properties Commit ChangesSaves updates to the new branch. Create Pull RequestOpens a PR for review. Notify SlackSends PR link and details to the team. Setup Steps Import the provided n8n workflow JSON. Configure GitHub credentials in all GitHub & HTTP nodes. Set your repository name and owner. Configure Slack credentials and select a channel. Ensure .env.staging exists in your repo. Activate the workflow. Push a change to .env.staging — automation starts instantly How To Customize Nodes Customize ENV File Replace .env.staging with .env.production or others. Update filename in GitHub fetch + check nodes. Customize Android Files Extend logic to include: local.properties BuildConfig.kt settings.gradle Customize Branch Naming Modify the Generate New Branch Name node. Add environment names or commit IDs. Customize Slack Message You can add: Emojis PR author name Changed variable list Mentions (@team, @android) Add-Ons (Optional Enhancements) You can extend this workflow to: Support multiple ENV files Add approval checks before PR creation Auto-merge after approval Validate ENV variable formats Send diff summary to Slack Block secrets from being committed Add Jira / Linear ticket creation Trigger Android CI build after PR creation Use Case Examples 1\. Environment Sync Keep Android configs aligned with staging ENV automatically. 2\. CI/CD Safety Prevent broken builds due to mismatched config values. 3\. Team Transparency Everyone sees config updates via Slack + PRs. 4\. DevOps Automation Remove repetitive manual config updates. 5\. Audit Friendly All changes tracked through Git history & PRs. Troubleshooting Guide | Issue | Possible Cause | Solution | |------------------------|----------------------------------|------------------------------------------------------| | Workflow not triggered | Webhook not configured | Re-register GitHub webhook | | No PR created | .env.staging not changed | Ensure the file is modified | | Wrong values updated | Parsing logic issue | Check KEY=VALUE format | | Slack message not sent | Invalid credentials | Reconnect Slack API | | Commit failed | Missing permissions | Check GitHub token scopes | Need Help? If you need help extending or customizing this workflow, adding production support, CI integrations, security checks or enterprise-scale automation, then our n8n workflow development team at WeblineIndia can help you build robust, production-ready workflows.

+2

Review GitHub pull requests and label them using OpenAI GPT-4o-mini and Slack

Automate GitHub pull request reviews and labeling using OpenAI This workflow automates the first line of code review for your development team. By leveraging OpenAI, it analyzes pull request diffs, assigns descriptive labels based on change size and category, posts summary comments back to GitHub, and keeps your team informed via Slack. Who’s it for? DevOps Engineers** looking to standardize PR triage. Team Leads** who want to provide instant feedback to developers. Open Source Maintainers** managing high volumes of contributions. Development Teams** aiming to reduce manual overhead in code reviews. How it works / What it does Trigger: The workflow starts via a GitHub PR Webhook when a pull request is opened or synchronized. Data Gathering: It extracts PR metadata and uses the GitHub Node and HTTP Request Node to fetch a list of changed files and the raw code diff. Analysis: A Code Node categorizes the changes (e.g., size labels like size/S or size/L). AI Review: The AI Agent (powered by OpenAI) analyzes the code diff to generate a quality score, summary, and specific strengths/concerns. Action: The GitHub Node updates the PR with relevant labels. An automated review comment is posted to the PR discussion. A summary is sent to a Slack channel. Reporting: All review data is logged into Google Sheets for long-term tracking and analytics. Requirements GitHub Account:** OAuth credentials with repository access. OpenAI API Key:** For the Chat Model (recommends GPT-4o-mini or higher). Slack Workspace:** A bot token to post to the #code-reviews channel. Google Sheets:** A spreadsheet with headers matching the PR metadata. How to set up GitHub Webhook: Configure your GitHub repository to send "Pull request" events to the Webhook URL provided by this workflow. Credentials: Authenticate your GitHub, OpenAI, Slack, and Google Sheets accounts in their respective nodes. Google Sheets: Select your target Spreadsheet and Sheet name in the "Log to Sheets" node. Slack: Ensure the Slack bot is invited to the channel specified in the "Notify Slack" node. How to customize AI Prompt:* Modify the "System Message" in the AI Code Reviewer* node to reflect your team's specific coding standards or preferred review tone. Labeling Logic:** Edit the "Analyze File Changes" node to add custom labels based on file paths (e.g., frontend, documentation). Review Logic:* Add an If Node* after the AI analysis to only auto-approve PRs with a quality score higher than 90.

+2

Convert GitHub Code Commits to LinkedIn Posts with Gemini AI and Code Image Generation

Turn your code commits into engaging social media content automatically. This workflow monitors a GitHub repository, uses AI to write a LinkedIn post about your changes, generates a beautiful "Mac-window" style image of your code, and publishes it all to LinkedIn. How it works GitHub Trigger: Watches for new push events in your selected repository. AI Analysis: Passes the code changes to an LLM (via LangChain) to write a professional LinkedIn post and select the best code snippet. Image Generation: Creates a custom HTML view of your code (with syntax highlighting and window controls) and converts it to an image using the HCTI API. Hosting & Posting: Uploads the generated image back to GitHub for hosting, then combines the text and image to publish a live post on LinkedIn. Set up steps Configure Credentials: You will need credentials for: GitHub (OAuth2 or Access Token) LinkedIn (OAuth2) OpenRouter (or swap the model node for OpenAI/Anthropic) HCTI.io (for the HTML-to-Image conversion) Update GitHub Nodes: In the Trigger node: Set your Owner and Repository. In the File Download node: Set the same Owner and Repository. In the Upload Image node: Set the target repo where you want images stored. Update LinkedIn Node: Add your LinkedIn Person URN in the Person field.

CI Artifact Completeness Gate (Git Push, Sentry Artifact Verification, Commit)

CI Artifact Completeness Gate (GitHub Push → Sentry Release Files → Artifact Validation → GitHub Commit Status Update) This workflow acts as a CI/CD quality gate for mobile app crash-symbolication artifacts. Whenever a new commit is pushed to GitHub, the workflow automatically checks the corresponding Sentry release and confirms whether required build artifacts (dSYM or ProGuard + mapping.txt) exist. If artifacts are complete, it updates the GitHub commit status to success, allowing the PR to be merged. If incomplete, the workflow fails silently (no commit status update), effectively blocking merges. ⚡ Quick Implementation Steps Configure GitHub Trigger for your repo. Add Sentry API credentials. Add GitHub API credentials. Update Sentry project URLs with your org_slug and proj_slug. Ensure your build pipeline uploads artifacts to Sentry before the workflow runs. Activate workflow. What It Does This workflow ensures your mobile crash-symbolication artifacts are fully present in Sentry for every release. When a new GitHub push occurs, the workflow: Reads the commit SHA and repo info from the GitHub Push event. Fetches the list of all releases from Sentry. Locates the correct release and fetches its uploaded artifact files. Runs custom validation logic: Success if: a .dSYM file exists OR*\ both proguard.txt AND mapping.txt are present\ Failure if: neither dSYM nor both mapping artifacts exist. If validated successfully, the commit receives a success status on GitHub → PR can be merged. This provides a strong CI gate ensuring symbolication completeness and preventing un-debuggable releases. Who's It For Mobile development teams using Sentry for crash reporting. Engineering teams enforcing strict release-quality gates. DevOps teams wanting automated artifact validation. CI/CD pipeline engineers integrating Sentry symbolication checks. Teams who frequently upload dSYM or ProGuard mapping files. Requirements to Use This Workflow n8n instance (cloud or self-hosted) GitHub repository access (API credentials) Sentry project with: org_slug project_slug Auth Token with release access Build process that uploads artifacts to Sentry releases The release version must match the format expected by the workflow How It Works & How To Set Up Step 1: GitHub Push Trigger The GithubPushTrigger node listens for push events and extracts: Commit SHA Repository full name Branch Metadata No configuration required except selecting your GitHub credentials. Step 2: Configure Sentry Release Fetching Open Check Sentry Artifacts Releases and update: https://sentry.io/api/0/projects/<org_slug>/<proj_slug>/releases/ Make sure the Sentry credential is correctly selected. Step 3: Fetch Files for the Specific Release The next HTTP Request (Check Sentry Artifacts Files) uses a dynamic URL: https://sentry.io/api/0/projects/<org_slug>/<proj_slug>/releases/{{ $json.version }}/files/ Ensure your build pipeline sets version consistently with what Sentry receives. Step 4: Artifact Validation Logic The Verify Artifacts node runs JS logic to check: ✔ Condition 1 --- Valid dSYM Any file ending with .dSYM ✔ Condition 2 --- Valid Android Mapping proguard.txt\ mapping.txt ✖ Failure --- If neither set exists The Code node returns: { "status": "failure", "description": "Missing artifacts..." } This stops the workflow and prevents GitHub commit-status update. Step 5: Extract Commit Info & Prepare Update The Artifacts Validation and Get Repository Data node compiles: repo full name commit SHA validation status If validation failed → workflow ends here. Step 6: Update GitHub Commit Status The Update Status node hits: POST https://api.github.com/repos/<repoFullName>/statuses/<commitSHA> And sends: { "state": "success", "description": "Artifacts successfully verified." } This appears as a green check on your commit/PR. Step 7: Activate the Workflow Turn on the workflow to start enforcing symbolication completeness for all releases. How To Customize Nodes Change Sentry Project Edit URLs in both Sentry HTTP Request nodes: org_slug proj_slug Add Additional Artifact Rules Modify JS inside Verify Artifacts, e.g., require: native symbols extra asset files other platform artifacts Customize Commit Status Message Edit the request body in Update Status. Support Multiple Platforms / Multiple Releases Branch logic in: Code nodes Conditional checks Add-Ons (Optional Enhancements) Add Slack/Teams notifications when artifacts are missing. Auto-retry release checks after build completes. Merge-blocking PR checks for GitHub. Multi-platform artifact validation (iOS + Android + Unity). Upload artifacts directly from n8n. Store validation logs in Airtable or Google Sheets. Add GitHub Checks API rich reporting. Use Case Examples Block merges until symbolication artifacts are uploaded. Enforce strict Sentry release completeness for every build. Ensure Android mapping files always match the correct release version. Automatically verify multiple release types (debug, staging, production). Improve crash debugging by preventing un-symbolicated builds from shipping. Troubleshooting Guide | Issue | Possible Cause | Solution | |----------------------------|-----------------------------------------------|--------------------------------------------------------------------------| | Commit status never updates| Validation failed silently | Check logs from Verify Artifacts | | "version undefined" in URL | Sentry release list not matched | Ensure your build uploads a valid version | | 401 from Sentry API | Invalid/broken Sentry token | Regenerate token and update credentials | | Always failing validation | Artifact names differ (e.g., .dsym.zip) | Update RegEx patterns in Code node | | GitHub status API returns 404 | Missing repo permissions | Update GitHub credentials (repo status scope) | | Files array empty | Build system not uploading artifacts | Verify build → Sentry upload step | Need Help? If you need help customizing the artifact rules, integrating multiple platforms or automating Sentry/GitHub workflows, reach out to our n8n automation developers at WeblineIndia. We can assist with: Mobile CI/CD pipelines Sentry automation Multi-artifact validation GitHub PR quality-gates Advanced Code-node scripting And so much more. Happy automating! 🚀

+4

Aggregate & Update Documentation from Slack, Teams & GitHub with Claude Sonnet 4.5

How It Works Aggregates communication data from Slack, Microsoft Teams, Gmail, GitHub, and Confluence into a single, unified AI-powered analysis workflow designed for quality review and automated documentation updates. This solution is specifically aimed at teams managing distributed content and knowledge workflows across multiple platforms. It addresses the challenges of fragmented communication and isolated information silos that often prevent rapid content review and timely decision-making. The workflow begins with a scheduled trigger, followed by multi-source data collection, merging and normalizing inputs, Claude AI-powered analysis, validation and quality checks, formatting, and finally publishing updates to Notion and Confluence, accompanied by Slack notifications to ensure stakeholders are promptly informed. Setup Steps -Connect credentials: Slack API, Teams, Gmail OAuth, GitHub PAT. -Confluence API, Anthropic API key, Notion Integration. -Configure monitored channels/repositories. -Set schedule frequency. -Map output destinations (Notion/Confluence). -Test merged output before enabling automation. Prerequisites Slack workspace, Teams account, Gmail access, GitHub repository, Confluence space, Anthropic API key, Notion workspace, n8n instance. Use Cases Content review teams processing feedback, documentation teams aggregating updates, QA teams reviewing communications Customization Add/remove source nodes, adjust Claude prompts for analysis type, modify output destinations Benefits Saves 6+ hours weekly, eliminates missed content, AI-driven quality assurance

Generate GitHub Release Notes with AI Comparison

Generate GitHub Release Notes with AI Automatically generate GitHub release notes using AI. This workflow compares your latest two GitHub releases, summarises the changes, and produces a clean, ready-to-paste changelog entry. It’s ideal for automating GitHub Releases, versioning workflows, and keeping your documentation or CHANGELOG.md up to date without manual editing. What this workflow does Listens for newly published GitHub Releases. Fetches and compares the latest two GitHub release versions. Uses an AI Chat Model to summarise changes and generate structured release notes. Outputs clean, reusable release note content for GitHub, documentation, or CI/CD pipelines. How it works GitHub Trigger detects a new published release. Release detail nodes extract the latest tag, body, and repository metadata. Comparison logic fetches the previous release and prepares a diff. Chat Model nodes (via OpenRouter) generate both a summary and a final, formatted release note. Requirements / Connections GitHub OAuth credential configured in n8n. OpenRouter API key connected to the Chat Model nodes. Setup instructions Import the template. Select your GitHub OAuth connection in all GitHub nodes. Add your OpenRouter credential to the Chat Model nodes. (Optional) Adjust the AI prompts to customise tone or formatting. Output The workflow produces: A concise summary of differences between the last two GitHub releases. A polished AI-generated GitHub release note ready to publish. Customisation ideas Push generated notes directly into a CHANGELOG.md or documentation repo. Send release summaries to Slack or Teams. Include commit messages, PR titles, or labels for deeper analysis.

Sync Azure DevOps Work Items to GitHub Issues with Google Sheets Tracking

Who is this for? This workflow is designed for software teams, project managers, and developers who manage work across Azure DevOps and GitHub. It helps organizations that use Azure DevOps for work item tracking but rely on GitHub for issue management and collaboration. If you need to ensure that your DevOps Stories and Tasks are mirrored in GitHub issues while keeping a single source of truth in Google Sheets, this workflow is for you. What problem is this workflow solving? / Use case Managing projects across multiple platforms often leads to missed updates and poor traceability. Stories created in Azure DevOps may not be tracked properly in GitHub.\ Tasks under Stories often lose visibility when teams split between platforms.\ Manual syncing between tools takes time and causes human errors. This workflow solves that problem by automating the sync between Azure DevOps Stories and GitHub Issues, while also keeping a Google Sheets record for cross-referencing and reporting. What this workflow does Triggers from Azure DevOps Stories -- When a Story is created or updated, the workflow is activated.\ Creates a GitHub Issue -- A new issue is generated in the specified GitHub repository.\ Assigns a random collaborator -- One repository collaborator is randomly assigned to the issue.\ Logs mapping in Google Sheets -- The Azure DevOps Story ID, GitHub Issue number, and URL are stored for tracking.\ Triggers from Azure DevOps Tasks -- When a Task linked to a Story is created, the workflow looks up its parent in Google Sheets.\ Updates the GitHub Issue -- The parent GitHub Issue is updated with a clickable link to the new Task for better visibility. Setup Connect your accounts GitHub (OAuth2 or personal token)\ Google Sheets (OAuth2)\ Azure DevOps (Webhook integration) Configure Webhooks Add the workflow's webhook URLs to Azure DevOps service hooks for Work Item Created/Updated events. Update repository details Set the GitHub repository where issues should be created. Customize Sheets Use the provided Google Sheet or link your own for issue mappings. How to customize this workflow to your needs Modify assignment logic**: Instead of random collaborator assignment, edit the Code node to assign issues based on workload or labels.\ Change Sheet schema**: Add more fields (e.g., State, IterationPath) to your Google Sheet for richer reporting.\ Expand task linking**: Customize the way Tasks are appended to GitHub issues (e.g., group by state, show due dates). Powered By Concept Recall https://conceptrecall.com

Automate iOS Config Sync: .env to Xcode with GitHub PRs and Email Notifications

iOS Environment Config Sync Wizard: .env to Xcode This workflow automatically detects changes to .env.staging files, compares them against iOS Xcode configuration files, creates pull requests to sync values, and invalidates Xcode build caches when needed. It ensures consistency between environment files and iOS project configs while automating the propagation of changes across the codebase and notifying the team via email. Quick Implementation Steps Import the workflow JSON into your n8n instance Set up credentials for GitHub and email Configure the webhook URL in your Git repository Customize configuration parameters in the "Set Configuration" node Activate the workflow What It Does The Environment Config Sync for iOS Xcode Projects workflow is designed to maintain consistency between environment configuration files and iOS project configuration files. When changes are made to .env.staging, the workflow automatically detects these changes, determines which iOS configuration files need to be updated, creates a new branch with those updates, and opens a pull request for review. The workflow analyzes the differences between the environment file and iOS configs, identifies which values need to be synchronized, and applies these changes to the appropriate files. It also checks if any of the changed values require cache invalidation and handles this automatically. Finally, it sends a detailed email notification to the iOS team with information about the sync operation. This automation reduces manual work, ensures consistency between configuration files, and helps prevent issues caused by mismatched environment settings across different parts of the iOS build system. Who's It For This workflow is ideal for: iOS development teams managing environment-specific configurations DevOps engineers responsible for maintaining Xcode project configuration consistency Mobile app developers working with multiple environment configurations Teams implementing CI/CD best practices for iOS applications Organizations using environment files to manage build-time configurations for Xcode projects Requirements n8n instance (self-hosted or cloud) GitHub repository with iOS project files Email service (SMTP) for sending notifications .env.staging file or similar environment configuration file iOS configuration files (Info.plist, Config.xcconfig, etc.) How It Works Webhook Trigger: The workflow starts when a push event occurs in the GitHub repository Configuration Setup: Sets up configurable parameters for file paths, branches, and notification settings File Change Detection: Checks if the .env.staging file was modified in the push Config Diff Analysis: Compares the .env.staging file with iOS Xcode configurations to identify differences Branch Creation: Creates a unique branch name and creates a new branch in the repository File Update Preparation: Prepares the updated content for each configuration file File Updates: Updates each configuration file in the new branch with the synced values PR Creation: Creates a pull request with all the configuration changes Cache Invalidation: Invalidates Xcode build cache if necessary based on changed keys Email Notification: Sends a detailed email notification about the completed sync operation How To Set Up Steps to Configure and Use 1\. Import the Workflow Import the provided JSON file into your n8n instance 2\. Set Up Credentials GitHub**: Create a new credential with a GitHub personal access token with repo scope Email**: Create a new credential with your SMTP server details for sending emails 3\. Configure GitHub Webhook Go to your GitHub repository settings Navigate to Webhooks and click "Add webhook" Set the Payload URL to the webhook URL from your n8n workflow Select "application/json" as the content type Choose "Let me select individual events" and select "Push events" Click "Add webhook" 4\. Configure Parameters Modify the parameters in the "Set Configuration" node to match your project structure: envFilePath**: Path to your environment file (default: ".env.staging") configFiles**: Array of iOS config files to update (default: \["Info.plist", "Config.xcconfig"\]) targetBranch**: Branch to create PRs against (default: "main") cacheInvalidationKeys**: Keys that trigger cache invalidation (default: \["API\_KEY", "BUNDLE\_VERSION", "ENVIRONMENT"\]) prLabels**: Labels to apply to created PRs (default: \["config-sync", "automated", "ios"\]) emailTo**: Email address for notifications (default: "[email protected]") 5\. Configure Email Settings In the "Send Email Notification" node, update the "fromEmail" parameter to match your sending email address Ensure your SMTP credentials are properly configured in n8n 6\. Activate the Workflow Once all configurations are complete, activate the workflow Test by making a change to your .env.staging file and pushing it to the repository How To Customize Add More Config Files**: Update the configFiles parameter in the "Set Configuration" node to include additional iOS configuration files like .xcconfig files or project.pbxproj Modify Cache Invalidation Logic**: Update the cacheInvalidationKeys parameter to change which keys trigger cache invalidation Customize PR Content**: Edit the "Create PR" node to modify the PR title, body, or labels Change Email Notifications**: Update the "Send Email Notification" node to modify the email format, subject, or add additional recipients Implement Actual Cache Invalidation**: Modify the "Invalidate Cache" node to implement actual Xcode cache invalidation logic for your CI/CD system Add More Environment Files**: Extend the workflow to monitor additional environment files beyond .env.staging Add‑ons Multi-Environment Support: Extend the workflow to handle multiple environment files (.env.development, .env.production) with different target branches and configurations Configuration Validation: Add validation steps to ensure that environment values match expected formats or patterns before creating PRs Automated PR Merging: Add logic to automatically merge PRs if all checks pass and no conflicts are detected Configuration History Dashboard: Integrate with a database to track configuration changes over time and provide analytics Team Approval Workflow: Add approval steps that require team members to review and approve configuration changes before PRs are created Use Case Examples API Key Rotation: When security policies require rotating API keys, the workflow automatically updates all iOS configuration files with the new keys and invalidates the Xcode build cache to ensure the changes take effect immediately. Environment Promotion: When promoting configurations from staging to production, the workflow ensures that all iOS project files are consistently updated across the codebase, preventing deployment issues caused by mismatched configurations. Bundle Version Updates: When updating bundle versions in .env.staging for a new App Store release, the workflow automatically updates version strings in Info.plist files, ensuring version consistency for App Store submission. Feature Flag Management: When feature flags are added or modified in .env.staging, the workflow propagates these changes to Config.xcconfig files, ensuring that feature flags are consistently available throughout the iOS application. Multi-Target Projects: In projects with multiple iOS targets (e.g., app, extension, watchOS), the workflow can be extended to update configuration files across all targets when environment variables change, ensuring consistency throughout the application ecosystem. Troubleshooting Guide | Issue | Possible Cause | Solution | | --- | --- | --- | | Webhook not triggering | Webhook URL not configured correctly in GitHub | Verify the webhook URL is correctly copied and configured in your GitHub repository settings | | Changes not detected | .env.staging file path doesn't match configuration | Check the envFilePath parameter in the "Set Configuration" node and ensure it matches your file structure | | Branch creation fails | GitHub token doesn't have sufficient permissions | Ensure the GitHub personal access token has the "repo" scope and access to the target repository | | File updates fail | Config file paths don't exist in the repository | Verify the configFiles parameter in the "Set Configuration" node matches actual file paths in your repository | | PR creation fails | Target branch doesn't exist or insufficient permissions | Verify the targetBranch parameter matches an existing branch and the GitHub token has appropriate permissions | | Email notifications not sent | Email credentials not configured or incorrect | Verify your SMTP credentials are correctly configured in n8n and the email address in the "Send Email Notification" node is valid | | Cache invalidation not working | Cache invalidation logic not implemented for your CI/CD system | Modify the "Invalidate Cache" node to implement the appropriate Xcode cache invalidation mechanism for your CI/CD system | | PRs created with no changes | Diff logic not properly detecting differences | Review the "Perform Config Diff" node and ensure it correctly identifies differences between environment and iOS config files | | Workflow stops after file change detection | Workflow logic error in code nodes | Check the JavaScript code in the "Perform Config Diff" node for syntax errors or logic issues | Want to Customize ? Need help setting up or customizing this Environment Config Sync for iOS Xcode Projects workflow? The n8n experts at WeblineIndia can assist you with: Customizing the workflow to fit your specific iOS project structure Integrating with additional tools and services in your CI/CD pipeline Implementing advanced configuration validation and management Setting up multi-environment support and promotion workflows Training your team on iOS configuration management best practices

+8

Creating SEO-Optimized Blogs for WordPress Using Specific Tools

✍️ AI-Powered High-Quality Blog Automation Automate SEO-optimized blog creation, publishing, and internal linking — designed for Lovable.dev or seamless WordPress integration. Proven to boost impressions by +15% weekly on real websites. 📌 Example: AI Applications in Real Estate Playbook — fully generated, optimized, and published with this automation. 🚀 What This Workflow Does Bring Your Own Keywords** You provide the keyword list — the workflow applies a scoring formula to rank them by relevance and competition for maximum SEO impact. Keyword Scoring & Logging** Scores primary and secondary keywords, logs them in PostgreSQL, and prevents reuse until strategically relevant. Deep Research & Blog Planning** Uses Perplexity AI and other AI models to outline, plan, and enrich each article with authoritative external sources. SEO-Optimized Redaction** Writes multi-part, long-form blogs with integrated internal links (to your existing content) and external links to reputable sites. Image Generation & Selection** Creates or selects high-quality header and in-article images, optimized for your topic. Full Blog Infrastructure** Internal & external linking logic Blog card + metadata updates Sitemap updates & Google indexing submission Post logging for future reference Publishing Flexibility** Direct GitHub commits for Lovable.dev WordPress-ready export Optional Slack approval before publishing 🔗 Integrated Services PostgreSQL** – Keyword & content database Perplexity AI** – Research & planning OpenAI / OpenRouter Models** – Multi-part blog writing Lovable.dev / GitHub** – Direct publishing WordPress-ready JSON output** – Easy CMS import Slack** – Approval workflow before going live 💼 What You Get Detailed Setup Guide** Workflow Description** 📥 Perfect For Website owners wanting consistent SEO growth Agencies handling multiple client sites Marketers running content-heavy campaigns Lovable.dev or WordPress users who want hands-off publishing 💡 Why You’ll Love It This is more than a blog writer — it’s a complete content infrastructure. From keyword prioritization to publishing and indexing, it keeps your site growing in reach and authority while you focus on your business.

GitHub Workflow Version Control Dashboard with Commit History and Rollbacks

This n8n template provides enterprise-level version control for your workflows using GitHub integration. Stop losing hours to broken workflows and manual exports – get proper commit history, visual diffs, and one-click rollbacks. This is the first template for n8n that provides real version control with commit-level granularity. Perfect for power users and tech teams managing multiple complex workflows. Animation demonstrates early bird version and may differ from the latest one How it works Automated sync**: Workflows are automatically synced to GitHub on your preferred schedule Smart categorization**: Dashboard shows which workflows are synced, n8n-only, or GitHub-only Complete commit history**: View every change with timestamps, authors, and commit messages Flexible import**: Import workflows from GitHub as new workflows or replace existing ones Individual workflow control**: Sync specific workflows with custom commit messages How to use Import the workflow template into your n8n instance Generate your n8n API key from your instance settings Configure your GitHub credentials and repository settings Set up the webhook endpoint for the dashboard interface Access the dashboard via the generated webhook URL Configure automatic sync schedule or use manual sync options Requirements n8n instance (cloud or self-hosted) with API access GitHub account and repository Basic understanding of Git workflows Customizing this workflow DIY or available as part of consulting services Professional customization for specific deployment workflows and integrations Custom sync schedules and commit message formats can be configured during setup

Automated Wazuh Rule Deployment Pipeline with GitHub, XML Validation & Telegram Alerts

🚀 Say Goodbye to Manual Rule Deployments in Wazuh! Just Commit— Let Your Pipeline Auto‑Deploy via GitHub + n8n 🎯 👨‍💻 Tired of This Endless Cycle? Create rule → Validate → Copy to server → Restart Wazuh → Notify team* Repeat that every week — you’re spending more time deploying than detecting. What if one GitHub commit could do it all automatically? **✅ Validate ✅ Deploy ✅ Restart ✅ Notify** — without touching the server. Well, this workflow does just that. **🔥 Presenting: ⚡️ Git‑Powered Wazuh Rule Deployment Using n8n** 🧠 What This Workflow Does in 10 Seconds — Automatically: ✅ Watches GitHub commits — triggers only if the message contains #deploy-wazuh ✅ Checks if commit author is allowed ✅ Sends contextual SOC notifications about deployment attempt 🧪 Downloads & validates rule XML using xmllint 📦 Uploads to Wazuh Manager node only if validation succeeds ♻️ Restarts Wazuh Manager and verifies loading 📢 Sends alert to your team on Telegram (or other medium) with result: success/failure & reasons 🧠 Why Detection Engineers Will Love This: ⏱️ Saves hours weekly — Just commit & chill 🕒 Zero‑delay deployments — Go live instantly 🧪 Stops bad rules before they crash your SIEM 🔁 Rapid iteration — build, commit, done 🧘 No babysitting — Pipeline handles everything 📊 Informative alerts like: "Rule custom_malware_alert.xml deployed by Mariskarthick – Validation ✅ – Restart 🔁 Completed" 📌 Perfect For: 🛡️ Detection Engineers deploying rules weekly 🏢 MSSPs with multiple Wazuh environments 🚨 Threat Intel teams needing rapid turnaround **💥 This Isn’t Just Automation — It’s Detection Engineering at Its Finest. Let your GitHub commits trigger real‑time rule deployment — with validation, restart, and SOC alerts built‑in.** Commit. Deploy. Detect.* Created by Mariskarthick M Senior Security Analyst | Detection Engineer | Threat Hunter | Open-Source Enthusiast

INST - The n8n Installer: Deploy Workflows with Automatic Credential Mapping

INST: The n8n Workflow Installer This workflow provides everything you need to package and deploy multiple workflows from a single workflow you distribute. That's right, now you can package up dozens of workflows and send your client(s) a single workflow to run, that will create them all and auto-assign all the credentials. This workflow installs 3 files when you run it, demonstrating the functionality. Just make your own mods to the system, repackage it, and you are ready to go! Requirements An n8n instance with API access enabled and an access key Optional: GitHub and OpenAI access keys What This Workflow Does Installs 3 additional workflows, demonstrating the functionality One of the workflows is a packager, that you configure for your own needs Two example workflows demonstrate functionality, and can be deleted Step-by-Step Setup Run the Workflow This will get the example and tool workflows on your instance. Package Your Content Configure the packager, then run it to produce a base64-compressed version of your files. Customize the Installer Make your own copy of the installer, and set the base64 payload. Deploy the Installer Export your installer script. Now, anyone you send it to will get all your packaged workflows when they execute it. How to Use This Workflow This workflow is meant to be reused and adapted. You can: Integrate it into a deployment pipeline Turn it into a subworkflow for dynamic installs Extend it to include triggers, permission settings, or test runs If you frequently deploy or share n8n assets, this installer gives you a repeatable way to do it with confidence.

Automate GitHub PRs & JIRA updates from Git commit commands-single repo

This n8n template from Intuz delivers a complete and automated solution to streamline your development workflow for a single repository. By embedding specific keywords and a JIRA issue ID within your git commit commands, this workflow automatically creates a Pull Request in GitHub and simultaneously updates the corresponding JIRA ticket. This provides a complete, seamless integration that eliminates manual steps and keeps your project management perfectly in sync with your codebase. How it works This workflow acts as a powerful bridge between your Git repository and your project management tools, driven entirely by the structure of your commit messages. GitHub Webhook Trigger: The workflow starts when a developer pushes a new commit to a specified repository in GitHub. Parse Commit Message: A Code node extracts key information from the commit message: The JIRA Issue Key (e.g., FF-1196). The base branch for the PR (e.g., development). Action commands like [auto-pr] and [taskcompleted]. Conditional PR Creation: An IF node checks if the [auto-pr] command is present. If yes, it uses the GitHub node to automatically create a pull request from the developer's branch to the specified base branch. If no, this step is skipped, allowing for multiple commits before a PR is made. Conditional JIRA Update: Another IF node checks for the [taskcompleted] command. If yes, it uses the JIRA node to transition the corresponding issue to your "Done" status (e.g., "Task Completed" or "In Review"). If no, the JIRA issue remains in its current state, perfect for work-in-progress commits. How to Use: Quick Start Guide Click the "Use Template" button to import this workflow into your n8n instance. Configure the GitHub Trigger: Open the "GitHub Push Trigger" node. It will display a unique Webhook URL. Copy this URL. In your GitHub repository, go to Settings > Webhooks > Add webhook. Paste the URL into the Payload URL field. Set the Content type to application/json. Under "Which events would you like to trigger this webhook?", select Just the push event. Click Add webhook. Connect Your Accounts: GitHub: Select your GitHub API credential in the "Create Pull Request" node. JIRA : Select your JIRA API credential in the "Update JIRA Issue Status" node. Customize the JIRA Transition (Important): Open the "Update JIRA Issue Status" node. In the Transition parameter, you need to set the specific status you want to move the issue to (e.g., 'Done', 'Completed', 'In Review'). You can use the ID or the exact name of the transition from your JIRA project's workflow. Activate the Workflow: Save your changes and activate the workflow. You're ready to automate! Example Commit Message: git commit -m "FF-1196 Implement OAuth login [auto-pr,development,taskcompleted]" Key Requirements to Use Template An active n8n instance. A GitHub account with repository admin permissions to create webhooks. A JIRA Cloud account with permissions to update issues. Developers who can follow the specified git commit message format. Connect with us Website: https://www.intuz.com/n8n-workflow-automation-templates Email: [email protected] LinkedIn: https://www.linkedin.com/company/intuz Get Started: https://n8n.partnerlinks.io/intuz For Custom Worflow Automation Click here- Get Started

Automated Workflow Backup to GitHub on Schedule

Easily ensure your n8n workflows are never lost! This template automates the process of backing up all your n8n workflows to a GitHub repository every 6 hours. Set it up once and enjoy worry-free workflow versioning and disaster recovery! 🔄✨ 📝 What This Workflow Does Schedules backups**: Triggers the workflow automatically every 6 hours—no manual steps needed. ⏰ Exports all current workflows**: Collects a JSON snapshot of every workflow in your n8n instance. 📦 Pushes backups to GitHub**: Commits each backup file to your specified GitHub repository with a time-stamped commit message for easy tracking. 🗂️🚀 Smart file handling**: Checks if a backup file already exists and creates or updates as needed, keeping your repository clean and organized. 🤖 ⚡️ Why Use This Template? Automate your workflow backups – never miss a backup again!** Seamless integration with GitHub** for team collaboration, change management, and rollback. Simple, reliable, and fully customizable** to match your backup intervals and repository setup. Peace of mind** that your critical automation assets are always protected. 📦 How the Template Works: Step-by-step Overview Scheduled Trigger: Fires every 6 hours to launch the backup sequence. Get All Workflows: Uses the HTTP Request node to fetch all n8n workflows from your instance as JSON data. Move Binary Data: Converts the JSON into a binary format, ready for GitHub storage. Edit/Create Backup File: Attempts to edit (update) an existing backup file in your GitHub repo. If the file does not exist, the workflow will create a new one. Conditional Logic: Checks after each run whether the backup file exists and ensures previous versions can be recovered or merged as needed. Repeat: The process auto-loops every 6 hours—no further intervention required! 🔧 How To Set Up On Your Server Import the template into your n8n instance. Configure your GitHub credentials in the workflow nodes. Update the GitHub repository details (owner, repository, and filePath) to use your own repo and desired file path. Set your n8n API key and update the API endpoint URL to match your deployment. Save and activate the workflow—now your backups are on autopilot! 👨‍💻 Example Use Cases Version control for rapidly changing automation environments. Safeguarding business-critical automation assets. Easy rollback in case of workflow corruption or accidental deletion. Team collaboration through GitHub's pull request and review process. 🌟 Pro Tips Adjust the backup interval in the Schedule Trigger node if you require more/less frequent backups. Use GitHub branch protection rules for enhanced workflow security. Pair this backup workflow with notifications (e.g., Slack or Email) for backup alerts. Protect your n8n workflows with automated, reliable, and versioned GitHub backups—set it and forget it! 🚦🔒

+4

Build & Deploy MVPs from Text Prompts with AI, GitHub & Vercel

⚡ Instant MVP Builder Idea, Build, and Deploy — in Minutes, with AI by Varritech Technologies 🏗️ What Is It? Instant MVP Builder is a plug-and-play n8n workflow that takes a plain-English app idea and turns it into a fully deployed web application — without writing a single line of code. Designed for founders, solopreneurs, and agencies, this system uses AI agents, GitHub, and Vercel to automatically: Analyze and structure the app idea Generate source code with GPT Deploy a live frontend to the web 🧠 How It Works Webhook Trigger Accepts a chat message or form input with a basic app idea. AI Prompt Agent (Langchain) Turns the message into structured specs (name, features, stack, etc). Code Generator Agent (OpenAI) Writes frontend code (React) tailored to the app spec. GitHub Integration Creates a new repo from a starter template and pushes the code. Vercel Deployment Deploys the app and returns a public URL — all automatically. 🔧 Built With n8n** – Automation engine for flow orchestration Langchain + OpenAI** – For AI-powered prompt and code creation GitHub API** – To manage repositories Vercel API** – For instant frontend deployment JavaScript** – For logic and parsing 🎯 Use Cases 🚀 Startup MVP generation 🧪 Hackathon-ready app builds 🎨 Client landing page creation 📦 Internal tool prototypes 💡 “Idea-to-product” workflows 🟨 What Makes It Special? 🧠 AI-generated code, not templates ⚙️ Fully automated from input to deploy 🌍 Public app URL in minutes 🧩 Easily customizable: edit prompts, swap repo, or deploy elsewhere 🧱 Includes built-in sticky notes + Notion setup guide 🛠️ What’s Included ✅ Cleaned, import-ready .json file for n8n ✅ Notion setup guide ✅ In-flow sticky notes describing every node ✅ No hardcoded secrets — ready for your credentials ✅ Lifetime access & updates for personal use 📄 License This workflow is licensed for single-business or internal use. Need something more? We offer: 🤝 Resell licenses for agencies 🌟 White-label customization 🔧 Prompt tuning or backend extensions 👋 About Varritech Varritech Technologies is an AI-first development agency helping businesses go from idea to production 5× faster. We specialize in building autonomous engineering workflows, onboarding systems, sales funnels, and internal tools — all powered by modern AI. 📬 [email protected] 🌐 varritech.com ✅ Build smarter. Launch faster. Automate everything. With Instant MVP Builder, your next app idea doesn’t need a dev — just a trigger.

Automatic Jest Test Generation for GitHub PRs with Dual AI Review

Workflow: Automatic Unit Test Creator from GitHub 🏗️ Architecture Overview This workflow listens for GitHub pull-request events, analyzes changed React/TypeScript files, auto-generates Jest tests via AI, has them reviewed by a second AI pass, and posts suggestions back as PR comments: GitHub Webhook → PR opened or updated Fetch & Diff → Retrieve raw diff of changed files Filter & Split → Isolate .tsx files & their diffs Fetch File Contents → Provide full context for tests Test Maker Agent → Generate Jest tests for diff hunks Code Reviewer Agent → Refine tests for style & edge-cases Post PR Comment → Sends suggested tests back to GitHub 📦 Node-by-Node Breakdown flowchart LR A[Webhook: /github/pr-events] --> B[GitHub: Get PR] B --> C[Function: Parse diff_url + owner/repo] C --> D[HTTP Request: GET diff_url] D --> E[Function: Split on "diff --git"] E --> F[Filter: /\.tsx$/] F --> G[GitHub: Get File Contents] G --> H[Test Maker Agent] H --> I[Code Reviewer Agent] I --> J[Function: Build Comment Payload] J --> K[HTTP Request: POST to PR Comments] Webhook: GitHub PR Events Type: HTTP Webhook (/webhook/github/pr-events) Subscribed Events: pull_request.opened, pull_request.synchronize GitHub: Get PR Node: GitHub Action: "Get Pull Request" Inputs: owner, repo, pull_number Function: Parse diff_url + owner/repo Extracts: diff_url (e.g. …/pulls/123.diff) owner, repo, merge_commit_sha HTTP Request: GET diff_url Fetches unified-diff text for the PR. Function: Split on "diff --git" Splits the diff into file-specific segments. Filter: /.tsx$/ Keeps only segments where the file path ends with .tsx. GitHub: Get File Contents For each .tsx file, fetches the latest blob via GitHub API. Test Maker Agent Prompt: "Generate Jest unit tests covering only the behaviors changed in these diff hunks." Output: Raw Jest test code. Code Reviewer Agent Reads file + generated tests Prompt: "Review and improve these tests for readability, edge-cases, and naming conventions." Output: Polished test suite. Function: Build Comment Payload Wraps tests in TypeScript fences: // generated tests… Constructs JSON: { "body": "<tests>" } HTTP Request: POST to PR Comments URL: https://api.github.com/repos/{owner}/{repo}/issues/{pull_number}/comments Body: Contains the suggested tests. 🔍 Design Rationale & Best Practices Focused Diff Analysis Targets only .tsx files to cover UI logic. Two-Stage AI Separate "generate" + "review" steps mimic TDD + code review. Stateless Functions Pure JS for parsing & transformation, easy to test. Non-Blocking PR Comments Asynchronous suggestions—developers aren't blocked. Scoped Permissions GitHub token limited to reading PRs & posting comments.

Backup Clockify to Github based on monthly reports

Purpose This workflow creates a versioned backup of an entire Clockify workspace split up into monthly reports. How it works This backup routine runs daily by default The Clockify reports API endpoint is used to get all data from the workspace based on time entries A report file is being retrieved for every month starting with the current one, going back 3 month in total by default If changes happened during a day to any report, it is being updated in Github Prerequisites Create a private Github repository Create credentials for both Clockify and Github (make sure to give permissions for read and write operations) Setup Clone the workflow and select the belonging credentials Follow the instructions given in the yellow sticky notes Activate the workflow

Backup Squarespace code Injections to Github

This workflow backup Squarespace website header and footer injections into Github How It Works The Squarespace injections are fetched when an URL is placed Setup Instructions First, edit HTTP Request's URL to put your Squarespace site URL there Next, to configure the Github, update the Globals node with the following values: repo.owner – Your GitHub username repo.name – The name of your GitHub repository storing the workflows repo.path – The folder path within the repository where workflows are stored For example, if your GitHub username is john-doe, your repository is named n8n-backups, and injections are stored in a squarespace-backup/ folder, you would set: repo.owner → john-doe repo.name → n8n-backups repo.path → squarespace-backup/ Each site's injections will be added into seperate folder Required Credentials GitHub API – Access to your repository Who Is This For? This template is made for Squarespace users who want to backup their header and footer injections at interval to or on demand Check out my other templates: 👉 My n8n Templates

+2

Googleform submission to create a Github issue bug report

Automated Workflow for Google Form Submissions, GitHub Issues, and Discord Notifications This workflow streamlines how new Google Form submissions are processed by automatically creating GitHub issues and sending real-time notifications to a Discord channel through a webhook. Who Is This Template For? Developers** looking to centralize bug reporting and issue tracking. Project Managers** seeking an efficient way to log tasks and updates. QA Teams** that need a fast, automated process for reporting and resolving issues. Workflow Overview Google Form Trigger The workflow begins with a Google Sheets Trigger node that checks for new form submissions every minute. Add New Form Submissions to Google Sheets Each new submission is recorded in a dedicated Google Sheet for easy reference and archiving. Filter Out Already Posted Issues An If node checks if the issue is already posted on GitHub by looking for an existing GitHub link in the sheet. Format Message / Output Parsing If the issue is new, an OpenAI Chat Model node generates a structured output, including a title, description, and suggested fix. Add Issue to GitHub The structured output is used to create a new issue in the specified GitHub repository. Send Notification to Discord A Discord webhook is triggered to send a notification to your chosen channel, including a link to the newly created GitHub issue. Add GitHub Link to the Sheet The GitHub issue link is added back to the Google Sheet for easy cross-referencing. Setup Steps Google Sheets Setup Create/Designate a Google Sheet:** Ensure it’s set to receive form submissions. Configure the Trigger Node:** Provide the correct document ID and sheet name in the Google Sheets Trigger node. OpenAI Configuration API Credentials:** Set up the OpenAI Chat Model node with valid OpenAI API credentials. Prompt Definition:** Create a prompt that formats the form submission data into a structured output (e.g., title, description, suggested fix). GitHub Configuration OAuth Credentials:** Configure the GitHub node with your GitHub OAuth credentials. Target Repository:** Specify the repository where new issues should be created. Discord Webhook Webhook URL:** Obtain a webhook URL from your Discord server. Notification Setup:** Use the HTTP Request node to send notifications to your chosen Discord channel. Google Sheets Update Document & Sheet Name:** Provide the same Google Sheet details used in the first step. Add GitHub Link:** Update the corresponding row with the newly created GitHub issue link. Recommended Google Sheet Columns Timestamp**: Automatically recorded when the form is submitted. Issue Title**: Generated by the OpenAI Chat Model. Issue Description**: Detailed breakdown of the issue. GitHub Link**: Automatically populated once the issue is created. Discord Notification Status** (optional): Indicates whether the notification was sent successfully. Additional Notes Duplicate Prevention**: The conditional logic ensures existing issues aren’t recreated on GitHub. AI-Powered Formatting**: OpenAI helps structure the issue details, providing clarity for developers. Real-Time Alerts**: Discord notifications keep your entire team updated on new issues as they arise.

Creators Hub: Generate Dynamic SVG Stats with daily updates

n8n Creators Template: Creator Profile Stats Updater This n8n workflow template is designed to automate the process of updating a creator's profile statistics, including total workflows, complex workflows, approved workflows, pending workflows, total nodes, and total views. It utilizes various nodes to fetch data, process it, and update a SVG file hosted on GitHub to reflect the latest stats. Workflow Overview Schedule Trigger: Triggers the workflow execution at specified intervals. Config: Sets up configuration details like creator username, colors for text, icons, border, and card. Get Workflows: Fetches workflows associated with the creator from the n8n API. Workflows Data: Processes the fetched data to calculate various statistics. Get User: Fetches user details from the n8n API. Download Image: Downloads the creator's profile image. Extract From File: Extracts binary data from the downloaded image file. SVG: Generates an SVG file with updated stats and visual representation. GitHub: Commits the updated SVG file to the specified GitHub repository. Final: Prepares the final data set for further processing or output. Sticky Note: Provides a visual note or reminder within the workflow editor. Embed & Live Preview Since it's a .SVG format you can host it anywhere. treat it like normal image so you can embed it with any site, forum, page that support posting images. here's example code for markdown: Here's the result Or served through CDN & Cache Setup Instructions GitHub Credentials: Ensure you have GitHub credentials set up in your n8n instance to allow the workflow to commit changes to your repository. Configure Trigger: Adjust the Schedule Trigger node to set the desired execution intervals for the workflow. Set Configuration: Customize the Config node with your GitHub username and preferred aesthetic options for the SVG. Deploy Workflow: Import the workflow into your n8n instance and deploy it. Customization Options Text and Icon Colors**: Customize the colors used in the SVG by modifying the respective fields in the Config node. Profile Image Size**: Adjust the image size in the Download Image node URL if needed. Commit Messages**: Modify the commit messages in the GitHub nodes to suit your version control conventions [I've used $now funaction to include current time in message which will gives allways a diffrent commit value]. Requirements n8n (Self-hosted or Cloud version compatible with 2024 releases and up) GitHub account and repository Basic understanding of n8n workflow configuration Support and Contributions For support, please refer to the n8n community forum or the official n8n documentation. Contributions to the template can be made you're allowed to reuse this workflow and reshare with edit (like new design/colors etc..) under your name.

GitHub and HTTP Request integration

How to connect GitHub and HTTP Request

Step 1: Create a new workflow and add the first step

Step 2: Add and configure GitHub and HTTP Request nodes

Step 3: Connect GitHub and HTTP Request

Step 4: Customize and extend your GitHub and HTTP Request integration

Step 5: Test and activate your GitHub and HTTP Request workflow

Back up your n8n workflows to Github

Popular GitHub and HTTP Request workflows