Development & IT Workflows
Software development and IT operations
Backup 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 Daily Backup of n8n Workflows to GitLab
This workflow automates the daily backup of n8n workflows to a GitLab repository, ensuring version control and synchronization. It compares current n8n workflows with their GitLab counterparts and updates the repository if changes are detected.
n8n$14.99Automate n8n Workflow Backups and Documentation to GitLab
Automatically back up your n8n workflows to a GitLab repository and generate AI-powered documentation whenever workflows are updated or activated.
n8n$9.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.99Check VPS Resource Usage Every 15 Minutes
This n8n workflow template is designed to help system administrators and DevOps professionals monitor key resource usage metrics - CPU, RAM, and Disk - on a VPS (Virtual Private Server). The workflow automatically checks these resources every 15 minutes and sends an email alert if any resource usage exceeds the 80% threshold. This proactive monitoring helps maintain optimal server performance and prevents resource-related downtimes. # Who This Workflow Is For - **System Administrators** managing Linux-based servers who need to ensure their systems are running smoothly without manual monitoring. - **DevOps Professionals** who manage multiple environments and need automated tools to alert them to potential issues before they affect operations. - **IT Support Teams** who require an easy way to keep tabs on server health across an organization's infrastructure. # How It Works 1. **Schedule Trigger**: The workflow is triggered every 15 minutes by a Cron node. 2. **Resource Checks**: Separate SSH Command nodes are configured to execute specific commands that check the current usage of RAM, Disk, and CPU. 3. **Data Aggregation**: The results from each check are merged using a Merge node, which combines the data into a single payload for analysis. 4. **Threshold Analysis**: A Function node evaluates whether any resources' usage exceeds the predefined 80% threshold. 5. **Alerts**: If any metric exceeds the threshold, an email alert is sent through an Email node, ensuring that administrators can react promptly to potential issues. # Setup Steps 1. **Configure SSH Nodes**: Update each SSH node with the appropriate credentials and target server details where the resource checks will be performed. 2. **Set Thresholds**: If different sensitivity levels are required, review and adjust the resource usage thresholds within the Function node. 3. **Email Configuration**: Enter the correct email addresses in the Email node for where alerts should be sent. Ensure that your email-sending credentials and server details are correctly configured.
n8n$9.99Automate Backup of Self-Hosted n8n Workflows to Google Drive with Version Control
This workflow automates the backup of workflows from a self-hosted n8n instance to Google Drive, ensuring version control and easy recovery in case of accidental modifications or deletions.
n8n$14.99Automate 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 Daily n8n Workflow Backups to Nextcloud with 7-Day Retention
This workflow automates the daily backup of n8n workflows to Nextcloud, ensuring the last 7 days of backups are retained while older ones are deleted to save space.
n8n$9.99Automate Nightly n8n Workflow Backups to Google Drive
This workflow automates the nightly backup of all n8n workflows to a designated Google Drive folder. It organizes backups by moving previous ones to an 'n8n_old' folder and deletes backups older than a specified age.
n8n$24.99WebhookDocs: Generate Swagger Preview of Your Active Workflows
# How it Works This meta-workflow is designed to intelligently scan all your active workflows in n8n, identify those that contain Webhook nodes, and automatically generate a Swagger (OpenAPI) specification based on them. The output Swagger document reflects all accessible endpoints from your Webhook nodes, making it easier to: - Visualize your API structure - Share your endpoints - Integrate with tools like Postman or Swagger UI  ## Enhanced Parameter Support If you want the Swagger to reflect request parameters (e.g., query or body fields), you can annotate your Webhook nodes using the Note section. When configured properly, these annotations enrich your Swagger documentation with parameter names, types, and descriptions.   # Setup Steps 1. Add the WebhookDocs to n8n. Import the WebhookDocs JSON file into your n8n instance. 2. Activate the WebhookDocs (you can also use the test-endpoint). Annotate Webhook Nodes (Optional but Recommended). To enable parameter documentation, open the Note section of each Webhook node and add annotations in the following format: ``` //@body field_name string description //@query field_name string description ``` 3. Open the page https://n8n.yourinstance.com/webhook/swagger
n8n$4.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.99Automate Hourly n8n Workflow Backups to Google Drive with Auto Cleanup
Ensure the safety of your n8n workflows by automatically backing them up to Google Drive every hour, with an integrated cleanup process to manage storage efficiently.
n8n$14.99JSON String Validator via Webhook
This n8n template provides a simple yet powerful utility for validating if a given string input is a valid JSON format. You can use this to pre-validate data received from external sources, ensure data integrity before further processing, or provide immediate feedback to users submitting JSON strings. --- ## How it works - Webhook: This node acts as the entry point for the workflow, listening for incoming POST requests. It expects a JSON body with a single property: - jsonString: The string that you want to validate as JSON. - Code (JSON Validator): This node contains custom JavaScript code that attempts to parse the jsonString provided in the webhook body. - If the jsonString can be successfully parsed, it means it's valid JSON, and the node returns an item with valid: true. - If parsing fails, it catches the error and returns an item with valid: false and the specific error message. - This logic is applied to each item passed through the node, ensuring all inputs are validated. - Respond to Webhook: This node sends the validation result (either valid: true or valid: false with an error message) back to the service that initiated the webhook request. --- ## Who is it for? ### This workflow is ideal for: - Developers & Integrators: Pre-validate JSON payloads from external systems (APIs, webhooks) before processing them in your workflows, preventing errors. - Data Engineers: Ensure the integrity of JSON data before storing it in databases or data lakes. - API Builders: Offer a dedicated endpoint for clients to test their JSON strings for validity. - Customer Support Teams: Quickly check user-provided JSON configurations for errors. - Anyone handling JSON data: A quick and easy way to programmatically check JSON string correctness without writing custom code in every application. --- ## Data Structure When you trigger the webhook, send a POST request with a JSON body structured as follows: ``` { "jsonString": {"name": "n8n", "type": "workflow"} } ``` Example of an invalid JSON string: ``` { "jsonString": {"name": "n8n"} // Missing quotes around name } ``` The workflow will return a JSON response indicating validity: For a valid JSON string: ``` { "valid": true } ``` For an invalid JSON string: ``` { "valid": false, "error": "Unexpected token n, {'name': 'n8n'} is not valid JSON" } ``` --- ## Setup Instructions - Import Workflow: - In your n8n editor, click Import from JSON and paste the provided workflow JSON. - Configure Webhook Path: - Double-click the Webhook node. - In the Path field, set a unique and descriptive path (e.g., /validate-json). - Activate Workflow: - Save and activate the workflow. --- ## Tips This JSON validator workflow is a solid starting point. Consider these enhancements: - Enhanced Error Feedback: - Upgrade: Add a Set node after the Code node to format the error message into a more user-friendly string before responding. - Leverage: Make it easier for the caller to understand the issue. - Logging Invalid Inputs: - Upgrade: After the Code node, add an IF node to check if valid is false. If so, branch to a node that logs the invalid jsonString and error to a Google Sheet, database, or a logging service. - Leverage: Track common invalid inputs for debugging or improvement. - Transforming Valid JSON: - Upgrade: If the JSON is valid, you could add another Function node to parse the jsonString and then operate on the parsed JSON data directly within the workflow. - Leverage: Use this validator as the first step in a larger workflow that processes JSON data. - Asynchronous Validation: - Upgrade: For very large JSON strings or high-volume requests, consider using a separate queueing mechanism (e.g., RabbitMQ, SQS) and an asynchronous response pattern. - Leverage: Prevent webhook timeouts and improve system responsiveness.
n8n$4.99Automate Docker Registry Cleanup and Notifications
This workflow automates the cleanup of old image tags in a Docker registry, preserving the latest and most recent tags, and sends notifications upon completion or failure.
n8n$14.99Automate Uptime Monitoring with Scheduled Checks and Alerts
This n8n workflow automates website uptime monitoring using scheduled checks. It alerts you via email and Slack if any site goes down, ensuring you are promptly informed.
n8n$9.99Automate Core Web Vitals Monitoring with Lighthouse and Alerts
This workflow automates the monitoring of Core Web Vitals using Lighthouse reports, sending alerts via Telegram and logging data in Google Sheets for performance tracking.
n8n$9.99Automate n8n Updates Using Version Check and Portainer Webhook
This workflow automatically updates your n8n container via a Portainer webhook whenever a new version is available, eliminating the need for manual checks.
n8n$9.99Automate GitLab Merge Requests Using APIs with n8n
# **Who is this template for?** This template is designed for developers, DevOps engineers, and automation enthusiasts who want to streamline their GitLab merge request process using n8n, a low-code workflow automation tool. It eliminates manual intervention by automating the merging of GitLab branches through API calls. # **How it works?** - **Trigger the workflow**: The workflow can be triggered by a webhook, a scheduled event, or a GitLab event (e.g., a new merge request is created or approved). - **Fetch Merge Request Details**: n8n makes an API call to GitLab to retrieve merge request details. - **Check Merge Conditions**: The workflow validates whether the merge request meets predefined conditions (e.g., approvals met, CI/CD pipelines passed). - **Perform the Merge**: If all conditions are met, n8n sends a request to the GitLab API to merge the branch automatically. # **Setup Steps** **1. Prerequisites** - An n8n instance (Self-hosted or Cloud) - A GitLab personal access token with API access - A GitLab repository with merge requests enabled **2. Create the n8n Workflow** - Set up a trigger: Choose a trigger node (Webhook, Cron, or GitLab Trigger). - Fetch merge request details: Add an HTTP Request node to call GET /merge_requests/:id from GitLab API. - Validate conditions: - Check if the merge request has necessary approvals. - Ensure CI/CD pipelines have passed. - Merge the request: - Use an HTTP Request node to call PUT /merge_requests/:id/merge API. **3. Test the Workflow** - Create a test merge request. - Check if the workflow triggers and merges automatically. - Debug using n8n logs if needed. **4. Deploy and Monitor** - Deploy the workflow in production. - Use n8n's monitoring features to track execution. This template enables seamless GitLab merge automation, improving efficiency and reducing manual work! #### Note: Never hard code API token or secret in your HTTP request.
n8n$9.99Centralized Error Monitoring & Alerts via Telegram, Slack & Other Messengers
## Who is this for? This workflow is designed for developers, DevOps engineers, and automation specialists who manage multiple n8n workflows and need a reliable way to monitor for failures and receive alerts in real time. ## What problem is this workflow solving? Monitoring multiple workflows can be challenging, especially when silent failures occur. This workflow helps ensure you're immediately informed whenever another workflow fails, reducing downtime and improving system reliability. ## What this workflow does The solution consists of two parts: **ERROR NOTIFIER**: A centralized workflow that sends alerts through your chosen communication channel (e.g., Telegram, WhatsApp, Gmail). **ERROR ALERTER**: A node snippet to be added to any workflow you want to monitor. It captures errors and triggers the **ERROR NOTIFIER** workflow. Once set up, this system provides real-time error alerts for all integrated workflows. ## Setup 1. Import both workflows: - **ERROR NOTIFIER** (centralized alert handler) - **ERROR ALERTER** (to be added to your monitored workflows) 2. Add credentials for your preferred alert channel: - WhatsApp (OAuth or API) - Telegram - Gmail - Discord - Slack 3. Activate the workflows: - Ensure **ERROR NOTIFIER** is active and ready to receive triggers. - Paste **ERROR ALERTER** at the end of each workflow you want to monitor, connecting it to the error branch. Sign up for a [free consultation](https://boanse.gumroad.com/l/free_n8n_consultation) and find out how n8n can help you.
n8n$9.99Automate N8N Audit and Failure Monitoring with InfluxDB
Automatically collect and send N8N audit logs and failed workflow executions to InfluxDB for comprehensive monitoring and analysis.
n8n$14.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.99Auto-Update n8n to Latest Version with Coolify
Automatically detect new n8n releases (stable or beta) from GitHub, update Coolify environment variables, and trigger deployments. --- #### **Functionality** This workflow automates the deployment of [n8n](https://n8n.io) releases to a [Coolify](https://coolify.io) instance. It supports two tracks: 1. **Beta Releases**: Checks GitHub every minute for prereleases, filters duplicates, updates the `N8N_VERSION` environment variable, and deploys. 2. **Stable Releases** (disabled by default): Checks the latest stable release hourly and deploys. Key Features: - **Deduplication**: Ensures no repeated deployments for the same release. - **Version Parsing**: Extracts the semantic version (e.g., `1.34.0`) from GitHub release names. - **Coolify Integration**: Updates environment variables and triggers deployments via API. --- #### **Expected Outcomes** - New n8n beta/stable releases detected via GitHub API. - Coolify environment variable `N8N_VERSION` updated to the latest version. - Automatic deployment triggered in Coolify. --- ### **Setup Guide** 1. **Replace Placeholders**: - Update `m8ccg8k44coogsk84swk8kgs` in the `Update ENV` and `Deploy` nodes with your Coolify **Application UUID**. 2. **Configure Credentials**: - Add Coolify API credentials (`httpHeaderAuth`) with a valid API token in the headers. 3. **Enable Triggers**: - Toggle the `Auto Update Latest Release` node if stable releases are desired. Adjust schedule intervals as needed. 4. **Test**: - Run the workflow manually to validate API connections and version parsing. --- ### **SEO Keywords** Automated Deployment, n8n CI/CD, Coolify Integration, GitHub Release Monitoring, Environment Variable Management, Beta Release Automation.
n8n$9.99Automate n8n Credential Backups to Google Drive
Effortlessly back up your n8n credentials to Google Drive with this automated workflow, ensuring secure and regular backups for recovery and migration purposes.
n8n$9.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.99
Related categories
Custom AI Systems & Services
Our team of experienced AI builders will help build custom AI systems, workflows, and solutions.
Request Custom Work