Business Operations & ERPs Workflows
Enterprise resource planning and operations
Streamline Client Onboarding with Automated Google Drive and Email Notifications
Automate the creation of Google Drive folders and send personalized email notifications to clients, enhancing onboarding efficiency and clarity.
n8n$4.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.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.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.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.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 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 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.99Automate Project Kickoff with Dropbox, OpenAI, Slack & Gmail
Streamline project initiation by automatically creating structured folders in Dropbox and sending notifications via Slack and Gmail. This workflow enhances efficiency and collaboration by leveraging n8n's automation capabilities.
n8n$14.99Automate Clio Manage Matter Creation from Google Forms Responses
This workflow automatically creates a contact and a matter in Clio Manage whenever a new response is submitted in Google Forms, streamlining your legal case management process.
Make$3.99Pattern for Parallel Sub-Workflow Execution Followed by Wait-for-All Loop
## What this workflow does This set of workflows shows how to start multiple sub-workflows, asynchronously, in parallel, and then wait for all of them to complete. Normally, sub-workflows would need to be run synchronously, in series, or, if they are executed asynchronously (to run concurrently, in parallel), there is no easy way to merge/wait for an arbitrary number of them to complete. This is a design pattern template to show one approach for running multiple, data-driven instances of a sub-workflow asynchronously, in parallel (instead of running them one at a time in series), but still prevent the later steps in the workflow from continuing until all of the sub-workflows have reported back that they are finished, via callback URL. There are other techniques involving messaging services, database tables, or other external flow manager helpers, but this technique accomplishes the goal fully within n8n. ## Setup To implement this pattern, examine the nodes in the template and modify the incoming data leading to: 1. A split-out loop to asynchronously execute a sub-workflow multiple times, in parallel. For instance, each sub-workflow might process one of a list of incoming documents. The resumeUrl for the main/parent workflow is provided to all of the sub-workflow executions, along with a unique identifier that can be counted later (e.g., a document file name). 2. A wait-for-all loop that checks whether all sub-workflows have reported back (`if` node) and builds a unique list of identifiers from the callbacks received from each execution of the sub-workflow. The sub-workflow should be designed to respond immediately (async) and later send a callback request when it has finished processing. The callback request should include the unique identifier value received when the sub-workflow was started. This is meant to be a possible answer to questions like [this one about running things in parallel](https://community.n8n.io/t/is-it-possible-to-run-a-part-of-the-workflow-in-parallel/60221), maybe [this one about waiting for things to finish](https://community.n8n.io/t/node-does-not-wait-for-predecessor-node-always-need-a-merge-node/60773), [this one about managing sub-batches of things by waiting for each batch](https://community.n8n.io/t/maximum-parallel-subworkflows/60052), or [this one about running things in parallel](https://community.n8n.io/t/parallel-execution-of-bat-files/49493). The topic of how to do this comes up a lot, and this is one of the only techniques that (so far) seems to work.
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.99SAP Service Layer Login
This minimal utility workflow connects to the SAP Business One Service Layer API to verify login credentials and return the session ID. It's ideal for testing access or using as a sub-workflow to retrieve the B1SESSION token for other operations. **HOW IT WORKS:** **1. Trigger Manually** The workflow is initiated using a Manual Trigger. Ideal for testing or debugging credentials before automation. **2. Set SAP Login Data** The Set Login Data node defines four key input variables: - sap_url: Base URL of the SAP B1 Service Layer (e.g., https://sap-server:50000/b1s/v1/) - sap_username: SAP B1 username - sap_password: SAP B1 password - sap_companydb: SAP B1 Company DB name **3. Connect to SAP** An HTTP Request node performs a POST to the Login endpoint. The body is structured as: ```json { "UserName": "your_sap_username", "Password": "your_sap_password", "CompanyDB": "your_sap_companydb" } ``` If successful, the response contains a SessionId which is essential for authenticated requests. **4. Return Session or Error** The response is branched: On success – the sessionID is extracted and returned. On failure – the error message and status code are stored separately. **SETUP STEPS:** **1. Create SAP Service Layer Credentials** Although this workflow uses manual inputs (via Set), it's best to define your connection details as environment variables for reuse: - SAP_URL=https://your-sap-host:50000/b1s/v1/ - SAP_USER=your_sapuser - SAP_PASSWORD=your_password - SAP_COMPANY_DB=your_companyDB Alternatively, update the Set Login Data node directly with your values. **2. Run the Workflow** Click Execute Workflow in n8n. Watch the response from SAP: - If successful: sessionID will be available in the Success node. - If failed: statusCode and errorMessage will be available in the Failed node. **USE CASES:** - Reusable Login Module Export this as a reusable sub-workflow for other SAP-integrated flows. - Credential Testing Tool Validate new environments, test credentials before deployment.
n8n$4.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 SSL Certificate Monitoring with Google Sheets and Email Alerts
This n8n workflow automatically checks SSL certificates for websites listed in a Google Sheet and sends email alerts if any are expiring within 14 days. This helps prevent downtime and security issues caused by expired certificates.
n8n$14.99Automate Cal.com Meeting Attendee Management with Google Sheets, Beehiiv, and Telegram Notifications
Streamline your meeting attendee management by automatically logging details in Google Sheets, subscribing attendees to Beehiiv, and receiving Telegram notifications.
n8n$9.99Automatically Create ClickUp Tasks from New Trello Cards
Streamline your workflow by automatically generating ClickUp tasks whenever a new card is added in Trello. This integration ensures that your task management stays synchronized across platforms.
Make$3.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.99Automated Error Alerts with Google Sheets, Telegram, and Gmail in n8n
This workflow automates error handling in n8n by logging errors to Google Sheets, notifying a Telegram channel, and sending email alerts via Gmail, ensuring prompt awareness of issues.
n8n$4.99Automate Stripe Payment Recovery and Follow-Up Emails
Automatically detect failed Stripe payments, log them in Google Sheets, and send follow-up emails to recover revenue using n8n.
n8n$9.99Create a new Airtable record for every new email in Gmail
Automatically create a new Airtable record for every new email received in Gmail, streamlining your data organization and management process.
MakeFreeAutomate 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 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.99Automate Webpage Change Detection and Notifications with Google Suite
Monitor webpage content changes and receive notifications via Google Suite when updates occur. Ideal for tracking important documents like company policies or competitor pages.
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