Development & IT Automation Workflows — Page 3 | Neura Market

Neura Market/Categories

Home/Categories/Development & IT

Development & IT Workflows

Software development and IT operations

Automate 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.99
Automate 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.99
Automate 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

Marketplace

Prompts
Workflows
Agents Store
Workflow Packs
Categories
Marketplace

Directories

AI Tools Directory
ChatGPT
Claude
Gemini
Cursor
Grok
DeepSeek
Perplexity
CoPilot
Midjourney
Stable Diffusion
MCP Servers
.md Directory
All Directories

Free Tools

AI Text Humanizer
AI Content Detector
Workflow Generator
Model Comparison
AI Pricing Calculator
AI Benchmarks
ROI Calculator
All Free Tools

Resources

AI News
Blog
AI Answers
Error Solutions
AI Tutorials
AI Models
Integrations
Alternatives
n8n vs Zapier
Make vs Zapier
n8n vs Make
Resource Library
Documentation
API Access to Our Data

Community

AI Newsletter
AI Jobs
AI Events
AI Companies
Start Selling
Sell n8n Workflows
Sell AI Agents
Sell Prompts
Creator Guide
Advertise
Affiliates

Company

About
Contact
Help
Careers
Pricing
Terms
Privacy
License
DMCA

The #1 Newsletter in AI

Weekly updates, news, and content that matter.

© 2026 Neura Market. All rights reserved.

$9.99

Automate 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.

Automate 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...

Webhook Creation and Job Listing Scraping Workflow

This workflow automates the scraping of job listings from Indeed using Bright Data, with webhook integration.

Automate 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.

JSON 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.

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.

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.

Automate 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.

Centralized 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.

Automate 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.

Auto-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.

Automate 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.

Automate 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.

Automate 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.

Automate 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.

Automate 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 ...

Automated Service Health Monitoring with Slack Alerts

This workflow performs scheduled health checks on your web services or APIs, verifies failures with a second check, and sends alerts to Slack if a service fails twice consecutively. It minimizes false positives and reduces alert fatigue.

Automate n8n Workflow Backups to GitHub with Email and Telegram Alerts

Ensure your n8n workflows are safely backed up to GitHub and receive notifications via email or Telegram. This automation helps prevent data loss during updates or migrations.

Deploy Code to GitHub with Natural Language via Slack & Claude 3.5

## Github Deployer Agent ## Overview The Github Deployer Agent is an intelligent automation tool that integrates with Slack to streamline code deployment workflows. Powered by Anthropic's Claude 3.5 and Avily for web search, it enables seamless, context-aware file pushes to a GitHub repository with minimal user input. ## Capabilities - Accepts natural language via Slack - Automatically pushes code to a default GitHub repository - Uses Claude 3.5 for code generation and decision-making - Leverages Avily for real-time web search to enhance context - Supports folder structure hints to ensure clean and organized repositories ## Required Connections To operate correctly, the following integrations must be in place: - Slack API token with permission to read messages and post responses - GitHub Personal Access token with repo write permissions - Avily API Key for external search functionality - Claude 3.5 API Access via Anthropic Detailed configuration instructions are provided in the workflow. ## Example Input From Slack, you can send messages like: Generate a basic `README.md` for my Python project and store it in the root directory. ## Customizing This Workflow You can tailor the workflow by: - Modifying default folder paths or repository settings - Integrating Jira node to use issue keys as default folder naming - Adding Slack file upload option

Automate n8n Workflow Backups to GitLab

Automatically retrieve and back up all workflows from an n8n instance to a GitLab repository, updating only when changes are detected.

Readable Workflow Export & Deployment Pipeline for Multi-Environment CI/CD

**This n8n workflow template uses community nodes and is only compatible with the self-hosted version of n8n.** ## Export workflows with readable names, tagged for different environments To ensure understandable workflow exports, ease of use in delivery pipelines, and a better developer experience, this workflow helps with exporting workflows. ## Inner workings - First, the workflow ensures that the directory structure for storing the workflows is correct. - Exports all workflows. - Next, it processes all workflow files and stores them with readable names. - Based on tags, it will also export to `dev` and `prod` folders for easy commit and usage in a delivery pipeline. ## Configuration No special setup is required for readable exporting. ## Usage Create a workflow and tag it with **Auto deploy to dev**. Run the workflow, this will create the needed folders and workflows with readable names. Commit these in your version control. Have a CI/CD pipeline build an n8n container. - See the attached Dockerfile. Check our **Auto Starter workflow** for auto-starting workflows after deployment. ## CI/CD Bonus: Attached are two nodes with some example configuration on building your own automated n8n deployment. - A Dockerfile, to get the new entrypoint and exported workflows packaged in the container. - An updated entrypoint to build your own container, import the workflows, and run the Auto Starter. Set the following environment variables: - `SARUP_WORKFLOWS_LOAD_LOCATION`: to specify the folder to import from and distinguish between environments. - `SARUP_WORKFLOW_ID`: the ID of the workflow to run after starting n8n. > **Note:** The Instance Started n8n trigger won't work, as all workflows are disabled upon import.

← PreviousPage 3 of 17Next →

Related categories

Communication (2,463)AI (1,930)Business Operations & ERPs (1,540)Other (1,425)Productivity (1,202)Marketing (1,145)Data & Analytics (995)File & Document Management (802)CRM - Sales (604)Notifications (580)

Need a custom development & it workflow?

Our automation experts build tailored workflows for your exact stack and process.

Request a Custom Workflow