GitHub Automation Workflows
343 ready-made GitHub workflows for n8n, Make, Zapier, Activepieces, and Pipedream. Dev workflows: issues, PRs, releases, and repo events wired to your tools.
Automate n8n Workflow Backup and Synchronization with GitHub
Automatically back up your n8n workflows to GitHub and synchronize deletions to maintain consistency.
n8n$19.99Daily 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 1. Configure the Config node in the subworkflow to set: - GitHub Repo Owner - GitHub Repo Name - Main folder path (repo_path) 2. Connect your GitHub and (optionally) Slack credentials. 3. Set the workflow to run on a daily cron schedule. 4. Test the workflow manually to confirm the GitHub integration works. Sign up for a [free consultation](https://boanse.gumroad.com/l/free_n8n_consultation) and find out how n8n can help you.
n8n$14.99Automate Podcast Episode Publishing to Spotify via Google Drive and GitHub
Streamline your podcast publishing by automating the upload of episodes to Spotify. This workflow manages audio file uploads to Google Drive, updates your RSS feed on GitHub, and ensures episodes are live on Spotify with minimal manual intervention.
n8n$14.99Interactive GitHub API Documentation Chatbot with RAG, Pinecone, and OpenAI
This workflow creates an interactive chatbot that allows users to query the GitHub API documentation using natural language. By leveraging Retrieval Augmented Generation (RAG), OpenAI's language models, and Pinecone's vector database, it delivers precise and context-aware responses.
n8n$14.99Automate GitHub Pull Request Code Reviews with AI and Google Sheets
This n8n workflow automates code reviews for GitHub pull requests using OpenAI's language models and coding best practices stored in Google Sheets. It streamlines the review process by generating AI-powered comments and labeling reviewed pull requests.
n8n$9.99Automate SEO Blog Post Generation and Publishing to GitHub
Automatically generate and publish SEO-optimized blog posts to GitHub every 8 hours. This workflow uses trending topic research, AI content generation, and JSON formatting to streamline your content creation process.
n8n$9.99Daily Automated Backup of n8n Workflows to GitHub
This workflow automates the daily backup of all your n8n workflows to a specified GitHub repository, ensuring version control and secure storage. It leverages the n8n and GitHub APIs to maintain an up-to-date backup history, providing a reliable disaster recovery solution.
n8n$9.99Automate Weekly Tutorial Creation from Trending GitHub Repos to WordPress
This workflow automates the generation of technical tutorials from trending GitHub repositories, using AI to create content and posting drafts to WordPress. It streamlines content creation for your blog, ensuring fresh, relevant topics with minimal manual effort.
n8n$9.99Automate n8n Workflow Backups with GitHub Integration
Effortlessly back up and synchronize your n8n workflows to a GitHub repository with intelligent change detection and rename support.
n8n$19.99Integrate GitHub Models with OpenAI-Compatible API in n8n
Leverage GitHub's free AI models by integrating them into your n8n workflows using a custom OpenAI-compatible API.
n8n$14.99Automate Bidirectional Sync Between n8n Workflows and GitHub Repositories
Ensure your n8n workflows and GitHub repositories are always in sync with this automated workflow. It resolves version conflicts and maintains consistent backups by comparing and updating workflows in both systems.
n8n$14.99Automate n8n Workflow and Credential Backups to GitHub with Change Detection
This n8n workflow automates the backup of workflows and credentials to GitHub, only committing changes when differences are detected, reducing redundant commits.
n8n$14.99Automate Social Media Posts from GitHub Discussions Using AI
Streamline your social media content creation by automating the curation and sharing of trending GitHub discussions from Hacker News to Twitter and LinkedIn using AI.
n8n$14.99Create a Custom GitHub MCP Server for Issue Management
Set up a personalized GitHub MCP server to manage repository issues and comments, enhancing security and control over user access.
n8n$14.99Multi-Platform Source Discovery with SerpAPI, DuckDuckGo, GitHub, Reddit, & Bluesky
# Source Discovery - Automatically Search More Up-to-Date Information Sources ## Overview **Version**: 1.0 This workflow utilizes various nodes to discover and analyze potential sources of information from platforms like Google, Reddit, GitHub, Bluesky, and others. It is designed to streamline the process of finding relevant sources based on specified search themes. ## Features - Automated source discovery from multiple platforms. - Filtering of existing and undesired sources. - Error handling for API requests. - User-friendly configuration options. ## Who is this for? This workflow is ideal for researchers, content marketers, journalists, and anyone looking to efficiently gather and analyze information from various online sources. ## What problem does this solve? This workflow addresses the challenge of manually searching for relevant information sources, saving time and effort while ensuring that users have access to the most pertinent content. Ideal use-cases include: - Resource Compilation for Academic and Educational Purposes - Journalism and Research - Content Marketing - Competitor Analysis ## What this workflow does The workflow gathers data from selected platforms through search terms. It filters out known and undesired sources, analyzes the content, and provides insights into potential sources relevant to the user's needs. ## Workflow Steps ### 1. Search Queries - Fetch sources using SerpAPI search, DuckDuckGo, and Bluesky. - Utilizes GitHub repositories to find relevant links. - Leverages RSS feeds from subreddits to identify potential sources. ### 2. Filtering Step - Removes existing and undesired sources from the results. ### 3. Source Selection - Analyzes the content of the identified sources for relevance. ## Expected Input / Configuration The workflow is primarily configured via the **Configure Workflow Args (Manual)** node or the **Global Variables** custom node. - Search themes: Keywords or phrases relevant to the desired content. - Lists of known sources and undesired sources for filtering. ## Expected Output A curated list of potential sources relevant to the specified search themes, along with insights into their content. ## Example       ## n8n Setup Used - **n8n version:** 1.105.3 - **n8n-nodes-serpapi:** 0.1.6 - **n8n-nodes-globals:** 1.1.0 - **n8n-nodes-bluesky-enhanced**: 1.6.0 - **n8n-nodes-duckduckgo-search**: 30.0.4 - **LLM Model:** mistral-small-latest (API) - **Platform:** Podman 4.3.1 on Linux - **Date:** 2025-08-06 ## Requirements to Use / Setup - Self-hosted or cloud n8n instance. - Install the following custom nodes: SerpAPI, Bluesky, and DuckDuckGo Search. - [n8n-nodes-serpapi](https://github.com/serpapi/n8n-nodes-serpapi) - [n8n-nodes-duckduckgo-search](https://github.com/samnodehi/n8n-nodes-duckduckgo) - [n8n-nodes-bluesky-enhanced](https://github.com/brianmoney/n8n-nodes-bluesky) - Install the Global Variables Node for enhanced configuration: - [n8n-nodes-globals](https://github.com/umanamente/n8n-nodes-globals) (or use Edit Field (Set) node instead) - Provide valid credentials to nodes for your preferred LLM model, SerpAPI, and Bluesky. Credentials for GitHub recommended. ## Notes, Assumptions & Warnings - Ensure compliance with the terms of service of any platforms accessed or discovered in this workflow, particularly concerning data usage and attribution. - Monitor API usage to avoid hitting rate limits. - The workflow may encounter errors such as 403 responses; in such cases, it will continue by ignoring the affected substep. - Duplicate removal is applied, but occasional overlaps might still appear depending on the sources. - This workflow assumes familiarity with n8n, APIs, and search engines. - Using AI agents (Mistral or substitute LLMs) requires access to their API services and keys. - This is not a Curator of News. It is designed to find websites that are relevant and useful to your searches. If you are looking for a relevant news selector, please check this [workflow](https://n8n.io/workflows/6157-multi-source-news-curator-with-mistral-ai-analysis-summaries-and-custom-channels/). ## About Us This workflow was developed by the Hybroht team. Our goal is to create tools that harness the possibilities of technology and more. We aim to continuously improve and expand functionalities based on community feedback and evolving use cases. For questions, reach out via [contact@hybroht.com](mailto:contact@hybroht.com). ### Warranty & Legal Notice This free workflow is provided as-is without any warranties of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. By using
n8n$24.99Auto-Create GitHub PRs & JIRA Updates from Git Commit Commands (Multi-Repo)
# This n8n template from [Intuz](https://www.intuz.com/) provides a complete and automated solution for scaling your DevOps practices across multiple repositories. Are you tired of the repetitive dance between git push, creating a pull request in GitHub, updating the corresponding task in JIRA, and then manually notifying your team in Slack or Notion? This template puts your entire post-commit workflow on autopilot, creating a seamless and intelligent bridge between your code and your project management. By embedding specific keywords and a JIRA issue ID into your git commit commands, this workflow automatically creates a Pull Request in the correct GitHub repository and updates the corresponding JIRA ticket. This creates a complete, centralized system that keeps all your projects synchronized, providing a massive efficiency boost for teams managing a diverse portfolio of codebases. ## Who This Template Is For? This template is a must-have for any organization looking to streamline its software development lifecycle (SDLC). It's perfect for: - Development Teams: Eliminate tedious, manual tasks and enforce a consistent workflow, allowing developers to stay focused on coding. - DevOps Engineers: A ready-to-deploy solution that integrates key developer tools without weeks of custom scripting. - Engineering Managers & Team Leads: Gain real-time visibility into development progress and ensure processes are followed without constant check-ins. - Project Managers: Get accurate, automatic updates in JIRA the moment development work is completed, improving project tracking and forecasting. ## Step-by-Step Setup Instructions Follow these steps carefully to configure the workflow for your environment. **1. Connect Your Tools (Credentials)** - GitHub: Create credentials with repo scope to allow PR creation. - JIRA: Create an API token and connect your JIRA Cloud or Server instance. - Slack: Connect your Slack workspace using OAuth2. - Notion: Connect your Notion integration token. **2. Configure the GitHub Webhook (For Each Repository)** This workflow is triggered by a GitHub webhook. You must add it to every repository you want to automate. - First, Save and Activate the n8n workflow to ensure the webhook URL is live. - In the n8n workflow, copy the Production URL from the Webhook node. - Go to your GitHub repository and navigate to Settings > Webhooks > Add webhook. - In the Payload URL field, paste the n8n webhook URL. - Change the Content type to application/json. - Under "Which events would you like to trigger this webhook?", select "Just the push event". - Click Add webhook. Repeat this for all relevant repositories. **3. Configure the JIRA Nodes (Crucial Step)** Your JIRA project has unique IDs for its statuses. You must update the workflow to match yours. - Find the two JIRA nodes named "Update task status after PR" and "Update the task status without PR". - In each node, go to the Status ID field. - Click the dropdown and select the status that corresponds to "Done" or "Development Done" in your specific JIRA project workflow. The list is fetched directly from your connected JIRA instance. **4. Configure Notification Nodes** Tell the workflow where to send updates. - For Slack: Open the two nodes named "Send message in slack..." and select your desired channel from the Channel ID dropdown. - For Notion: Open the two nodes named "Append a block in notion..." and paste the URL of the target Notion page or database into the Block ID field. **5. Final Activation** Once all configurations are complete, ensure the workflow is Saved and the toggle switch is set to Active. You are now ready to automate! ## Customization Guidance This template is a powerful foundation. Here's how you can adapt it to your team's specific needs. **1. Changing the PR Title or Body:** - Go to the "Request to create PR (HTTP Request)" node. - In the JSON Body field, you can edit the title and body expressions. For example, you could add the committer's name ({{$(Webhook).item.json.body.pusher.name}}) or a link back to the JIRA task. **2. Adapting to a Fixed Branching Strategy:** - If your team always creates pull requests against a single branch (e.g., develop), you can simplify the workflow. - In the "Request to create PR" node, change the base value in the JSON body from {{...}} to your static branch name: base: develop. - You can then remove the base branch logic from the "Commit Message Breakdown (Code)" node. **3. Modifying Notification Messages:** - The text sent to Slack and Notion is fully customizable. - Open any of the Slack or Notion nodes and edit the text fields. You can include any data from previous nodes, such as the PR URL ({{$(Request to create PR).item.json.body.html_url}}) or the repository name. **4. Adjusting the Commit Regex for Different Conventions:** - This is an advanced customization. If your team uses a different commit format (e.g., (DEV-123) instead of DEV-123), you can adjust the regex in the "Commit Message Breakdown (Code)" node to match your team's convention.
n8n$24.99Automate Release Notes Generation and Distribution with GitHub, JIRA, and Google Gemini
Streamline your software release process by automatically generating and emailing professional release notes using GitHub, JIRA, and Google Gemini.
n8n$14.99Automate Daily Postgres Table Backups to GitHub as CSV Files
This workflow automates the daily backup of all public Postgres tables to a GitHub repository in CSV format, ensuring your data is consistently up-to-date and version-controlled.
n8n$14.99Automate GitHub Trending Data Collection to Supabase
Streamline the process of collecting and storing GitHub trending repository data in Supabase for easy access and analysis.
n8n$9.99Automate GitHub PRs & JIRA Updates from Git Commit Commands - Single Repo
## This n8n template from [Intuz](https://www.intuz.com/) 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. 1. **GitHub Webhook Trigger:** The workflow starts when a developer pushes a new commit to a specified repository in GitHub. 2. **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]. 3. **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. 4. **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 1. Click the Use Template button to import this workflow into your n8n instance. 2. 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. 3. 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. 4. 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 projects workflow. 5. 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/services - Email: getstarted@intuz.com - LinkedIn: https://www.linkedin.com/company/intuz - Get Started: https://n8n.partnerlinks.io/intuz ## For Custom Workflow Automation Click here - [Get Started](https://www.intuz.com/get-started)
n8n$14.99Automate Extraction of Trending GitHub Repositories
Effortlessly scrape and structure data from GitHub's trending repositories page, providing insights into popular open-source projects.
n8n$4.99Back up Your Workflows to GitHub
Based on [Jonathan's](https://n8n.io/creators/jon-n8n/) 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 credentials 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/**](https://n8n.io/creators/solomon/)
n8n$14.99Automate Blog Updates via Discord with GitHub and Gemini AI
## Automate blog updates via Discord with GitHub and customizable AI chatbot  **Disclaimer:** This template uses the [n8n-nodes-discord-trigger](https://github.com/katerlol/n8n-nodes-discord-trigger) community node, which means it works only in **self-hosted n8n** instances. (works for **both** cloud and localhost) ## Who's it for This workflow is designed for developers, bloggers, and technical writers who want a **hands-free way to draft and publish blog posts** directly from Discord. Instead of juggling multiple tools, you just send a message to your Discord bot, and the workflow creates a properly formatted Markdown file in your GitHub repo. ## How it works - Listens for new messages in a Discord channel or DM using the **Discord Trigger (community node)**. - Passes your message to an **AI chatbot model** (Google Gemini, OpenAI GPT, or any other connector you prefer) to draft or format the content. - Uses **GitHub nodes** to check existing files, read repo contents, and create new `.md` posts in the specified directory. - Adds the correct timestamp with the **Date & Time node**. - Sends a **confirmation reply** back to Discord (Regular Message Node). - Guardrails ensure it **only creates new Markdown files in the correct folder**, without overwriting or editing existing content. ## How to set up 1. Import the workflow (or download the file here [BlogAutomationclean.json](https://github.com/Praneel7015/n8n-discord-github-blog-buddy/blob/main/BlogAutomationclean.json)) into your self-hosted n8n. 2. Install the [n8n-nodes-discord-trigger](https://github.com/katerlol/n8n-nodes-discord-trigger) community node inside n8n workflow dashboard (**click the link for the steps of setup**). 3. Create credentials for: - Discord bot trigger from the **community node** - Discord bot send Message from the **Regular Discord Message Node** - GitHub (personal access token with repo permissions) - Your AI provider (Gemini, OpenAI, etc.) 4. Update the GitHub nodes with: - **Owner** – your GitHub username - **Repo** – your blog repo name - **Path** – target directory for new Markdown posts 5. Customize the AI agents **system prompt** to match your tone and workflow. (Default prompt included below.) 6. Test it in a private Discord channel before going live. ## Requirements - Self-hosted n8n instance (works both on cloud and localhost) - GitHub repository with write access - Discord bot credentials (**BOTH ARE REQUIRED: COMMUNITY NODE FOR TRIGGER AND REGULAR NODE** read below for reasoning) - AI model credentials (Gemini, OpenAI, or other supported provider) ## How to customize the workflow - Swap the AI model node for any provider you like: Gemini, OpenAI, or even a local LLM. - Adjust the **prompt** to enforce your blog style guide. - Add additional steps like auto-publishing, Slack notifications, or Notion syncs. - Modify the directory path or file naming rules to fit your project. ## Reason for Using the Community Discord Trigger Node and Regular Discord Message Node From testing, the Community Discord node cannot send big messages (Has a Certain limit), while the Original/Regular Discord Message Node can send far beyond that amount which helps for viewing Files. Feel free to use both trigger and Send Message from the community node if facing issues, it will still work flawlessly other than message limit. ## Default Prompt ``` ## Core Identity & Persona You are the **n8n Blog Master**, a specialized AI agent. Your primary function is to assist your user with content management. * **Your Mission:** Automate the process of creating, formatting, editing, and saving blog posts as Markdown files within the user's specified repository. * **User Clarification:** The repository owner always refers to your **user** and, in the context of API calls, the **repository owner**. It is never part of a file path. * **Personality:** Helpful, precise, security-conscious. Semi-casual and engaging, but never overly cheerful. --- ## Operational Zone & Constraints * **Repository:** You may only interact with the repository **`<insert-repo-name-here>`**. * **Owner:** The repository owner is **`<insert-username-here>`**. * **Branch:** Always operate on the `main` branch. * **Directory Access:** You can **only** write or edit files in the directory **`<insert-directory-path-here>`**. You are forbidden from interacting elsewhere. * **File Permissions:** - You may **create new `.md` files**. - If a file already exists, notify the user and ask if they want to edit it. - Editing is only allowed if the user explicitly confirms (e.g., “yes”, “go ahead”, “continue”). - If the user confirms, proceed with editing. --- ## Available Tools & Usage Protocol You have a limited but well-defined toolset. Always use them exactly as described: ### 1. Date & Time Tool * Purpose: Always f ```
n8n$9.99Restore n8n Credentials from GitHub Backups
Effortlessly restore your n8n instance credentials from GitHub backups using this automated workflow. This ensures seamless recovery and migration of credentials.
n8n$9.99
More integrations
Need a custom GitHub workflow?
Our automation experts build tailored GitHub integrations for your exact stack.
Request a Custom Workflow