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 Workflow Backups to GitHub with Subfolder Organization
Automatically backup your n8n workflows to GitHub, organizing them into subfolders based on tags. This ensures safe storage and easy migration.
n8n$14.99Automate AI Resume Parsing and GitHub Profile Analysis
Streamline candidate evaluation by automating resume parsing with AI and analyzing GitHub profiles for technical insights, complete with team notifications.
n8n$14.99Automated GitHub Scanner for Exposed AWS IAM Keys
# Automated GitHub Scanner for Exposed AWS IAM Keys ## Overview This n8n workflow automatically scans GitHub for exposed AWS IAM access keys associated with your AWS account, helping security teams quickly identify and respond to potential security breaches. When compromised keys are found, the workflow generates detailed security reports and sends Slack notifications with actionable remediation steps. ## Key Features - **Automated AWS IAM Key Scanning**: Regularly checks for exposed AWS access keys on GitHub - **Real-time Security Alerts**: Sends immediate Slack notifications when compromised keys are detected - **Comprehensive Security Reports**: Generates detailed reports with exposure information and risk assessment - **Actionable Remediation Steps**: Provides clear instructions for securing compromised credentials - **Continuous Monitoring**: Maintains ongoing surveillance of your AWS environment ## Workflow Steps 1. **List AWS Users**: Retrieves all users from your AWS account 2. **Split Users for Processing**: Processes each user individually 3. **Get User Access Keys**: Retrieves access keys for each user 4. **Filter Active Keys Only**: Focuses only on currently active access keys 5. **Search GitHub for Exposed Keys**: Scans GitHub repositories for exposed access keys 6. **Aggregate Search Results**: Consolidates and deduplicates search findings 7. **Check For Compromised Keys**: Determines if any keys have been exposed 8. **Generate Security Report**: Creates detailed security reports for compromised keys 9. **Extract AWS Usernames**: Extracts usernames from AWS response for notification 10. **Format Slack Alert**: Prepares comprehensive Slack notifications 11. **Send Slack Notification**: Delivers alerts with actionable information 12. **Continue Scanning**: Maintains continuous monitoring cycle ## Setup Requirements ### Prerequisites - Active n8n instance - AWS account with IAM permissions - GitHub account/token for searching repositories - Slack workspace for notifications ### Required Credentials 1. **AWS Credentials**: - IAM user with permissions to list users and access keys - Access Key ID and Secret Access Key 2. **GitHub Credentials**: - Personal Access Token with search permissions 3. **Slack Credentials**: - Webhook URL for your notification channel ## Configuration 1. **AWS Configuration**: - Configure the List AWS Users node with your AWS credentials - Ensure proper IAM permissions for listing users and access keys 2. **GitHub Configuration**: - Set up the Search GitHub for Exposed Keys node with your GitHub token - Adjust search parameters if needed 3. **Slack Configuration**: - Configure the Slack node with your webhook URL - Customize notification format if desired ## Usage ### Running the Workflow 1. **Manual Execution**: Click Execute Workflow to run an immediate scan 2. **Scheduled Execution**: Set up a schedule to run periodic scans (recommended daily or weekly) ### Repository Compatibility This workflow is compatible with both public and private GitHub repositories to which you have access. It will scan all repositories you have permission to view based on your GitHub credentials. ### Handling Alerts When a compromised key is detected: 1. Review the Slack notification for details about the exposure 2. Follow the recommended remediation steps: - Deactivate the compromised key immediately - Create a new key if needed - Investigate the exposure source - Update any services using the compromised key ## Disclaimer This workflow template is provided for reference purposes only to demonstrate how to automate AWS IAM key exposure scanning. Please note: - The scanning process may produce false positives as it only matches potential AWS access key patterns - Always verify any reported exposures manually before taking action - Disabling or deleting access keys without proper verification could have significant negative impacts on your environment - Understand which systems and applications rely on identified access keys before deactivating them - This template should be customized to fit your specific environment and security policies **IMPORTANT**: Use this workflow with caution and only after thoroughly understanding your AWS environment. The authors of this template are not responsible for any disruptions or damages resulting from its use. ## Security Considerations - This workflow requires access to sensitive AWS credentials - Store all credentials securely within n8n - Review and rotate access keys regularly ## Customization Options - Adjust GitHub search parameters for more targeted scanning - Customize Slack notification format and content - Modify security report generation for your specific needs - Integrate with additional notification channels (email, MS Teams, etc.) ### Optional: Enabling Interactive Slack Buttons The Slack Block Kit notification format supports interactive
n8n$14.99Backup Workflows to Git Repository on GitHub
[Source code](https://code.swecha.org/shashikanth/n8n-templates/-/tree/main/backup-workflows), I maintain this workflow here. # Usage Guide This workflow backs up all workflows as JSON files named in the `[workflow_name].json` format. ## Steps 1. **Create GitHub Repository** - Skip this step if using an existing repository. 2. **Add GitHub Credentials** - In **Credentials**, add the GitHub credential for the repository owner. 3. **Download and Import Workflow** - Import this workflow into n8n. 4. **Set Global Values** - In the **Globals** node, set the following: - `repo.owner`: GitHub username of the repository owner. - `repo.name`: Name of the repository for backups. - `repo.path`: Path to the folder within the repository where workflows will be saved. 5. **Configure GitHub Nodes** - Edit each GitHub node in the workflow to use the added credentials. ## Workflow Logic Each workflow run handles files based on their status: 1. **New Workflow** - If a workflow is new, create a new file in the repository. 2. **Unchanged Workflow** - If the workflow is unchanged, skip to the next item. 3. **Changed Workflow** - If a workflow has changes, update the corresponding file in the repository. ## Current Limitations / Needs work 1. **Name Change of Workflows** - If a workflow is renamed or deleted in n8n, the old file remains in the repository. 2. **Deleted Workflows** - Deleted workflows in n8n are not removed from the repository.
n8n$14.99Automate n8n Workflow Imports from GitHub via Webhook
Streamline the deployment of n8n workflows by automatically importing them from a GitHub repository using a secure webhook. This setup ensures version control and seamless integration into your CI/CD pipeline.
n8n$9.99Automate Bug Tracking with GitHub Issues and Telegram Alerts Using AI
Streamline bug tracking by creating GitHub issues from webhook inputs, classifying them with AI, and sending alerts via Telegram. This workflow enhances efficiency by automating the classification and notification of critical issues.
n8n$14.99Automate Social Media Posts from GitHub README and CHANGELOG Updates
Automatically generate and publish social media posts on Twitter and LinkedIn whenever your GitHub repository's README or CHANGELOG files are updated.
n8n$14.99Automate Squarespace Code Injection Backups to GitHub
This workflow automates the backup of Squarespace header and footer code injections to a GitHub repository, ensuring your customizations are securely stored and versioned.
n8n$14.99Create 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](https://github.com/) (image storage) and [shorten.rest](https://shorten.rest/) (URL redirects). Both can be swapped for your preferred services. --- Follow me on [LinkedIn](https://www.linkedin.com/in/parsadanyan/) for more tips on AI automation and n8n workflows!
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.99Synchronize Typebot Flows with GitHub for Backup and Deletion
Automate the backup of Typebot flows to GitHub and ensure synchronization by deleting files in GitHub if flows are removed from Typebot.
n8n$19.99Automate GitHub Workflow Sync to n8n After Pull Request Merges
Streamline your CI/CD process by automatically syncing GitHub workflows to n8n after a pull request is merged, reducing manual errors and saving time.
n8n$9.99Automate SEO Blog Publishing for Jekyll with AI and GitHub Integration
Streamline the process of publishing SEO-optimized blog posts to a Jekyll site on GitHub using AI-generated content. This workflow automates content creation, formatting, and social media sharing.
n8n$9.99Back Up Your n8n Workflows on 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 it requires at least version 0.198.0 of n8n.
n8n$14.99Get GitHub Issue Updates and Send Notifications to Telegram
## **Who is this for?** This workflow is ideal for: - **Developers** who want to stay updated on issues without constantly checking GitHub. - **Managers** tracking issue progress in a Telegram group. - **DevOps teams** that need automated notification alerts for new or updated issues. ## **What problem does this workflow solve?** Keeping track of GitHub issues manually can be tedious. Teams often miss critical updates because notifications are buried in emails or dashboards. This workflow automates the process by fetching new or open GitHub issues and instantly sending notifications to a specified Telegram chat. ## **What this workflow does** This workflow connects GitHub and Telegram to provide real-time issue notifications: 1. **Fetch GitHub Issues** - Retrieves new or open issues from a selected GitHub repository. 2. **Format the Issue Details** - Extracts key information like issue title, number, status, and URL. 3. **Send to Telegram** - Posts the formatted issue details to a Telegram group or private chat. ## **Setup Guide** ### **Prerequisites** Before setting up the workflow, ensure you have: - **GitHub Personal Access Token**: Required to fetch issue details. Generate it under Developer Settings with `repo` or `public_repo` permissions. - **Telegram Bot Token**: Create a bot via [BotFather](https://t.me/BotFather) on Telegram and obtain the token. - **Telegram Chat ID**: Find the chat ID where the bot should send messages using [this method](https://t.me/getmyid_bot). ### **Step-by-Step Setup** 1. **Set Up GitHub Node** - Authenticate using your GitHub token. - Choose the repository you want to track. - Configure filters (e.g., fetch only open issues). 2. **Format Issue Details** - Extract key details like title, issue number, assignee, and status. - Customize the message structure for better readability. 3. **Send Message to Telegram** - Add the Telegram node and enter your bot token. - Use the Chat ID to define the recipient. - Format the message to include issue details and links. 4. **Schedule the Workflow** (Optional) - Use the **Cron node** to run this workflow periodically (e.g., every hour). ## **How to Customize This Workflow** - **Filter Issues by Labels**: Modify the GitHub node to fetch only issues with specific labels. - **Include Additional Fields**: Add issue comments, priority, or assignee details in the message. - **Send Alerts Based on Priority**: Use conditional logic to send high-priority issues to a different chat. - **Trigger on Issue Events**: Instead of fetching periodically, use GitHub webhooks (if permitted in the repo) to trigger the workflow on issue creation or updates. ## **Why Use This Workflow?** - **Automates GitHub issue tracking** without manually checking repositories. - **Instant notifications in Telegram** ensure quick response times. - **Fully customizable** to fit different team workflows.
n8n$9.99Back Up Your Credentials to GitHub
Based on [Jonathan's](https://n8n.io/creators/jon-n8n/) 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 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. ### 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/**](https://n8n.io/creators/solomon/)
n8n$14.99Automate n8n Workflow Backups to GitHub Every 6 Hours
Ensure your n8n workflows are securely backed up by automating the backup process to a GitHub repository every 6 hours. This workflow provides seamless versioning and disaster recovery.
n8n$9.99Automate n8n Workflow Documentation and Backup to Notion and GitHub
This workflow automates the documentation and backup of n8n workflows by storing them in a Notion database and GitHub repository. It leverages OpenAI's GPT-4 for summarization and sends notifications to a Slack channel for updates.
n8n$14.99Automate Wazuh Rule Deployment with GitHub and Telegram Alerts
Streamline your Wazuh rule deployment process by automating validation, deployment, and notifications using GitHub commits and Telegram alerts.
n8n$9.99Automate WordPress Backup to GitHub
This workflow automates the process of backing up WordPress content to GitHub, ensuring your data is securely stored and version-controlled.
n8n$14.99Automate n8n Workflow Backups to GitHub with Discord Notifications
This workflow automates the backup of all your n8n workflows to a GitHub repository, with real-time notifications via Discord for backup status updates.
n8n$14.99Automate GitHub Issue Creation and Email Notifications from Notion
This workflow automates the process of tracking feature requests in Notion, creating GitHub issues, and notifying your team via email based on issue status. It's ideal for teams collaborating on project delivery using Notion and GitHub.
n8n$9.99Automate Monitoring of Multiple GitHub Repositories with Webhooks
This workflow enables efficient monitoring of multiple GitHub repositories using webhooks, eliminating the need for constant polling. It allows for easy addition and removal of repositories from your watchlist, streamlining management.
n8n$14.99
More integrations
Need a custom GitHub workflow?
Our automation experts build tailored GitHub integrations for your exact stack.
Request a Custom Workflow