Workflow Templates

WORKFLOW INTRODUCTION This automation organizes and consolidates your n8n workflows into categorized JSON files (Active, Template, Done, Archived) and uploads them directly to a Google Drive folder. It is designed to help users manage large instances by creating organized, human-readable backups. HOW IT WORKS API Connection:** Connects to your n8n instance using the internal API. Categorization:** Groups workflows by status and tags. WIP Logic:** Any workflow without a specific status or tag is automatically routed to a work-in-progress consolidation file. Cloud & Self-Hosted Ready:** Works for both n8n Cloud and self-hosted instances. WORKFLOW PROCESS OVERVIEW Fetch -> Filter -> Convert -> Upload -> Wait 5 seconds See below for a full breakdown. USAGE GUIDE & SETUP This workflow is dependent on the n8n internal statuses of Active and Archived, and the tags "Template" and "Done". Anything that is not Active, Archived, or labeled Template or Done, is considered a work-in-progress by default. To make this workflow work for you please tag your templates as Template, and your completed projects as Done. PRE-REQS A pre-designated Google Drive folder (and its ID) for housing the folders and files created by this workflow REQUIRED CREDENTIALS Google Drive account N8N account > N8N API Key THE CONFIGURATION NODE Input the ID of your pre-designated Google Drive folder Input the base URL of your N8N instance (e.g. https://subdomain.app.n8n.cloud, https://n8n.domain.com, http://localhost:5678) 2a. Do NOT include anything after the ".cloud", ".com", or the ":5678" API KEY INSTRUCTIONS How to get: Settings -> API -> Create API Key -> Name it -> Copy it Note: Copy the API key and save it somewhere secure. You won't be able to see it again!!**_ How to use (Two Methods): Note: The node is set up for Method 2 by default Method 1 (Quick Start-Direct Insertion). In the Workflows node: Authentication: None Send Headers: on Name: X-N8N-API-KEY Value: [YOUR N8N API KEY] Note:** Queries and Body are not needed for this method._ Method 2 (Best Practice-N8N Credential). In the Workflows node: Authentication: Generic Credential Type Generic Auth Type: Header Auth Header Auth: Select "Create new credential" (NOTE: If you already have a Header Auth for your N8N API key select it here) 2a. In the credential creation area: Name: X-N8N-API-KEY Value: [YOUR N8N API KEY] Note:** Queries, Header, and Body are not needed for this method._ WORKFLOW PROCESS BREAKDOWN (after configuration) Creates a Google Drive folder to house the resulting files Grabs your workflows from the public API Splits out the workflows into individual items for easier processing Filters out the Active workflows (True: a-d; False: Go to 5) 4a. Sorts the active workflows by name 4b. Converts the active workflows into a single JSON file 4c. Uploads the active JSON file to the folder created in Step 1. 4d. Wait 5 seconds to avoid errors caused by the Google spam upload detector Filters out the Not Archived workflows (True: Go to 6; False: a-d) 5a. Sorts the archived workflows by name 5b. Converts the archived workflows into a single JSON file 5c. Uploads the archived JSON file to the folder created in Step 1. 5d. Wait 5 seconds to avoid errors caused by the Google spam upload detector Filters out the workflows tagged "Template" (True: a-d; False: Go to 7) 6a. Sorts the template workflows by name 6b. Converts the template workflows into a single JSON file 6c. Uploads the template JSON file to the folder created in Step 1. 6d. Wait 5 seconds to avoid errors caused by the Google spam upload detector Filters out the workflows tagged "Done" (True: a-d; False: e-g) 7a. Sorts the done workflows by name 7b. Converts the done workflows into a single JSON file 7c. Uploads the done JSON file to the folder created in Step 1. 7d. Wait 5 seconds to avoid errors caused by the Google spam upload detector 7e. Sorts the work-in-progress workflows by name 7f. Converts the work-in-progress workflows into a single JSON file 7g. Uploads the work0in-progress JSON file to the folder created in Step 1. 7h. Wait 5 seconds to avoid errors caused by the Google spam upload detector LIMITATIONS N8N Cloud users on a trial account cannot generate or use the N8N API key. If you use Method 1 (Direct Insertion) in the API Key Instructions your API Key will not be listed as connected to this workflow if you use my Workflow Credentials Auditor. Same goes for all other credentials directly inserted into a HTTP Request node. ALTERNATIVE VERSIONS AND CUSTOM BUILDS While this version focuses on global status tagging using Google Drive, I have developed a parallel version for Github Repository storage. Need the Github Version?** I provide the standard Workflow Organizer Consolidated Github version free upon request. Want to backup workflows without consolidating them?* I offer the standard *Workflow Organizer** free upon request for both Google Drive and GitHub. Note: The Google Drive version is meant to work in tandem with this Workflow Organizer Consolidated Google Drive. They should be linked to the same parent folder. Need a Custom build?** If you require advanced logic (e.g. client-specific routing, multi-tier tagging, unique project tagging, integration with other platforms), I offer custom automation services tailored to your business needs. A custom version of this workflow or the Github version is $15. Contact me here: workflows@zmglobalit.com

Overview This n8n workflow provides an automated notification system that monitors tickets in GLPI (Gestionnaire Libre de Parc Informatique) and sends proactive alerts through Microsoft Teams when tickets are approaching their expiration dates. Key Features 🕘 Automated Scheduling Daily execution scheduled at 9:00 AM Continuous monitoring without manual intervention Customizable scheduling configuration 🎯 Intelligent Deadline Detection Automatic identification of tickets expiring within the next 2 days Configurable date-based filtering criteria Efficient processing of multiple simultaneous tickets 👥 Targeted Notifications Personalized alerts sent to specific technicians via Microsoft Teams Automatic assignment based on ticket assignee Structured messages with key ticket information 🔧 Complete GLPI Integration Secure connection through GLPI REST API Authentication with application tokens Automatic session management (initiation and closure) Technical Functionalities Data Processing Extraction: Automatic queries to GLPI database Filtering: Ticket separation by assigned technician Transformation: Data formatting for readable notifications Conditional Flow Automatic evaluation of responsible technician Intelligent notification routing Handling of cases without specific assignment Session Management Automatic session initiation with GLPI Secure session token maintenance Controlled session closure upon completion Ticket Information Included Each alert contains: Ticket Title: Clear problem description Ticket ID: Unique identifier for tracking Time Remaining: Days/hours until expiration System Requirements Infrastructure GLPI server with REST API enabled Running n8n instance Microsoft Teams account with API permissions Required Credentials GLPI user with application administrator privileges Valid GLPI application token OAuth2 credentials for Microsoft Teams GLPI User ID Identification For complete workflow configuration, it's necessary to identify the correct IDs of technical users for proper notification assignment. User IDs can be obtained by accessing user management in GLPI and observing the ID directly in the browser URL when selecting a specific user. Path: Administration > Users > [Select User] When clicking on the desired user, you can see the user ID directly in the browser URL (e.g., id=7 for Support Technician 1, id=8 for Support Technician 2). Configuration Environment Variables json{ "glpi_url": "https://your-glpi-server.com", "app_token": "your-application-token-here" } Available Customization Alert Period**: Modifiable from 2 days to any desired range Execution Schedule**: Configurable according to operational needs Recipients**: Adaptable to specific team structure Operational Benefits For Support Teams Reduction of expired tickets Improved response times Proactive workload management For Organizations Higher SLA compliance Increased customer satisfaction Optimized technical support resources Ideal Use Cases IT Service Centers**: Incident and request management Technical Support Teams**: Critical case tracking Organizations with Strict SLAs**: Service agreement compliance IT Departments**: Internal ticket monitoring Scalability This workflow is designed to: Handle high ticket volumes Adapt to teams of different sizes Integrate with multiple communication channels Expand with additional functionalities Installation and Deployment Import the JSON workflow into n8n Configure GLPI and Microsoft Teams credentials Update configuration variables Activate the scheduled trigger Perform functionality tests This workflow represents a robust and scalable solution for proactive ticket management in enterprise environments, significantly improving operational efficiency and service commitment compliance.

Back up n8n workflows to Google Drive automatically This workflow provides a robust solution for backing up your n8n workflows to Google Drive. It is designed to handle backups for multiple n8n instances centrally and leverages Google Drive's native file versioning to keep your history clean. 🚀 ✨ Key Features 🔄 Smart Version Control: Instead of creating a new file for every backup, this workflow checks if the file exists and updates it. This utilizes Google Drive's built-in "Manage Versions" feature, allowing you to rollback changes without cluttering your folder. 🌍 Multi-Instance Support: Easily backup workflows from multiple n8n servers (e.g., Development, Production) in one go. ⚡ Efficiency: Filters out inactive or archived workflows to save resources. 🧩 Self-Contained Logic: Uses a recursive design to process workflows efficiently. ⚙️ How It Works The workflow operates in two main stages: Fetch & Dispatch: Run daily: The workflow triggers on a schedule. Fetch workflows: It connects to your configured n8n instances via the n8n Public API to retrieve all active workflows. It then batches the data and configures the target folders for each host. Core Backup Logic: Process backup recursively: The workflow calls itself to process the list. Drive Comparison: It lists files in the target Google Drive folder and compares them with the n8n workflows. Smart Sync: 🆕 New: If the workflow doesn't exist on Drive, it uploads a new file. ♻️ Update: If the workflow exists but has been modified, it updates the existing file (preserving the file ID and history). 📝 Setup Instructions 🔑 Credentials Set up Google Drive OAuth2 API credentials. Set up n8n API credentials for each instance you want to backup. 📂 Configure Folder IDs Create a folder in Google Drive for your backups and copy the Folder ID from the URL. Open the nodes named Config Host 1 (and Config Host 2, etc.). Replace the value for targetFloderId with your actual Google Drive Folder ID. 🔗 Link the Sub-Workflow ⚠️ Important: This workflow calls itself to process the data recursively. Open the node named Process backup recursively. Ensure the Workflow ID field is pointing to this workflow's ID (you can select it from the list after saving the workflow for the first time). 🛠️ Requirements n8n Service Account or API Key. Google Cloud Console Project with Google Drive API enabled.

Transform markdown text into beautifully formatted Notion pages using the Mark2Notion API. This workflow handles all the complexity of Notion's block structure, including tables, nested lists, code blocks, and special formatting. What this template does This workflow takes any markdown-formatted text and automatically converts it into properly structured Notion blocks, then appends it to your specified Notion page. It handles all of Notion's API limitations automatically, including: Chunking content over 100 blocks Splitting text over 2000 characters Rate limiting and retry logic Complex table structures Nested lists, including 3+ level of nesting Use Cases AI Content Publishing**: Send ChatGPT, Claude, or other LLM outputs directly to your Notion documentation Form to Documentation**: Convert form submissions into formatted project pages GitHub to Notion**: Sync issues, PRs, or README files to your team wiki Meeting Notes Automation**: Transform transcripts into structured meeting notes Report Generation**: Create beautiful reports from data sources How to use this template Get your Mark2Notion API key at https://mark2notion.com (free tier includes 100 requests/month) Create a Notion integration at https://notion.so/my-integrations and copy the token Add connection to the integration on your Notion page Copy your page ID from the Notion page URL Configure the HTTP Request node with your credentials. Use "x-api-key" header name for Mark2Notion Header Auth. Test with sample markdown to see the result More Information Full API documentation: https://docs.mark2notion.com Quickstart guide: https://mark2notion.com/guides/quickstart Feedback and support: https://github.com/elitemaks/mark2notion-api

This n8n template from Intuz provides a complete and automated solution to streamline your sales and accounting process. Simply add new transaction details to a designated Google Sheet, and this workflow takes over. Using specific status keywords in a column to trigger the process, it automatically creates new customer profiles and generates sales receipts in QuickBooks. This creates a complete, end-to-end system from a simple spreadsheet entry to a formal accounting record, eliminating manual data entry. How it works This workflow streamlines the process of recording sales from a Google Sheet into QuickBooks Online, intelligently handling both new and existing customers. 1. Trigger on New Row: The workflow starts automatically whenever a new row is added to your specified Google Sheet. 2. Check for Existing Customer: It takes the customer's name from the new row and searches your QuickBooks account to see if a customer with that DisplayName already exists. 3. Conditional Logic (IF Node): Based on the search result, the workflow splits into two paths: If Customer Exists (True Path): The workflow proceeds directly to create a Sales Receipt, linking it to the existing customer's ID found in the search. If Customer Does Not Exist (False Path): The workflow first creates a new customer in QuickBooks using the name and email from the sheet. It then uses the ID of this newly created customer to generate the corresponding Sales Receipt. How to Use: Quick Start Guide Prepare your Google Sheet: Make sure you have a Google Sheet with clear headers for your sales data. The template is configured for the following columns: CustomerName, Email, Amount, and Quantity. Import the Template: Click the "Use Template" button to import the workflow into your n8n instance. Configure Google Sheet Node: Enter the Spreadsheet ID from your Google Sheet's URL. Enter the Sheet Name where your sales data is located (e.g., Sheet1). Configure the QuickBooks Nodes: Select your QuickBooks Online credential or create a new one for the "Search for Customer", "Create Receipt for EXISTING Customer", "Create New Customer", and "Create Receipt for NEW Customer" nodes. Important: In both "Create Receipt" nodes, you must provide a valid Product/Service ID from your QuickBooks account. Find this in the node parameters under Line > Sales Item Line Detail > Item Ref > Value. Activate the Workflow: Save your changes and activate the workflow. Now, every new row you add to the Google Sheet will automatically create the necessary records in QuickBooks. Key Requirements to Use Template An active n8n instance. A Google account with a prepared Google Sheet. A QuickBooks Online account. A QuickBooks Developer account to obtain the API credentials needed to connect to n8n. At least one Product or Service item set up in your QuickBooks account to be referenced in the sales receipts. 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 Worflow Automation Click here- Get Started

How is works This template makes it possible to extract Search Results from LinkedIn and import them into a Google Sheet. It determines from where the url is coming from (LinkedIn Basic, Sales Navigator or Recruiter) and selects which node needs to be used. The node returns a Run ID while in the background the list is being exported. Run going through a loop the workflow waits untill the job is done. When the export is ready, the response is being transformed into a workable object which then can be used to append the data into a Google Sheet. How to use Connect with a Google Sheet and have the correct columns in place Go to your LinkedIn platform and do a People search. That can be done either in the LinkedIn Basic, Sales Navigator or Recruiter environment. Copy the url of the results page and within the workflow, click on Form Submission Paste in the url and click on Sumbit to start the workflow Requirements A LinkedIn Search Results page url A Google Sheet The https://support.sourcegeek.com/en/articles/12441230-n8n-integration

Tagged with: , , , ,

Tagged with: , , , ,

Tagged with: , , , ,

Tagged with: , , , ,

No description available

Tagged with: , , , ,