Development & IT Workflows
Software development and IT operations
Automate 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 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 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 HR Job Posting and Evaluation with AI Integration
This workflow automates the HR job posting and evaluation process, enabling organizations to efficiently manage job applications while leveraging the power of AI. By using this workflow, HR teams can save time, reduce manual errors, and enhance th...
Zapier$13.96Scheduled FXP/SFTP to MinIO Backup with Preserved Folder Structure
# Automated FP/SFP to MinIO Object Backup with Scheduling → Can work with FP/SFP Servers like your WordPress Website! ## What this workflow does? This workflow performs automated, periodic backups of files from an FP or SFP server directory to a MinIO S3 bucket running locally or on a dedicated container/VM/server. It can also work if the MinIO bucket is running on a remote cloud provider's infrastructure; you just need to change the URL and keys. ## Who's this intended for? Storage administrators, cloud architects, or DevOps who need a simple and scalable solution for retrieving data from a remote FP or SFP Server. This can also be practical for WordPress Devs that need to backup data from a server hosting a WordPress Website. In that case, you'll just need to specify the folder that you want to backup (could be one from wordpress/uploads or even the root one). ## How it works This workflow uses commands to list and download files from a specific directory on an FP-SFP Server, then sends them to MinIO using their version of the S3 API. The source directory can be a specific one or the entire server (the root directory). ## Requirements None, just a source folder/directory on an FP/SFP Server and a destination bucket on MinIO. You'll also need to get MinIO running. You're using Proxmox VE? Create a MinIO LXC Container: https://community-scripts.github.io/ProxmoxVE/scripts?id=minio ## Need a Backup from another Cloud Storage Provider? Need automated backup from another Cloud Storage Provider? → Check out our templates, we've done it with AWS, Azure, and GCP, and we even have a version for FP/SFP servers! ⚫ These workflows can be integrated into bigger ones and modified to best suit your needs! You can, for example, replace the MinIO node with another S3 Bucket from another Cloud Storage Provider (Backblaze, Wasabi, Scaleway, OVH, ...).
n8n$4.99Automate API Uptime Monitoring with Google Sheets and WhatsApp Alerts
This n8n workflow automates API uptime monitoring by checking API availability every 15 minutes. It retrieves API details from Google Sheets, implements retry logic, and sends WhatsApp alerts for any downtime.
n8n$14.99Automate Email Header Analysis for Security Threat Detection in Outlook
This workflow automates the analysis of email headers in Outlook to detect potential security threats by verifying authentication protocols and checking IP reputation.
n8n$19.99Kubernetes RCA and Alerting Using Gemini, Loki, Prometheus, Slack
## Summary This n8n workflow automates Kubernetes root cause analysis (RCA) and incident alerting by integrating with Loki, Prometheus, and Slack. It streamlines log collection, cluster health monitoring, and AI-driven RCA with Gemini, saving DevOps teams hours of manual troubleshooting. Designed for production-grade Kubernetes environments, this plug-and-play workflow delivers actionable insights directly to your Slack channels. ## Who's It For - DevOps Engineers automating Kubernetes monitoring and incident response. - Site Reliability Engineers (SREs) aiming to reduce mean time to resolution (MTTR). - Teams using n8n, Slack, Loki, and Prometheus for observability and automation. ## What It Does - Pulls logs from Loki, filtering for critical errors. - Monitors cluster health, checking pending, not ready, or restarting pods. - Fetches Prometheus metrics for nodes, namespaces, and services. - Generates AI-driven RCA using Google Gemini to analyze logs and metrics. - Sends formatted Slack alerts with deduplication and batching for readability. - Tracks pod lifecycle events, including crashloop states and restarts. ## How It Works - Log Collection: The workflow uses an n8n HTTP Request node to pull logs from Loki, filtering for critical errors. - Cluster Monitoring: A Kubernetes SSH node checks pod states (terminated or running). If terminated, ignore those pods for RCA. - Metrics Fetching: Prometheus metrics are retrieved via HTTP Request for nodes and services. - RCA Generation: Logs and metrics are merged into structured prompts for Google Gemini AI to produce actionable RCA insights. - Kubernetes Enrichment: RCA from Gemini goes to this node and enriches with Kubernetes documentation and provides the documentation links in RCA. - Slack Notifications: Alerts are batched, deduplicated, and sent to Slack with clear formatting. ## How to Set Up - Import the Workflow: Download the .json file and import it into your n8n instance. ### Configure Credentials: - Add your Loki, Prometheus, and Slack API credentials in the respective nodes (use n8n Credentials Manager if required). - Set up Google Gemini AI credentials for RCA generation. - Test the Workflow: Run the workflow manually to ensure logs, metrics, and alerts are processed correctly. - Schedule Execution: Use n8n's Schedule Trigger to run the workflow at desired intervals (e.g., every 5 minutes). ## Requirements - n8n K8s node installed (self-hosted only, see n8n documentation). - Access to Kubernetes clusters and API. - Loki and Prometheus set up for log and metrics collection. - Slack workspace with webhook access for notifications. - Google Gemini AI API key for RCA generation. ## How to Customize the Workflow - Adjust Filters: Modify the Loki query in the HTTP Request node to focus on specific error patterns. - Change Alert Frequency: Update the Schedule Trigger node for different intervals. - Add More Metrics: Extend the Prometheus node to include additional metrics like CPU or memory usage. - Customize Slack Alerts: Edit the Slack node to change message formatting or add more channels. - Enhance RCA: Adjust the Gemini AI prompt in the Set Fields node for more specific insights. ## Category DevOps / Monitoring & Observability / Kubernetes / AI ## Tags kubernetes, prometheus, slack, alerting, sre, ops, kube-state-metrics, Gemini, AI ## Slack Output 
n8n$24.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.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 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 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 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.99Restore and Recover n8n Credentials from Google Drive Backups with Duplication Protection
**This n8n workflow template uses community nodes and is only compatible with the self-hosted version of n8n.** ## **Restore n8n Credentials from Google Drive Backup** This template enables you to **restore your n8n credentials from a backup file in Google Drive**. It's an essential companion to a credential backup workflow, ensuring you can recover your setup in case of data loss, instance migration, or disaster recovery. The workflow **intelligently checks for existing credentials to prevent accidental overwrites of credentials** with the same name that are already present. This workflow is manually triggered. We recommend you use this restore workflow in conjunction with a backup solution like our [Auto Backup Credentials to Google Drive template](https://aiautomationpro.org/products/n8n-auto-backup-credentials-to-google-drive/). For more powerful n8n templates, visit our website or contact us at [**AI Automation Pro**](https://aiautomationpro.org/). We help your business build custom AI workflow automation and apps. ### Who is this for? This workflow is for n8n administrators and users who have backed up their n8n credentials to Google Drive (e.g., using a companion backup template) and need to restore them to the same or a different n8n instance. It's crucial for those managing self-hosted instances. ### What problem is this workflow solving? / use case If an n8n instance becomes corrupted, needs to be migrated, or if credentials are accidentally deleted, a manual re-creation of all credentials can be extremely time-consuming and error-prone. This workflow automates the restoration process from a known backup, saving significant time and ensuring accuracy. It's particularly useful for: - Disaster recovery. - Migrating n8n instances. - Quickly setting up a new n8n instance with existing credentials. ### What this workflow does The workflow is manually triggered and performs the following operations: 1. **Fetch Current Credentials:** - An On Click trigger starts the process. - It executes the command `npx n8n export:credentials --all --decrypted` via the Execute Command Get All Credentials node to get a list of all credentials currently in your n8n instance. - This list is then processed by JSON Formatting Data and Aggregate Credentials nodes to extract just the names of existing credentials for comparison. 2. **Download Backup File from Google Drive:** - The Google Drive Get Credentials File node searches your Google Drive for the `n8n_backup_credentials.json` file. - The Google Drive Download File node then downloads the found file. 3. **Process Backup Data:** - The Convert Files to JSON (an Extract From File node) converts the downloaded file content, expected to be JSON, into a usable JSON object. - Split Out nodes then process this data to handle individual credential entries from the backup file. 4. **Loop and Restore Credentials:** - The Loop Over Items (a SplitInBatches node) iterates through each credential from the backup file. - **Duplicate Check:** For each credential, an IF node (Check For Skipped Credentials) checks two conditions using an OR combinator: - If the credential name from the backup (`$(Loop Over Items).item.json.name`) is empty. - If a credential with the same name already exists in the current n8n instance (by checking against the list from the Aggregate Credentials node). - **Conditional Restore:** If the credential name is NOT empty AND it does NOT already exist (i.e., the conditions in the IF node are false), the workflow proceeds to the Restore N8n Credentials node (an n8n API node). This node uses the `name`, `type`, and `data` for each new credential from the backup file to create it in the n8n instance. Credentials with empty names or those already present are skipped as they take the true path of the IF node, which loops back. - A Wait node introduces a 1-second delay after each restoration attempt, to prevent API rate limiting before looping to the next item. ### Step-by-step setup 1. **n8n Instance Environment (for current credentials check):** - The n8n instance must have access to `npx` and `n8n-cli` for the Execute Command Get All Credentials node to function. 2. **Google Drive Credentials:** - Configure the Google Drive Get Credentials File and Google Drive Download File nodes with your Google OAuth2 credentials. 3. **n8n API Credentials:** - Configure the Restore N8n Credentials node with your n8n API credentials. This API key needs permissions to manage credentials. 4. **Backup File Name:** - The workflow is configured to search for a file named `n8n_backup_credentials.json` in the Google Drive Get Credentials File node. If your backup file has a different name or you want to specify a path, update the Query String parameter in this node. ### How to customize this workflow to your needs * **Backup**
n8n$9.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.99Webhook Creation and Job Listing Scraping Workflow
This workflow automates the scraping of job listings from Indeed using Bright Data, with webhook integration.
n8n$14.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.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 Instagram Content Scheduling with Facebook Graph API
This workflow is designed to streamline the process of scheduling and publishing various types of Instagram content, including images, videos, and reels, using the Facebook Graph API. By automating these tasks, users can save significant time and ...
n8n$19.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.99Automated Server Log Cleanup via Email Alerts with SSH - Nginx, Docker, System
This n8n workflow monitors email alerts for disk utilization exceeding 80%, extracts the server IP, logs into the server, and purges logs from Nginx, PM2, Docker, and system files to clear disk space. ### Key Insights - Ensure email alerts are consistently formatted with server IP details. - SSH access must be properly configured to avoid authentication failures. ### Workflow Process 1. Initiate the workflow with the `Check Disk Alert Emails` node when an email triggers on high disk usage. 2. Parse the email to extract the server IP using the `Extract Server IP from Email` node. 3. Set up SSH credentials and paths manually with the `Prepare SSH Variables` node. 4. Execute cleanup commands to delete logs from Nginx, PM2, Docker, and system files using the `Run Log Cleanup Commands via SSH` node. ### Usage Guide - Import the workflow into n8n and configure email and SSH credentials. - Test with a sample email alert to verify IP extraction and log deletion. ### Prerequisites - Email service (e.g., IMAP or API) for alert monitoring - SSH access with valid credentials ### Customization Options Modify the `Prepare SSH Variables` node to target specific log directories or adjust cleanup commands for different server setups.
n8n$4.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.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 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.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