Workflow Templates

Tagged with: , , , ,

This workflow contains community nodes that are only compatible with the self-hosted version of n8n. How it works This workflow automates the registration of event participants in SinergiaCRM from a Google Sheets spreadsheet. A Google Sheets Trigger watches for new rows with pending registrations. The flow checks if the participant already exists in SinergiaCRM by NIF (national ID). If the contact exists, it creates a relationship and registers them for an event. If the contact doesn’t exist, it first creates the contact, then adds the relationship and event registration. Finally, it marks the row as "Processed" in the original spreadsheet to avoid duplicate entries. Set up steps Connect your Google Sheets and SinergiaCRM accounts using OAuth credentials. Replace the sample Google Sheet ID and worksheet name with your own. Ensure the spreadsheet contains the following columns: First name, Last name, NIF, Email, Event ID, Relation type, Registration date, and Relation date. Add the appropriate values in the "To CRM" and "Processed" columns to control processing logic. Review sticky notes inside the workflow for additional guidance and customization tips.

Augment AI chatbot prompts with a knowledge graph reasoning ontology and improve the quality of responses with Graph RAG. In this workflow, we augment the original prompt using the InfraNodus GraphRAG system that will extract a reasoning ontology from a graph that you create (or that you can copy from our repository of public graphs). This additional reasoning logic will improve the user's prompt and make it more descriptive and closely related to the logic you want to use. As the next step, you can send it back to the same graph to generate a high-quality response using Graph RAG or to another graph (or AI model) to apply one type of knowledge in a completely different field. How it works Receives a request from a user (via n8n or a publicly available URL chat bot, you can also connect it to Telegram Sends the request to the knowledge graph in your InfraNodus account that contains a reasoning ontology represented as a knowledge graph. Reformulates the original prompt to include the reasoning logic provided. Sends the request to the knowledge graph in your InfraNodus account (same as the previous one or a new one for cross-disciplinary research) to retrieve a high-quality response using GraphRAG Special sauce: InfraNodus will build a graph from your augmented prompt, then overlap it on the knowledge graph you want to inquire, traverse this graph based on the overlapped parts and extended relations, then retrieve the necessary part of the graph and include it in the context to improve the quality of your response. This helps InfraNodus grasp the relations and nuances that are not usually available through standard RAG. How to use • Just get an InfraNodus API key and add it into your Prompt Augmentation and Knowledge Base InfraNodus HTTP nodes for authentication • Then provide the name of the graphs you want to be using for prompt augmentation and retrieval. Note, these can be two different graphs if you want to apply a reasoning logic from one domain in another (e.g. machine learning in biology or philosophy in electrical engineering). Support If you wan to create your own reasoning ontology graphs, please, refer to this article on generating your own knowledge graph ontologies. You may also be interested to watch this video that explains the logic of this approach in detail: Help article on the same topic: Using knowledge graphs as reasoning experts.

📞 Phone Number Validator with Google Sheets Validate and enrich phone numbers from Google Sheets using the phone number validator API. 📌 Use Case: Contact Validation & Enrichment Automatically check if phone numbers are valid and enrich them with metadata (country, location, timezone). Ideal for CRMs, lead management, and contact cleanup workflows. 🗂️ Google Sheets Columns | Column Name | Description | |-------------|-------------| | phone | The original phone number to validate (input column). | | is_valid | Result from API indicating if the phone number is valid (true / false). | | country | Country where the phone number is registered (e.g. "US"). | | location | More specific location info, such as city or region. | | timezone | The primary timezone associated with the phone number. | 🎯 Benefits ✅ Accurate Contact Data – Identify invalid or fake phone numbers automatically. 🌐 Geolocation Enrichment – Add country, location, and timezone for better segmentation. 🔁 Full Automation – No manual lookups or copying data between tools. 📊 Live Google Sheets Sync – Enriched data is updated directly into your spreadsheet. 🧠 Workflow Nodes Explained | Node | Purpose | |------|---------| | 🟢 Manual Trigger | Starts the workflow manually from n8n. | | 📄 Google Sheets (Read) | Fetches phone numbers from your spreadsheet using a Service Account. | | 🔁 Split In Batches | Loops over each row one at a time to handle individual API requests. | | 🌐 HTTP Request | Sends phone number to phone number validator via RapidAPI and receives validation + metadata. | | 📥 Google Sheets (Update) | Writes the response back into the matching row using the phone field. | 🛰️ API Used: phone number validator We use the phone number validator API from RapidAPI to: Validate phone numbers (real or fake?) Identify the country, location, and timezone > It’s fast, reliable, and great for cleaning large datasets or qualifying leads before outreach. 🧰 Prerequisites 📄 A Google Sheet with a column named phone 🔐 RapidAPI key with access to phone number validator 🔧 Google Service Account credentials set up in n8n 🚀 How to Use 🔗 Link your Google Sheet and configure authentication 🔑 Add your RapidAPI key in the HTTP node headers ▶️ Click "Execute Workflow" 🧠 Each phone number is validated and enriched 📊 Results are written back to your Google Sheet 📎 Tags phone validation, rapidapi, google sheets, data enrichment, phone number validator, crm automation, lead cleaning, timezone lookup

How it works This workflow automates the entire process of drafting and publishing blog posts to your WordPress site using advanced AI. It streamlines your content creation by: Generating engaging blog post titles based on your chosen topic. Crafting comprehensive blog post bodies (introduction, main points, conclusion) with professional formatting. Automatically publishing the generated content as a new post on your WordPress website. Save hours of manual writing and accelerate your content strategy with this intelligent automation. Set up steps Getting this workflow ready is straightforward and typically takes around 15-20 minutes. You'll need to: Obtain API keys for your preferred AI service (e.g., OpenAI, Google AI). Provide your WordPress website's URL and login credentials. Optionally, customize the AI prompts to match your specific content style or requirements. All detailed setup instructions and specific configuration guidance are provided within the workflow itself using sticky notes.

Description The Instagram Downloader workflow allows users to download Instagram videos or Reels directly through a Telegram Bot. Simply send an Instagram link to the bot, and it will process the link via a third-party API to fetch the highest quality video, then send it back to your Telegram chat. How It Works Telegram Trigger The workflow starts when the bot receives an Instagram link from a user. HTTP Request – URL Download The link is sent to the API https://www.mediadl.app/api/download to retrieve video metadata. Delay Waits a few seconds to ensure the API response is ready. Filtering URL Only Extracts the direct video file URL from the API result. Delay Adds a short pause to prevent connection errors during download. HTTP Request – Proxy Download Downloads the MP4 video file directly from the filtered URL. Send Video to Telegram Sends the downloaded video back to the user in Telegram. How to Set Up Create & Configure a Telegram Bot Open Telegram, search for BotFather. Send /newbot → choose a bot name & username. Copy the provided Bot Token. Prepare Your n8n Environment Log in to n8n (self-hosted or n8n Cloud). Create Telegram API Credentials using your Bot Token. Import the Workflow In n8n, click Import and select Instagram_Downloader.json. Configure Telegram Nodes Connect your Telegram API credentials in the Telegram Trigger and Send Video nodes. Configure HTTP Request Nodes Ensure the URL and headers in URL Download and Download nodes are correct (already pre-configured). Set responseFormat to file in the final download node. Activate & Test Toggle Activate. Send an Instagram link to your bot to test.

n8n Asynchronous Workflow with Wait Node POC This template contains a two-part workflow designed to demonstrate a proof-of-concept for asynchronous and parallel execution of tasks in n8n. Purpose The purpose of this template is to showcase how you can run multiple long-running tasks simultaneously without blocking your main workflow. It utilizes the "Wait For Sub-workflow Completion" option and the "Wait" node to effectively manage concurrent execution and collect results from sub-workflows via webhooks. This pattern is ideal for use cases involving batch processing or any scenario where a workflow needs to trigger multiple independent tasks and wait for all of them to report back. Setup Instructions Import: Import both the "Main Orchestrator" and "Asynchronous Worker" workflows into your n8n instance. Link Workflows: In the "Main Orchestrator" workflow, ensure the "Execute Workflow" node is correctly configured to call the "Asynchronous Worker" workflow. You can select it by its name from the dropdown menu. Configure: The template is pre-configured to run two parallel tasks with different wait durations to simulate a real-world scenario. You can adjust the parameters on the "Execute Workflow" node to test different wait times. Execution: Execute the "Main Orchestrator" workflow. You will see the workflow pause at the "Wait" nodes while the "Asynchronous Worker" workflows run in the background. Once they complete, they will call back via the webhook, allowing the main workflow to resume and summarize the results. For a detailed walkthrough of how this template works and an explanation of the underlying concepts, please read the full blog post here

Get the latest news, from Kagi, with a workflow that lets you filter by news category. Feed the results in your voice assistant automations to get on-demand news. Or leverage LLM models to create daily summaries from the headlines you retrieved. How it works This workflow takes a category name, from the ones available on Kagi News, then uses the Kagi News API to get all of the day's stories in that category. It then does a bit of filtering, to make it easier to manipulate. But you can skip or change that to your liking. How to use To test it, simply change the pinned data in the Start node, particularly the category field. You can use such examples as World, UK or Technology. Unsure as to what options for category there are? Just run the workflow and check the output of the Split Categories node! It will list all categories available. Take the value from categoryName. Things to consider I used categoryName as the input instead of categoryId for one reason: to make it easier for LLMs to populate that field. If this doesn't work for you, it should be quite easy to change. It is also a single category at a time. If you want to get stories from more categories at once, you can take an array as input in Start, then filter on the categories list containing your entries, rather than an exact match. Finally, you will have to merge all calls to Split out stories after each call to the API. Requirements None beyond an internet connection for your n8n instance. There is no API access token needed or any authorisation of any kind.

Description: Stay on top of product issues with this n8n automation template that centralizes bug reports from Zendesk into a Google Sheets dashboard. The workflow filters only tickets tagged as “bug,” enriches them with reporter details, and updates a single source of truth for developers, QA teams, and support staff. Perfect for product managers, SaaS companies, and agile teams that need full visibility into bug trends and customer impact without wasting time on manual data entry. What This Template Does (Step-by-Step) ⚡ Manual Trigger or Scheduling Run on-demand after releases or bug triage meetings, or set up a schedule to auto-run daily/weekly. 📥 Fetch All Zendesk Tickets Retrieves tickets from your Zendesk account with full metadata. 🔍 Filter Bug Reports Only Processes only tickets tagged as “bug” to ensure relevance. 👤 Add Reporter Details Enriches bug reports with requester’s name, email, and profile data for impact tracking. 📊 Update Google Sheets Bug Tracker Stores bug details including Ticket No., Description, Status, Reporter Info, and Tags. ✔️ Smart update avoids duplicates by using description as a unique key. 🔁 Continuous Bug Aggregation Ensures all relevant bug reports are tracked and kept up-to-date in one central place. Key Features 🔍 Tag-based bug filtering 📊 Centralized bug dashboard in Google Sheets ⚡ Zendesk + Google Sheets integration with OAuth2 ♻️ Real-time sync with deduplication logic 🔐 Secure API credential handling Use Cases 🐞 Track and prioritize product bugs from customer reports 📊 Give QA and dev teams a shared bug dashboard 📩 Identify high-impact bugs based on affected customers 📈 Monitor bug frequency and trends for release planning Required Integrations Zendesk API (for ticket fetch + user info) Google Sheets (for storing/updating bug tracker) Why Use This Template? ✅ Centralizes bug visibility for all teams ✅ Saves hours of manual spreadsheet updates ✅ Improves prioritization with customer context ✅ Scales easily with more tags or categories ✅ Keeps bug tracking transparent across stakeholders

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.

This workflow takes an image URL and a description of the desired background, then uses the APImage AI API to produce a high-quality image, preserving the subject and applying a natural-looking new background. Example Result Here you can see a before-and-after image, generated by APImage, using this workflow. Who This Workflow is For This workflow is perfect for anyone looking to generate polished, professional images quickly: E-commerce Teams**: Ensure consistent product images with uniform, professional backdrops to reinforce brand identity and trust. Content Creators**: Generate eye-catching visuals for social media, blogs, or marketing campaigns quickly. Designers**: Produce realistic mockups and conceptual designs without hours of manual editing. Businesses of All Sizes**: Automate large-scale image pipelines efficiently without expanding staff or budget. Anyone Needing AI Imaging**: Personal or professional projects can benefit from this automated, high-quality workflow. How the Workflow Works This n8n workflow leverages a Form Trigger and APImage’s AI endpoint to automate background replacement: ┌───────────────┐ │ Input Image │ │ (URL / source)│ └───────┬───────┘ │ ▼ ┌──────────────────────────┐ │ Background Replacement │ │ + Lighting Optimization│ │ (APImage AI) │ └───────┬──────────────────┘ │ ▼ ┌──────────────────────┐ │ Download Image │ │ (default name: data) │ └───────┬──────────────┘ │ ▼ ┌───────────────────────────┐ │ Output Nodes │ │ (DBs, Cloud, CMS, APIs) │ └───────────────────────────┘ Form Trigger:** Collects the image URL and descriptive prompt. Can be swapped with any data source node (databases, cloud storage, APIs). APImage Integration:** Processes the image, separates the subject, generates the new background, and preserves realistic lighting and shadows. Download Node:** Retrieves the processed image for storage or further use. Output Options:** Automatically upload images to Google Drive, Dropbox, Airtable, Notion, Amazon S3, or any other database, creating a fully automated pipeline. How to Set Up the Workflow Add Your APImage API Key Open the APImage API node. Replace Bearer YOUR_API_KEY with your API key from the APImage Dashboard 🡥. Test the Workflow Enter a valid image URL and a descriptive prompt in the Replace Background form. Click Run Workflow to see the processed image downloaded locally. Optional: Customize Output Storage Add nodes after the Download step to automatically save images to your preferred storage service or database. Requirements n8n instance: Cloud or self-hosted instance. APImage account and API key: Required to access the AI API. How to Customize the Workflow Change Background Prompts:** Modify the form or connect to dynamic sources like databases, CMS, or cloud storage. Adjust AI Settings:** Customize preserve_subject, light_direction, and light_strength in the APImage node for perfect results. Extend Outputs:** Connect to additional platforms for automatic sharing with teams, clients, or CMS systems. Automate Input:** Replace manual form triggers with automated triggers from Google Sheets, Airtable, Shopify, or product databases to handle bulk processing without manual intervention. Example Use Cases E-commerce:** Consistent product images with professional backgrounds. Marketing & Social Media:** Quickly generate visuals adapted to multiple themes. Photography & Design:** Produce mockups, portraits, and conceptual images with realistic lighting. Business Automation:** Scale image pipelines efficiently for large volumes. FAQ Q: What types of images are supported? A: JPG, PNG, and WebP are supported. Q: Can I choose a custom background? A: Yes. Provide a text description or integrate with other nodes supplying pre-defined backgrounds. Q: What is the default filename for processed images? A: The default filename is data, unless renamed in the workflow. Q: Do I need to store images locally? A: No. Connect output nodes to databases, cloud storage, or CMS platforms to store images automatically. Q: Can APImage be used in automated workflows? A: Absolutely. Integrate with n8n to process images automatically from various sources. Q: Does it enhance image quality? A: APImage adjusts lighting and contrast for natural, realistic results. Q: How is background replacement different from background removal? A: Background removal makes the background transparent. Background replacement swaps it with a new one and adjusts lighting for a natural look. Q: Are there limits to the number of images processed? A: Limits depend on your subscription plan and allocated credits

Description: Bridge the gap between Monday.com and Jira with this intelligent n8n automation template. The workflow listens for new or updated Monday.com items, normalizes data fields, and syncs them with your Jira backlog—automatically detecting duplicates using fuzzy matching logic. It then creates or updates Jira issues accordingly and logs the results back into Monday.com, ensuring your product and engineering teams stay aligned in real time. Ideal for project managers, product ops, and agile teams who manage intake in Monday.com but execute tasks in Jira. ✅ What This Template Does (Step-by-Step) 🌐 Webhook Trigger from Monday.com: Starts automatically whenever a new task or update occurs in Monday.com. 🔄 Normalize Monday.com Data: Extracts and cleans key data fields such as summary, component, severity, and description for consistent formatting before sending to Jira. 📊 Query Jira Backlog: Fetches all existing issues from Jira to establish a baseline for duplicate detection. 🔍 Detect Duplicates with Fuzzy Matching: Compares Monday item titles with Jira summaries using character-level similarity (>80% threshold) to detect potential duplicates even with minor variations. ⚖️ Decision Gate: Duplicate or New: If duplicate found: updates the existing Jira issue with new data. If no match: creates a new Jira task in the appropriate project and issue type. 🔧 Update Existing Jira Issues: Automatically enhances Jira tickets with latest information from Monday.com including updated priority, description, and reference links. ✨ Create New Jira Issues: For new requests, generates a Jira task with details mapped from Monday—complete with severity, component, and description. 📝 Log Actions Back to Monday.com: Posts an update back to the originating Monday item confirming whether the action created or updated a Jira issue, including timestamp and Jira key link. 📋 (Optional) Create New Monday Board: Can also auto-create a private board in Monday.com for project-specific task organization. 🧠 Key Features 🔍 Smart fuzzy duplicate detection (>80% match threshold) ⚙️ Full bidirectional visibility between Monday.com and Jira 📢 Automatic task creation and update logic 🧾 Real-time status logging and audit trail in Monday.com 🔐 Secure API-based connections for both platforms 💼 Use Cases 💡 Sync product feedback and feature requests from Monday to Jira 🎯 Centralize intake forms and align engineering backlogs 🤝 Eliminate duplicate Jira issues from multiple product submissions 📈 Maintain transparent traceability across tools 📦 Required Integrations Monday.com API – for item intake and updates Jira Software Cloud API – for issue creation and modification 🎯 Why Use This Template? ✅ Eliminates duplicate Jira issues automatically ✅ Keeps Monday.Com and Jira perfectly aligned ✅ Saves hours of manual task reconciliation ✅ Ideal for agile and cross-functional collaboration