Business Operations & ERPs Workflows
Enterprise resource planning and operations
Automate Solar Lead Management with Google Sheets and Gmail
Streamline solar lead qualification and follow-ups by capturing leads via webhook, storing data in Google Sheets, and sending personalized emails through Gmail.
n8n$14.99Automate Shipment Tracking and Customer Notifications via Google Sheets and WhatsApp
This workflow automates the tracking of shipments using Delhivery and DHL APIs, updates Google Sheets, and sends notifications to customers via WhatsApp and email when shipment statuses change.
n8n$9.99Automate Appointment Reminders and Follow-ups with Twilio
Streamline your client management by automating appointment reminders, follow-ups, and re-engagement offers using Google Calendar, Google Sheets, and Twilio.
n8n$9.99Automate QuickBooks Customer Onboarding with Personalized Welcome Emails
Streamline your new customer onboarding by automatically sending personalized welcome emails to new QuickBooks customers, tracked via Google Sheets.
n8n$14.99Automate Commercial Insurance Submissions with Google Suite, PDF, and Email
### Overview Supercharge your insurance agency's efficiency with this powerful automation template for n8n. Designed specifically for commercial insurance brokers and agents, this workflow transforms the tedious process of manual application submissions into a streamlined, one-click operation. Stop wasting hours on administrative tasks and start closing more deals. This template handles everything from reading new applications in a Google Sheet to generating custom PDFs and emailing them to the right carriers all in **40 seconds**, allowing you to focus on what matters most: your clients. ### How it works This workflow provides a powerful foundation for automating your commercial insurance submissions. It's designed to save you hours of manual work by streamlining the entire process from application intake to carrier communication. At a high level, this is what the flow does: - **1. Fetches New Applications:** Automatically reads new insurance applications from a designated Google Sheet. - **2. Filters Suitable Carriers:** Filters a built-in list of carriers to find the best matches for each application based on revenue and industry requirements. - **3. Generates Professional PDFs:** For each matched carrier, it automatically generates a professional PDF application using a pre-formatted Google Docs template. - **4. Distributes to Carriers:** Emails the personalized application and unique PDF attachment to each matched carrier. - **5. Creates a Summary Report:** Once all submissions are complete, it generates a clean HTML summary report and emails it to the broker. ### Set up steps **Estimated Set Up Time:** 10-15 minutes This template is designed for a quick setup. The detailed, step-by-step instructions are included in the Sticky Notes inside the workflow itself. The main setup steps are: - **1. Copy the Google Sheet:** Make a copy of the provided Google Sheet template to your own Google Drive. - **2. Connect Your Google Account:** Authorize your Google account for the three required nodes (Google Sheets, Google Drive, and Google Docs). - **3. Configure Your Email:** Add your email credentials to the two `Email Send` nodes (one for sending to carriers and one for notifying the broker).
n8n$24.99Automate CSRD XHTML Report Audits with Gmail and GPT-4
Streamline the auditing of CSRD XHTML reports by automating structure validation and report generation using Gmail and GPT-4.
n8n$9.99Automate Stock Portfolio Updates from OneDrive to Excel
Effortlessly synchronize and update your stock portfolio by transferring data from OneDrive CSV files to Excel using n8n. This workflow automates data extraction, transformation, and updates, ensuring your records are always current.
n8n$9.99Update Pipedrive deals based on a scheduled delay after listing all deals
Automatically update Pipedrive deals after listing them and applying a scheduled delay, optimizing your sales process with Pipedrive and Make.
Make$3.99Automate Weekly Square Sales Reports via Gmail
This workflow automates the generation and distribution of weekly sales reports from Square to Gmail, streamlining data analysis for management and finance teams.
n8n$14.99Automate GitHub Issue Creation and Email Notifications from Notion
This workflow automates the process of tracking feature requests in Notion, creating GitHub issues, and notifying your team via email based on issue status. It's ideal for teams collaborating on project delivery using Notion and GitHub.
n8n$9.99Automate Google Drive File Permission Audits for Enhanced Security
This workflow automates the auditing of Google Drive file permissions, identifying files with overly permissive access settings to enhance security and compliance.
n8n$14.99Automate Daily Workflow Backups to Google Drive with Telegram Alerts
This workflow automates the daily backup of your n8n workflows to Google Drive, ensuring data safety and organization. It creates timestamped folders, converts workflows to JSON files, and manages backups by retaining only the most recent seven days. Notifications are sent via Telegram to keep you updated on the backup status.
n8n$14.99Clone n8n Workflows Between Instances Using n8n API
## **Overview** The **n8n Workflow Cloner** is a powerful automation tool designed to **copy, sync, and migrate workflows** across different n8n instances or projects. Whether you're managing multiple environments (development, staging, production) or organizing workflows within a team, this workflow **automates the transfer process**, ensuring seamless workflow deployment with minimal manual effort. By automatically detecting and copying only the missing workflows, this tool helps **maintain consistency, improve collaboration, and streamline workflow migration** between projects or instances. ## **How to Use** ### 1. **Set Up API Credentials** - Configure API credentials for both **source** and **destination** n8n instances. - Ensure the credentials have **read and write** access to manage workflows. ### 2. **Select Source & Destination** - Update the **GET - Workflows** node to define the **source instance**. - Set the **CREATE - Workflow** node to specify the **destination instance**. ### 3. **Run the Workflow** - Click **Test Workflow** to start the transfer. - The system will fetch all workflows from the source, **compare** them with the destination, and copy any missing workflows. ### 4. **Change the Destination Project** (Optional) - By default, workflows are moved to the **KBB Workflows** project. - Modify the **Filter** node to transfer workflows to a different project. ### 5. **Monitor & Verify** - The **Loop Over Items** node ensures batch processing for multiple workflows. - Log outputs provide details on transferred workflows and statuses. ## **Key Benefits** - **Automate Workflow Transfers** - No more manual exports/imports. - **Sync Workflows Across Environments** - Keep workflows up to date in dev, staging, and production. - **Effortless Team Collaboration** - Share workflows across projects seamlessly. - **Backup & Migration Ready** - Easily move workflows between n8n instances. ## **Use Cases** - **CI/CD for Workflows** - Deploy workflows between development and production environments. - **Team Workflow Sharing** - Share workflows across multiple n8n projects. - **Workflow Backup Solution** - Store copies of workflows in a dedicated backup project. ## **Tags** - Workflow Migration - n8n Automation - Sync Workflows - Backup & Deployment
n8n$14.99Automate PCI DSS Control Evaluation and Compliance Tracking
Streamline your PCI DSS compliance process by automatically evaluating control responses using n8n. This workflow helps reduce audit fatigue and flags non-compliance early by classifying controls as Compliant, Partial, or Non-Compliant.
n8n$14.99Sync Notion Content to Webflow CMS as Draft Items with Status Tracking
## **How it works:** This template takes approved Notion pages and syncs them to a Webflow CMS collection as **draft** items. It reads pages marked **Status = Ready for publish** in a specific Notion database/project, merges JSON content stored across page blocks into a single object, then either **creates** a new CMS item or **updates** the existing one by **name**. On success, it sets the Notion page to **5. Done**; on failure, it switches the page to **On Hold** for review. ## **Step-by-step:** 1. **Manual Trigger** You start the run with **When clicking 'Execute workflow'**. 2. **Get Notion Pages (Notion – Database: Fetch Content Tasks)** Pull all pages with **Status = Ready for publish** scoped to the target **Project**. 3. **Loop Over Items (Split In Batches)** Process one Notion page at a time. 4. **Code (Pass-through)** Expose page fields (e.g., **name**, **id**, **url**, **sector**) for downstream nodes. 5. **Get Notion Block (children)** Fetch all blocks under the page **id**. 6. **Merge Content (Code)** Concatenate code-block fragments, **parse** them into one `mergedContent` JSON, and attach the page metadata. 7. **Get Webflow Items (HTTP GET)** List items in the target Webflow **collection** to see if an item with the same **name** already exists. 8. **Update or Create (Switch)** - **No match:** **Create Webflow Item** (POST) with `isDraft: true`, mapping all `fieldData` (e.g., category titles, meta title, excerpt, hero copy/image, benefits, problem pointers, FAQ, ROI). - **Match:** **Update Webflow Item (Draft)** (PATCH) for that **id**. Keep the **existing slug**, write the latest `fieldData`, leave `isDraft: true`. 9. **Write Back Status (Notion)** - **Success path** set **Status = 5. Done**. - **Error path** set **Status = On Hold**. 10. **Log Submission (Code)** Log a compact object with **status**, **notionPageId**, **webflowItemId**, **timestamp**, and **action**. 11. **Wait – Loop** Short pause, then continue with the next page. ## **Tools integration:** - **Notion** - source database and page blocks for approved content. - **Webflow CMS API** - destination collection; items created/updated as **drafts**. - **n8n Code** - JSON merge and lightweight logging. - **Split In Batches + Wait** - controlled, item-wise processing. Want hands-free publishing? Add a **Cron** trigger before step 2 to run on a schedule.
n8n$9.99Automate Security Questionnaire Responses with AI
Streamline and automate the process of responding to security questionnaires by leveraging AI to match questions with approved answers and evidence, ensuring fast and consistent responses.
n8n$9.99Track Expenses by Parsing Telegram Transaction Messages to Google Sheets
**Overview** This n8n workflow template automatically parses incoming Telegram transaction messages and logs structured data into a Google Sheet. It's designed to help individuals and small businesses track and record transactions shared via Telegram without manual data entry. **Target Audience** This template is ideal for: - Individuals, freelancers, and small businesses who receive transaction or payment notifications through Telegram and want to organize them in Google Sheets. - Anyone using self-hosted n8n (required due to custom community nodes). **Problem Solved** Manually copying transaction details from Telegram to Google Sheets is error-prone and time-consuming. This workflow automates the process by: - Monitoring a Telegram bot/chat for new messages. - Parsing transaction details (amount, sender, date, etc.). - Logging them in real-time into a Google Sheet for easy tracking. **Setup Instructions** 1. **Telegram Bot Setup** - Create a Telegram bot using BotFather. - Add the bot to the desired group/channel and grant admin permissions if needed. - Note down the bot token. 2. **Google Sheets Setup** - Create a Google Sheet with relevant columns (e.g., Date, Amount, Sender, Transaction ID). - Set up Google Sheets credentials in n8n for access. 3. **n8n Workflow Configuration** - Import this template into your self-hosted n8n instance. - Update the Telegram node: Add your bot token and specify the chat/group ID. - Update the Google Sheets node: Link it to your created sheet and ensure column mapping matches your sheet structure. - Adjust parsing logic if your message format varies (see next section for examples). 4. **Community Nodes** - This workflow uses custom community nodes. Ensure these are installed via the n8n settings or CLI: - [List your required community nodes here, e.g., n8n-nodes-telegram, n8n-nodes-gsheet, etc.] 5. **Activate the Workflow** - Save and activate your workflow. Send a test transaction message to your Telegram group/chat and verify data appears in your Google Sheet. 6. **Troubleshooting** - If messages are not being picked up, check bot permissions and the chat ID. - Ensure Google Sheets credentials are correct and the sheet is accessible. - Double-check that custom nodes are properly installed and up-to-date. **Example Telegram Message Formats** - Received: $75 from @john_doe on 2024-05-29. Transaction ID: 12345XYZ. - Paid $120 to @vendor on 2024-05-28. Ref: 67890ABC. - You received ₹5,000 from @amit. ID: 54321PQR. Date: 29/05/2024 The workflow parses messages in the above formats and logs the following columns: - Date - Amount - Sender/Receiver - Transaction/Reference ID If your message format differs, update the regex in the parsing node. **Disclaimer** This n8n workflow template uses custom community nodes and is only compatible with the self-hosted version of n8n. **Workflow Changes (For n8n Canvas)** Rename the Nodes: - If node → "Is Transaction Message?" - Google Sheets node → "Log to Google Sheet" (Rename other generic nodes for clarity, e.g., Telegram → "Listen for Telegram Messages", Function → "Parse Transaction Details") Sticky Note Improvement: (Edit the sticky note or add one if missing) **Workflow Steps:** - Listen for Telegram Messages: This node receives new messages from the Telegram bot. - Is Transaction Message? Checks if the message matches known transaction patterns. - Parse Transaction Details: Extracts amount, sender, date, and transaction ID using regex. - Log to Google Sheet: Records the parsed transaction in the linked Google Sheet for easy tracking.
n8n$4.99Sync Pipedrive Deals to ActiveCampaign Contacts Automatically
Automatically create or update contacts in ActiveCampaign when deals in Pipedrive are moved to a specified stage, ensuring your contact list is always up-to-date.
Make$2.99Automatically Send Daily Sales Summary Reports from Square via Microsoft Outlook
## Automatically Send Square Summary Report for Yesterday's Sales via Microsoft Outlook ## What It Does This workflow automatically connects to the Square API and generates a daily sales summary report for all your Square locations. The report matches the figures displayed in **Square Dashboard > Reports > Sales Summary**. It's designed to run daily and pull the previous day's sales into a CSV file, which is then sent to a manager/finance team for analysis. This workflow builds on my previous template, which allows users to automatically pull data from the Square API into n8n for processing. (See here: https://n8n.io/workflows/6358) ## Prerequisites To use this workflow, you'll need: - A Square API credential (configured as a Header Auth credential) - A Microsoft Outlook credential ## How to Set Up Square Credentials: - Go to **Credentials > Create New** - Choose **Header Auth** - Set the **Name** to `Authorization` - Set the **Value** to your Square Access Token (e.g., `Bearer <your-api-key>`) ## How It Works 1. **Trigger:** The workflow runs every day at 4:00 AM 2. **Fetch Locations:** An HTTP request retrieves all Square locations linked to your account 3. **Fetch Orders:** For each location, an HTTP request pulls completed orders for the specified report_date 4. **Filter Empty Locations:** Locations with no sales are ignored 5. **Aggregate Sales Data:** A Code node processes the order data and produces a summary identical to Square's built-in Sales Summary report 6. **Create CSV File:** A CSV file is created containing the relevant data 7. **Send Email:** An email is sent to the chosen third party ## Example Use Cases - Automatically send Square sales data to management to improve the quality of planning and scheduling decisions - Automatically send data to an external third party, such as a landlord or agent, who is paid via commission - Automatically send data to a bookkeeper for entry into QuickBooks ## How to Use - Configure both HTTP Request nodes to use your Square API credential - Set the workflow to **Active** so it runs automatically - Enter the email address of the person you want to send the report to and update the message body - If you want to remove the n8n attribution, you can do so in the last node ## Customization Options - Add pagination to handle locations with more than 1,000 orders per day - Instead of a daily summary, you can modify this workflow to produce a weekly summary once a week ## Why It's Useful This workflow saves time, reduces manual report pulling from Square, and enables smarter automation around sales data—whether for operations, finance, or performance monitoring.
n8n$9.99Automate AWS IAM User Management via Email Commands
This n8n workflow automates the management of AWS IAM users by processing email commands to create, delete, update users, and manage group assignments, with automatic email confirmations.
n8n$9.99Automatically Send Daily Sales Reports from Square via Gmail
## Automatically Send Square Summary Report for Yesterday's Sales via Gmail ## What It Does This workflow automatically connects to the Square API and generates a daily sales summary report for all your Square locations. The report matches the figures displayed in **Square Dashboard > Reports > Sales Summary**. It's designed to run daily and pull the previous day's sales into a CSV file, which is then sent to a manager/finance team for analysis. This workflow builds on my previous template, which allows users to automatically pull data from the Square API into n8n for processing. (See here: [https://n8n.io/workflows/6358](https://n8n.io/workflows/6358)) ## Prerequisites To use this workflow, you'll need: - A Square API credential (configured as a Header Auth credential) - A Gmail credential ## How to Set Up Square Credentials: - Go to **Credentials > Create New** - Choose **Header Auth** - Set the **Name** to `Authorization` - Set the **Value** to your Square Access Token (e.g., `Bearer <your-api-key>`) ## How It Works 1. **Trigger:** The workflow runs every day at 4:00 AM 2. **Fetch Locations:** An HTTP request retrieves all Square locations linked to your account 3. **Fetch Orders:** For each location, an HTTP request pulls completed orders for the specified report_date 4. **Filter Empty Locations:** Locations with no sales are ignored 5. **Aggregate Sales Data:** A Code node processes the order data and produces a summary identical to Square's built-in Sales Summary report 6. **Create CSV File:** A CSV file is created containing the relevant data 7. **Send Email:** An email is sent to the chosen third party ## Example Use Cases - Automatically send Square sales data to management to improve the quality of planning and scheduling decisions - Automatically send data to an external third party, such as a landlord or agent, who is paid via commission - Automatically send data to a bookkeeper for entry into QuickBooks ## How to Use - Configure both HTTP Request nodes to use your Square API credential - Set the workflow to **Active** so it runs automatically - Enter the email address of the person you want to send the report to and update the message body - If you want to remove the n8n attribution, you can do so in the last node ## Customization Options - Add pagination to handle locations with more than 1,000 orders per day - Instead of a daily summary, you can modify this workflow to produce a weekly summary once a week ## Why It's Useful This workflow saves time, reduces manual report pulling from Square, and enables smarter automation around sales data - whether for operations, finance, or performance monitoring.
n8n$9.99n8n Subworkflow Dependency Graph & Auto-tagging
## How it Works As n8n instances scale, teams often lose track of sub-workflows—who uses them, where they are referenced, and whether they can be safely updated. This leads to inefficiencies like unnecessary copies of workflows or reluctance to modify existing ones. This workflow solves that problem by: 1. Fetching all workflows and identifying which ones execute others. 2. Verifying that referenced sub-workflows exist. 3. Building a caller-subworkflow dependency graph for visibility. 4. Automatically tagging sub-workflows based on their parent workflows. 5. Providing a chart visualization to highlight the most-used sub-workflows.  ## Set Up Steps *Estimated time: ~10-15 minutes* 1. Set up n8n API credentials to allow access to workflows and tags. 2. Replace instance_url with your n8n instance URL. 3. Run the workflow to analyze dependencies and generate the graph. 4. Review and validate assigned tags for sub-workflows. 5. (Optional) Enable pie chart visualization to see the most-used sub-workflows. This workflow is essential for enterprise teams managing large n8n instances, preventing workflow duplication, reducing uncertainty around dependencies, and allowing safe, informed updates to sub-workflows.
n8n$24.99Automate n8n Workflow Documentation and Backup to Notion and GitHub
This workflow automates the documentation and backup of n8n workflows by storing them in a Notion database and GitHub repository. It leverages OpenAI's GPT-4 for summarization and sends notifications to a Slack channel for updates.
n8n$14.99Create Dynamic Workflows Programmatically via Webhooks & N8n API
## Overview This workflow exposes an HTTP endpoint (webhook) that accepts a JSON definition of an n8n workflow, validates it, and—if everything is correct—dynamically creates that workflow in the n8n instance via its internal API. If any validation fails or the API call encounters an error, an explanatory message with details is returned. ## Workflow Diagram ```text Webhook → Validate JSON → fails validation → Validation Error → passes → Validation Successful? → true → Create Workflow → API Successful? → Success Response → false → API Error → false → Validation Error ``` ## Step-by-Step Details ### 1. Webhook * **Type**: Webhook (POST) * **Path**: `/webhook/create-workflow` * **Purpose**: Expose a URL to receive a JSON definition of a workflow. * **Expected Input**: JSON containing the main workflow fields (`name`, `nodes`, `connections`, `settings`). ### 2. Validate JSON * **Type**: Code Node (JavaScript) * **Validations Performed**: * Ensure that `payload` exists and contains both `name` and `nodes`. * Verify that `nodes` is an array with at least one item. * Check that each node includes the required fields: `id`, `name`, `type`, `position`. * If missing, initialize `connections`, `settings`, `parameters`, and `typeVersion`. * **Output if Error**: ```json { "success": false, "message": "<error description>" } ``` * **Output if Valid**: ```json { "success": true, "apiWorkflow": { "name": payload.name, "nodes": payload.nodes, "connections": payload.connections, "settings": payload.settings } } ``` ### 3. Validation Successful? * **Type**: IF Node * **Condition**: `$json.success === true` * **Branches**: * **true**: proceed to **Create Workflow** * **false**: route to **Validation Error** ### 4. Create Workflow * **Type**: HTTP Request (POST) * **URL**: `http://127.0.0.1:5678/api/v1/workflows` * **Authentication**: Header Auth with internal credentials * **Body**: The `apiWorkflow` object generated earlier * **Options**: `continueOnFail: true` (to handle failures in the next IF) ### 5. API Successful? * **Type**: IF Node * **Condition**: `$response.statusCode <= 299` * **Branches**: * **true**: proceed to **Success Response** * **false**: route to **API Error** ### 6. Success Response * **Type**: HTTP Response Node * **Output**: ```json { "success": true, "message": "Workflow created successfully", "workflowId": "{{ $json.data[0].id }}", "workflowName": "{{ $json.data[0].name }}", "createdAt": "{{ $json.data[0].createdAt }}", "url": "http://localhost:5678/workflow/{{ $json.data[0].id }}" } ``` ### 7. API Error * **Type**: HTTP Response Node * **Output**: ```json { "success": false, "message": "Error creating workflow", "error": "{{ JSON.stringify($json) }}", "statusCode": "{{ $response.statusCode }}" } ``` ### 8. Validation Error * **Type**: HTTP Response Node * **Output**: ```json { "success": false, "message": "{{ $json.message }}" } ``` ## Example Webhook Request ```bash curl --location --request POST http://localhost:5678/webhook/create-workflow \ --header "Content-Type: application/json" \ --data-raw "{ \"name\": \"My Dynamic Workflow\", \"nodes\": [ { \"id\": \"start-node\", \"name\": \"Start\", \"type\": \"n8n-nodes-base.manualTrigger\", \"typeVersion\": 1, \"position\": [100, 100], \"parameters\": {} }, { \"id\": \"set-node\", \"name\": \"Set\", \"type\": \"n8n-nodes-base.set\", \"typeVersion\": 1, \"position\": [300, 100], \"parameters\": { \"values\": { \"string\": [ { \"name\": \"message\", \"value\": \"Hello from a webhook-created workflow!\" } ] } } } ], \"connections\": { \"Start\": { \"main\": [ [ { \"node\": \"Set\", \"type\": \"main\", \"index\": 0 } ] ] } }, \"settings\": {} }" ``` ### Expected Success Response ```json { "success": true, "message": "Workflow created successfully", "workflowId": "abcdef1234567890", "workflowName": "My Dynamic Workflow", "createdAt": "2025-05-31T12:34:56.789Z", "url": "http://localhost:5678/workflow/abcdef1234567890" } ``` ### Validation Error Response ```json { "success": false, "message": "The name field is required in the workflow" } ``` ### API Error Response ```json { "success": false, "message": "Error creating workflow", "error": { "...full API response details..." }, "statusCode": 401 } ```
n8n$9.99
Related categories
Custom AI Systems & Services
Our team of experienced AI builders will help build custom AI systems, workflows, and solutions.
Request Custom Work