Development & IT Automation Workflows — Page 2 | Neura Market
    Neura Market
    Neura Market    /Categories
    Marketplace
    Directories
    Resources
    Home/Categories/Development & IT

    Development & IT Workflows

    Software development and IT operations

    • Automate Website Uptime Monitoring with n8n

      Monitor your website's uptime and receive alerts via email and Telegram when downtime is detected, using n8n's powerful automation capabilities.

      n8nFree

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

    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 Models
    • Integrations
    • Alternatives
    • n8n vs Zapier
    • Make vs Zapier
    • n8n vs Make
    • Resource Library
    • Documentation

    Community

    • 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

    Stay Updated

    Get the latest AI tools and insights delivered to your inbox.

    Neura Market Logoneuramarket

    © 2026 Neura Market. All rights reserved.

    n8nFree

  1. Automated n8n Workflow Backup to Google Drive

    Securely back up all your n8n workflows as JSON files to Google Drive, ensuring disaster recovery and version control.

    n8nFree

  2. Automate Server Uptime Monitoring with Google Sheets and Email Alerts

    This workflow automates server uptime monitoring by pinging servers listed in a Google Sheet every minute. It logs server status and sends email alerts if any server is down, ensuring you stay informed about server health without manual checks.

    n8nFree

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

    n8nFree

  4. Scheduled 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, ...).

    n8nFree

  5. Automated 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.

    n8nFree

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

    n8nFree

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

    n8nFree

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

    n8nFree

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

    n8nFree

  10. Automate Docker Container Updates with Telegram Approval

    Streamline Docker container updates with automated version checks and Telegram-based approval for controlled deployments.

    n8nFree

  11. Restore 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**

    n8nFree

  12. WebhookDocs: 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 ![image.png](fileId:1349) ## 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. ![image.png](fileId:1348) ![image.png](fileId:1347) # 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

    n8nFree

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

    n8nFree

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

    n8nFree

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

    n8nFree

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

    n8n$19.99

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

    n8nFree

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

    n8nFree

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

    n8nFree

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

    n8nFree

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

    n8nFree

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

    n8nFree
    23. ← PreviousPage 2 of 17Next →

    Related categories

    Communication (2,463)AI (1,929)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