Workflow Templates

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. Configration 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 CICD 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: STARTUP_WORKFLOWS_LOAD_LOCATION: to specify the folder to import from and distinguish between environments. STARTUP_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.

Replicate Line Items on New Deal in HubSpot Workflow Use Case This workflow solves the problem of manually copying line items from one deal to another in HubSpot, reducing manual work and minimizing errors. What this workflow does Triggers** upon receiving a webhook with deal IDs. Retrieves** the IDs of the won and created deals. Fetches** line items associated with the won deal. Extracts** product SKUs from the retrieved line items. Fetches** product details based on SKUs. Creates** new line items for the created deal and associates them. Sends** a Slack notification with success details. Step up steps Create a HubSpot Deal Workflow 1.1 Set up your trigger (ex: when deal stage = Won) 1.2 Add step : Create Record (deal) 1.3 Add Step : Send webhook. The webhook should be a Get to your n8n first trigger. Set two query parameter : deal_id_won as the Record ID of the deal triggering the HubSpot Workflow deal_id_create as the Record ID of the deal created above. Click Insert Data -> The created object Set up your HubSpot App token in HubSpot -> Settings -> Integration -> Private Apps Set up your HubSpot Token integration using the predefined model. Set up your Slack connection Add an error Workflow to monitor errors

This workflow contains community nodes that are only compatible with the self-hosted version of n8n. This automated n8n workflow streamlines the process of screening CVs and validating candidate information using AI and email parsing. The system listens for new emails with CV attachments, extracts and processes the data, and either saves valid CVs to a target directory or notifies HR of invalid submissions. Good to Know The workflow improves efficiency by automating CV screening and validation. Ensures only CVs with essential fields (e.g., name, email, skills) are processed further. Email notifications alert HR to incomplete or invalid CVs for timely follow-up. The system pauses until all CV data is fully loaded to avoid processing errors. How It Works Trigger on New CV Email - Detects new emails with CV attachments. Extract Text from PDF CV - Parses content from attached PDF files. Ensure All CV Data Loaded - Waits until all data is ready for processing. Parse & Structure CV Information - Extracts structured details like name, skills, and experience using AI or custom logic. Check CV for Required Fields - Verifies the presence of essential fields (e.g., name, email, skills). Save Valid CV to Folder - Stores successfully validated CVs into a target directory. Notify HR of Invalid CV - Sends an email alert for incomplete or invalid CVs. Data Sources The workflow processes data from email attachments: CV PDF Files** - Contains candidate information in PDF format. How to Use Import the workflow into n8n. Configure email account credentials for monitoring new CV emails. Set up a target directory for storing validated CVs. Test with sample CV PDFs to verify extraction and validation. Adjust AI or custom logic based on specific required fields. Monitor email notifications for invalid CVs and refine the process as needed. Requirements Email account access with IMAP/POP3 support. PDF parsing capabilities (e.g., OCR or text extraction tools). AI or custom logic for data extraction and validation. A target directory for storing validated CVs. Customizing This Workflow Modify the "Check CV for Required Fields" node to include additional required fields (e.g., education, certifications). Adjust the email notification format to include more details about invalid CVs. Integrate with HR software for seamless candidate tracking. Details The workflow ensures efficient CV screening by automating repetitive tasks. Notifications help maintain a high-quality candidate pool by addressing issues early.

This automated n8n workflow efficiently manages the setup, creation, and deletion of PostgreSQL and MySQL databases on a Linux server, executing tasks in approximately 10 seconds. It automates installation, configuration, and user management with support for remote access. Core Elements Set Parameters** - Defines server details, database type, action, and credentials Type Check** - Confirms the selected database type PostgreSQL Action Check** - Identifies the action for PostgreSQL PostgreSQL Create Check** - Validates creation conditions for PostgreSQL Install PostgreSQL** - Sets up and configures PostgreSQL Create PostgreSQL DB** - Establishes a new PostgreSQL database with user access Delete PostgreSQL DB** - Removes a PostgreSQL database and user MySQL Action Check** - Identifies the action for MySQL MySQL Create Check** - Validates creation conditions for MySQL Install MySQL** - Sets up and configures MySQL Create MySQL DB** - Establishes a new MySQL database with user access Delete MySQL DB** - Removes a MySQL database and user Format Output** - Structures the final workflow output Getting Started Guide Import the workflow into n8n Adjust parameters in the Set Parameters node Execute the workflow Confirm the database operation on the server Necessary Requirements SSH-enabled Linux server Root-level access rights Customization Options Switch db_type between PostgreSQL and MySQL Select action (install, create, delete) via the action parameter Tailor database_name, db_user, and db_password as needed Features Install Database Server - Deploys PostgreSQL or MySQL with optimal configuration Create Database - Generates new databases with assigned users and permissions Delete Database - Eliminates databases and their associated users Parameters to Configure server_host: Your Linux server IP address server_user: SSH username (typically 'root') server_password: SSH password db_type: Select 'postgresql' or 'mysql' action: Select 'install', 'create', or 'delete' database_name: Name of the database to create or delete db_user: Database username db_password: Database password How to Use Copy the JSON code from the artifact Access your n8n workspace Choose "Import from JSON" or "+" → "From JSON" Insert the JSON code Set parameters in the "Set Parameters" node with your server information Run the workflow Workflow Actions Install: Sets up the database server, enables remote access, and initializes the database Create: Establishes a new database with a specific user Delete: Erases the database and its associated user The workflow automatically manages Ubuntu/Debian package setup Service initialization and configuration Remote access setup User and permission assignments Authentication configuration Update the parameters in the "Set Parameters" node with your server specifics and execute the workflow!

This n8n workflow illustrates how to convert PDF files into text with the PDF Toolkit from www.customjs.space. @custom-js/n8n-nodes-pdf-toolkit Notice Community nodes can only be installed on self-hosted instances of n8n. What this workflow does Change** the requested HTML to PDF.. Extract** text from the PDF. Use** a Code node to handle URLs that point to PDF files. Convert** the PDF to text. Requirements Self-hosted** n8n instance. CustomJS API key** for converting PDF to text. HTML** Data to convert PDF files. Code node** for handling URL that indicates PDF file. Workflow Steps: Manual Trigger: Runs with user interaction. HTML to PDF: Request HTML Data Convert HTML to PDF Convert PDF to Text: Convert the generated Text from PDF Usage Get API key from customJS Sign up to customJS platform. Navigate to your profile page Press "Show" button to get API key Set Credentials for CustomJS API on n8n Copy and paste your API key generated from CustomJS here. Design workflow A Manual Trigger for starting workflow. HTTP Request Nodes for downloading PDF files. Code node for handling URL that indicates PDF file. Convert PDF to Text. You can replace logic for triggering and returning results. For example, you can trigger this workflow by calling a webhook and get a result as a response from webhook. Simply replace Manual Trigger and Write to Disk nodes.

This workflow provides automated access to the Fire Part Crafter AI model through the Replicate API. It saves you time by eliminating the need to manually interact with AI models and provides a seamless integration for image generation tasks within your n8n automation workflows. Overview This workflow automatically handles the complete image generation process using the Fire Part Crafter model. It manages API authentication, parameter configuration, request processing, and result retrieval with built-in error handling and retry logic for reliable automation. Model Description: PartCrafter is a structured 3D mesh generation model that creates multiple parts and objects from a single RGB image. Key Capabilities High-quality image generation from text prompts** Advanced AI-powered visual content creation** Customizable image parameters and styles** Tools Used n8n**: The automation platform that orchestrates the workflow Replicate API**: Access to the Fire/part-crafter AI model Fire Part Crafter**: The core AI model for image generation Built-in Error Handling**: Automatic retry logic and comprehensive error management How to Install Import the Workflow: Download the .json file and import it into your n8n instance Configure Replicate API: Add your Replicate API token to the 'Set API Token' node Customize Parameters: Adjust the model parameters in the 'Set Image Parameters' node Test the Workflow: Run the workflow with your desired inputs Integrate: Connect this workflow to your existing automation pipelines Use Cases Content Creation**: Generate unique images for blogs, social media, and marketing materials Design Prototyping**: Create visual concepts and mockups for design projects Art & Creativity**: Produce artistic images for personal or commercial use Marketing Materials**: Generate eye-catching visuals for campaigns and advertisements Connect with Me Website**: https://www.nofluff.online YouTube**: https://www.youtube.com/@YaronBeen/videos LinkedIn**: https://www.linkedin.com/in/yaronbeen/ Get Replicate API**: https://replicate.com (Sign up to access powerful AI models) #n8n #automation #ai #replicate #aiautomation #workflow #nocode #imagegeneration #aiart #texttoimage #visualcontent #aiimages #generativeart #machinelearning #artificialintelligence #aitools #automation #digitalart #contentcreation #productivity #innovation

🚫 Email Unsubscribe Handler for Outlook Description This n8n workflow automatically scans recent email replies from your Outlook inbox and identifies unsubscribe requests. If a contact replies with any variation of "unsubscribe" within the past 7 days, the system performs two key actions: Saves the contact’s email address in a BigQuery unsubscribes table (for compliance and tracking). Deletes that contact from the active leads table in BigQuery (to stop future outreach). This flow can be triggered on a schedule (e.g. every 4 hours) or run manually as needed. Key Features 📥 Email Parsing from Outlook: Automatically monitors for replies that contain unsubscribe language. 🧠 Smart Filtering: Captures unsubscribes based on message content, not just subject lines. 🔄 BigQuery Integration: Logs unsubscribed emails and removes them from your leads dataset. 🤝 Connect with Me Description I’m Robert Breen, founder of Ynteractive — a consulting firm that helps businesses automate operations using n8n, AI agents, and custom workflows. I’ve helped clients build everything from intelligent chatbots to complex sales automations, and I’m always excited to collaborate or support new projects. If you found this workflow helpful or want to talk through an idea, I’d love to hear from you. Links 🌐 Website: https://www.ynteractive.com 📺 YouTube: @ynteractivetraining 💼 LinkedIn: https://www.linkedin.com/in/robert-breen 📬 Email: rbreen@ynteractive.com

For every release on GitHub this workflow will create an issue on GitLab. Copy workflow to your n8n Fill in missing fields (credentials & repo names) Based on Cron node to be able to track github repos you're not a member of (as you won't be able to create a webhook). If you do own the repo, you could replace Cron & GH node with a GitHub Trigger.

Description Boost your productivity and keep your Asana workspace clutter-free with this n8n workflow. It automatically scans for tasks whose due dates have passed and reschedules them to the current date, ensuring no important to-dos slip through the cracks. Additionally, any completed tasks in Asana with an overdue date are removed, maintaining a clear, organized task list. Key Benefits Streamline Task Management**: No more manual updates—let the workflow reschedule overdue tasks for you. Optimize Workspace Organization**: Eliminate finished tasks to focus on active priorities and reduce clutter. Save Time and Effort**: Automate repetitive maintenance, freeing you to concentrate on what truly matters. Configuration Steps Add your Asana credentials Schedule the workflow to run at desired intervals (e.g., daily or weekly). Select your Workspace Name and your Assignee Name (user) in the Get user tasks node (Optional) Tailor filtering conditions to match your preferred due-date rules and removal criteria. Activate the workflow and watch your Asana workspace stay up to date and clutter-free.

Task: Conditional filtering and branching items Why: Filtering and branching data based on conditions allows you to build complex workflows that work with more than one data flow scenario Main use cases: Filter out data that is not relevant for the rest of the workflow Split data to several branches of the workflow, where we want the data to be treated differently in the rest of the workflow

Use case If you have a form where potential leads reach out, then you probably want to analyze those leads and send a notification if certain requirements are met, e.g. employee number is high enough. MadKudu is built exactly to solve this problem. We use it along with Hunter to alert on Slack for high quality leads. How to setup Add you MadKudu, Hunter, and Slack credentials Set the Slack channel Click the Test Workflow button, enter your email and check the Slack channel Activate the workflow and use the form trigger production URL to collect your leads in a smart way How to adjust this template You may want to raise or lower the threshold for your leads, as you see fit.

Make your n8n instance faster, cleaner, and more efficient by deleting old workflow executions — while keeping only the most recent ones you actually need. Whether you're using n8n Cloud or self-hosted, this lightweight workflow helps reduce database/storage usage and improves UI responsiveness, using only official n8n nodes. 🔍 Description Automatically clean up old executions in your n8n instance using only official nodes — no external database queries required. Whether you're on the Cloud version or running self-hosted, this workflow helps you optimize performance and keep your instance tidy by maintaining only the most recent executions per workflow. Ideal for users managing dozens or hundreds of workflows, this solution reduces storage usage and improves the responsiveness of the n8n UI, especially in environments where execution logs can accumulate quickly. ✅ What It Does Retrieves up to 250 recent executions across all workflows Groups executions by workflow Keeps only the most recent N executions per workflow (value is configurable) Deletes all older executions (regardless of their status: success, error, etc.) Works entirely with native n8n nodes — no external database access required Optionally: set the number of executions to keep as 0 to delete all past executions from your instance in a single run 🛠️ How to Set Up 🔑 Create a Personal API Key in your n8n instance: Go to Settings → API Keys → Create a new key 🔧 Create a new n8n API Credential (used by both nodes): In your n8n credentials panel: Name: anything you like (e.g., “Internal API Access”) API Key: paste the Personal API Key you just created Base URL: your full n8n instance URL with the /api/v1 path, e.g. https://your-n8n-instance.com/api/v1 ✅ Use this credential in both: The Get Many Executions node (to fetch recent executions) The Delete Many Executions node (to remove outdated executions) 🧩 In the “Set Executions to Keep” node: Edit the variable executionsToKeep and set the number of most recent executions to retain per workflow (e.g. 10) Tip: Set it to 0 to delete all executions 📦 Note: The “Get Many Executions” node will retrieve up to 250 executions per run — this is the maximum allowed by the n8n API. 🧠 No further setup is required — the filtering and grouping logic is handled inside the Code Node automatically. 🧪 Included Nodes Overview 🕒 Schedule Trigger → Set to run daily, weekly, etc. 📥 Get Many Executions → Fetches past executions via n8n API 🛠️ Set Executions to Keep → Set how many recent ones to keep 🧠 Code Node → Filters out executions to delete per workflow 🗑️ Delete Executions → Deletes outdated executions 💡 Why Use This? Reduce clutter and improve performance in your n8n instance Maintain execution logs only when they’re useful Avoid bloating your storage or database with obsolete data Compatible with both n8n Cloud and self-hosted setups Uses only official, supported n8n nodes — no SQL, no extra setup 🔒 This workflow modifies and deletes execution data. Always review and test it first on a staging instance or on a limited set of workflows before using it in production.