Development & IT Workflows
Software development and IT operations
Real-time Data Breach Monitoring with Have I Been Pwned
Automatically monitor Have I Been Pwned for new data breaches every 15 minutes and receive alerts for any new breaches.
n8n$14.99Integrate NixGuard and Wazuh for Real-Time Security Insights in n8n
Seamlessly integrate NixGuard API into your n8n workflows for real-time security insights using your API key. This workflow provides rapid Retrieval-Augmented Generation (RAG) event knowledge with Wazuh integration, enhancing your security infrastructure.
n8n$9.99Automate SIEM Alert Enrichment with MITRE ATT&CK, Qdrant, and Zendesk in n8n
Enhance your cybersecurity operations by automating SIEM alert enrichment using MITRE ATT&CK intelligence, Qdrant vector storage, and Zendesk ticketing in n8n. This workflow streamlines alert processing, providing actionable insights and remediation steps.
n8n$14.99Automate Email Header Analysis for Security Insights in Gmail
Enhance your email security by automating the analysis of Gmail email headers to detect IP reputation, spoofing, and sender authenticity.
n8n$19.99Automated Vulnerability Scanning and Reporting with Nessus, AI, and Google Sheets
This workflow automates vulnerability scanning using Nessus, applies AI-based risk triage, and generates comprehensive reports in Google Sheets. It is designed for security teams to streamline compliance with NIST CSF and CISA KEV guidelines.
n8n$24.99š ļø Monica CRM Tool MCP Server: All 52 Operations
Complete zero-config MCP server exposing all 52 Monica CRM Tool operations to AI agents via webhook. Pre-built with official n8n nodes, AI expressions, and error handling.
n8n$29.99Automated AI-Powered Workflow Maintenance with Google Workspace Integration
Enhance your n8n instance management with an AI-driven system for intelligent workflow selection and maintenance. This automation handles security audits, workflow suspension, backups, and exports with smart filtering and scheduling.
n8n$24.99Automated IP Reputation Analysis and SOC Alerting with Splunk, VirusTotal, and AlienVault
Streamline your security operations by automating IP reputation checks and generating threat summaries using Splunk alerts, VirusTotal, and AlienVault. This workflow enhances your SOC's efficiency by providing actionable insights without the need for coding.
n8n$9.99Automate Malicious File Detection and Response with Wazuh, VirusTotal, and Slack Alerts
Streamline the detection and reporting of potentially malicious files using Wazuh alerts and VirusTotal hash validation, with automated Slack alerts and incident creation.
n8n$9.99Manage Cloudflare DNS Records with AI-Powered Chat Assistant
 ### This n8n flow demos basic dev-ops operation task, DNS records management. **AI agent** with light and basic prompt functions like `getter` and `setter` for DNS records. In this special case, we are managing a remote DNS server, via **API calls** - that are handled on the **CloudFlare** platform side. Use-cases for this flow can be standalone, or you can chain it in your pipeline to get powerful infrastructure flows for your needs. ## How it works - We created a basic agent and gave it a prompt to know about one tool: cf_tool - a subroutine (to itself flow - or it can be a separate dedicated one). - The prompt has defined arguments that are needed for passing them when calling the agent, for each action specifically. - The tool itself has a basic if switch that is - based off an action call - calling a specific CloudFlare API endpoint (and pass down the args from the tool). ### Requirements For storing and processing of data in this flow, you will need: - CloudFlare.com API key/token - for retrieving your data (https://dash.cloudflare.com/?to=/:account/api-tokens) - OpenAPI credentials (or any other LLM provider) saved - for agent chat - (Optional) PostgreSQL table for chat history saving ### Official CloudFlare API Documentation For full details and specifications, please use API documentation from: https://developers.cloudflare.com/api/ #### LinkedIn post Let me know if you found this flow useful on my LinkedIn post > [here](https://www.linkedin.com/posts/mkdizajn_manage-cloudflare-dns-records-with-ai-powered-activity-7358119317768409088-7hRV?utm_source=share&utm_medium=member_desktop&rcm=ACoAAAYKYd8B0_a-uIsW3piMYLQCgdQDd0yfrPc). Tags: `#cloudflare`, `#dns`, `#domain`
n8n$14.99Automated Workflow Backups with Google Drive and Slack Notifications
## Efficient loop-less N8N Workflow Backup Automation to Google Drive **This workflow eliminates traditional loop-based processing entirely, delivering unprecedented performance and reliability even when the number of workflows to be processed are large.** ### **What Makes This Different:** - **NO SplitInBatches node** - Traditional workflows use loops to process workflows one by one. - **NO individual file uploads** - No more multiple Google Drive API calls. - **NO batch error handling** - Eliminates complex loop iteration error management. - **ALL workflows processed simultaneously** - Revolutionary single-operation approach. - **Single compressed archive** - One ZIP file containing all workflows. - **One Google Drive upload** - Maximum efficiency, minimum API usage. ### **Key Benefits of Non-Loop Architecture:** - **3-5x Faster Execution** - Eliminated loop overhead and multiple API calls. - **Reduced API Costs** - Single upload instead of dozens of individual operations. - **Higher Reliability** - Fewer failure points, centralized error handling. - **Better Scalability** - Performance doesn't degrade with workflow count. - **Large Workflow Support** - Efficiently handles hundreds of workflows without performance degradation. - **Easier Maintenance** - Simpler workflow structure, easier debugging. - **Cleaner Monitoring** - Single success/failure point instead of loop iterations. --- ## Who's it for This template is designed for **n8n users, DevOps engineers, system administrators, and IT professionals** who need reliable, automated backup solutions for their n8n workflows. It's perfect for businesses and individuals who want to ensure their workflow automation investments are safely backed up with intelligent scheduling, compression, and cloud storage integration. ## How it works / What it does This workflow creates an **intelligent, automated backup system** that transforms n8n workflow backups from inefficient multi-file operations into streamlined single-archive automation. The system: 1. **Triggers automatically every 4 hours** or manually on-demand. 2. **Creates timestamped folders** in Google Drive for organized backup storage. 3. **Retrieves all n8n workflows** via the n8n API in a single operation. 4. **Converts workflows to JSON** and aggregates binary data efficiently. 5. **Compresses all workflows into a single ZIP archive** (eliminating the need for loops). 6. **Uploads the compressed backup** to Google Drive in one operation. 7. **Provides real-time Slack notifications** for monitoring and alerting. **Key Innovation: No Loops Required** - Unlike traditional backup workflows that use SplitInBatches or loops to process workflows individually, this system processes all workflows simultaneously and creates a single compressed archive, dramatically improving performance and reliability. ## How to set up ### 1. Configure Google Drive API Credentials - Set up Google Drive OAuth2 API credentials. - Ensure the service account has access to create folders and upload files. - Update the parent folder ID where backup folders will be created. ### 2. Configure n8n API Access - Set up internal n8n API credentials for workflow retrieval. - Ensure the API has permissions to read all workflows. - Configure retry settings for reliability. ### 3. Set up Slack Notifications - Configure Slack API credentials for the notification channel. - Update the channel ID where backup notifications will be sent. - Customize notification messages as needed. ### 4. Schedule Configuration - The workflow automatically runs every 4 hours. - Manual execution is available for immediate backups. - Adjust the schedule in the Schedule Trigger node as needed. ### 5. Test the Integration - Run a manual backup to verify all components work correctly. - Check Google Drive for the created backup folder and ZIP file. - Verify Slack notifications are received. ## Requirements - **n8n instance** (self-hosted or cloud) with API access. - **Google Drive account** with API access and sufficient storage. - **Slack workspace** for notifications (optional but recommended). - **n8n workflows** that need regular backup protection. ## How to customize the workflow ### Modify Backup Frequency - Adjust the Schedule Trigger node for different intervals (hourly, daily, weekly). - Add multiple schedule triggers for different backup types. - Implement conditional scheduling based on workflow changes. ### Enhance Storage Strategy - Add multiple Google Drive accounts for redundancy. - Implement backup rotation and retention policies. - Add compression options (ZIP, RAR, 7Z) for different use cases. ### Expand Notification System - Add email notifications for critical backup events. - Integrate with monitoring systems (PagerDuty, OpsGenie). - Add backup success/failure metrics and reporting. ### Security Enhancements - Implement backup encryption before upload. - Add backup verification and integrity checks. - Set up access logging and audit trails. ### Performance Optimizations
n8n$9.99Automate 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.
n8n$14.99Automate 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.
n8n$4.99Back up Your Workflows to GitHub
Based on [Jonathan's](https://n8n.io/creators/jon-n8n/) work. Check out his templates. ### How it works This workflow will backup your workflows to GitHub. It uses the n8n API node to export all workflows. It then loops over the data, checks in GitHub to see if a file exists that uses the credentials ID. Once checked, it will: - Update the file on GitHub if it exists; - Create a new file if it doesn't exist; - Ignore if it's the same. ### Who is this for? People wanting to backup their workflows outside the server for safety purposes or to migrate to another server. ### Check out my other templates āļø [**https://n8n.io/creators/solomon/**](https://n8n.io/creators/solomon/)
n8n$14.99Create a Custom GitHub MCP Server for Issue Management
Set up a personalized GitHub MCP server to manage repository issues and comments, enhancing security and control over user access.
n8n$14.99Automated 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.
n8n$9.99Automate NPM Package Installation and Updates for Self-Hosted Environments
Are you looking to install external libraries for your self-hosted N8N instance? This automated workflow makes adding npm packages to your N8N environment quick and effortless.  **Beware, this workflow only works on self-hosted instances.** ## What This Workflow Does This solution automatically installs npm packages like axios, cheerio, or node-fetch in your self-hosted N8N Docker container, making them immediately available in Code nodes. ### Key features - **Automated Installation:** No manual npm commands needed - **Daily Updates:** Scheduled trigger keeps packages current - **Smart Installation:** Only installs missing packages - **Multiple Triggers:** Manual, scheduled, and on startup of the N8N instance so you can upgrade your N8N version without worrying about external libraries. ## How to install and update external libraries automatically ### Step 1: Setting Up Your Environment Variables Before using external libraries in N8N Code nodes, configure these environment variables in your Docker compose file. #### Option A to allow specific external npm packages in N8N Code nodes ``` NODE_FUNCTION_ALLOW_EXTERNAL=axios,cheerio,node-fetch ``` #### Option B to allow all external npm packages in Code nodes ``` NODE_FUNCTION_ALLOW_EXTERNAL=* ``` ### Step 2: Import the external packages workflow Import the workflow into your N8N instance by copying and pasting all nodes. ### Step 3: Input the list of external libraries you need Edit the libraries_set node. Change the comma-separated list (e.g., axios, cheerio, node-fetch). **If you chose Option A above**, update your NODE_FUNCTION_ALLOW_EXTERNAL variable with the same packages. ### Step 4: Start the workflow! Run the workflow manually or let it trigger automatically. ## Why use this to install NPM packages in N8N? Managing external packages manually in N8N can be time-consuming. This workflow automates the entire process, making sure your libraries are always installed and up-to-date.
n8n$4.99Automate Android Feature Flag Cleanup with GitLab, LaunchDarkly, Jira, and Slack
This n8n workflow automates the detection and management of unused feature flags in Android Kotlin/Java codebases by comparing GitLab repository code with LaunchDarkly's feature flag list. It logs results in Google Sheets, creates Jira tickets for cleanup, and sends Slack alerts.
n8n$9.99Automated Error Log Monitoring with Slack Alerts and Jira Ticket Creation
This workflow automates the monitoring of server error logs, sending alerts via Slack and creating Jira tickets for critical issues. It ensures developers are promptly notified of both critical and non-critical errors.
n8n$14.99Auto-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.
n8n$24.99Automate 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)
n8n$14.99Automate Cloud to MinIO Backups with Scheduled Transfers
This workflow automates the periodic backup of objects from AWS S3, Azure Blob, and Google Cloud Storage to a local or remote MinIO bucket. Ideal for storage administrators and DevOps teams seeking a scalable backup solution.
n8n$14.99Automated Workflow Backup and AI Documentation with n8n and Airtable
Securely back up your n8n workflows and generate AI-powered documentation using Airtable. This workflow ensures version control and provides detailed summaries of changes, enhancing workflow management and collaboration.
n8n$24.99Automate Multicloud Security Baselines with OpenAI and Google Drive
Transform cloud provider documentation into auditable security baselines using OpenAI and Google Drive. This workflow automates the extraction, composition, and storage of multicloud security controls.
n8n$24.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