Workflow Templates

Tags*: AI Agent, Supply Chain, Logistics, Circular Economy, Route Planning, Transportation, GPS API Context Hi! I’m Samir — a Supply Chain Engineer and Data Scientist based in Paris, and founder of LogiGreen Consulting. I help logistics teams reduce operational workload and errors by combining AI automation, route optimization APIs, and workflow automation. This workflow is part of a circular economy project, where stores return reusable packaging (bins, crates, containers) to a central warehouse. > Let's circular economies with AI-powered automation using n8n! 📬 For business inquiries, you can add find me on LinkedIn Who is this template for? This workflow is designed for logistics teams participating in circular economy loops. Let us imagine your transportation company receives this pickup request: The two AI Agent nodes connected to Openroute Service API will process the information and reply with the detailed route plan. The results include driving time and the optimal sequence of stops generated by the multi-stop optimization endpoint of the API. How does it work? This workflow automates the end-to-end processing of multi-stop pickup requests for reusable packaging: 📨 Gmail Trigger listens for collection request emails 🧠 AI Agent parses the email into structured data (store ID, address, date) 📍 Each stop is geocoded into GPS coordinates 🗺️ OpenRouteService optimizes the stop sequence using truck-specific routing 📄 A second AI Agent formats a confirmation email in HTML with the ordered pickup plan 📧 The reply is sent back with all details including duration and route Steps: 💌 Trigger on a new Gmail message 🧠 Extract data using AI Agent (e.g., stores, addresses, times) 📑 Store raw and processed data in Google Sheets 📍 Enrich with GPS coordinates 🚚 Optimize route using OpenRouteService (truck profile) 📄 Format the confirmation using an AI Agent 📬 Send reply to requester with route and timing What do I need to get started? You’ll need: A Gmail account to receive collection requests A Google Sheet to store and review data A free OpenRouteService API key Access to OpenAI for using AI Agent nodes Sample pickup request emails to test Next Steps 🗒️ Use the sticky notes inside the n8n canvas to: Plug in your Gmail and OpenRouteService credentials Try with a sample store collection email Validate the confirmation format and route accuracy This template was built using n8n v1.93.0 Submitted: June 7, 2025

Tags*: AI Agent, Supply Chain, Logistics, Route Planning, Transportation, GPS API Context Hi! I’m Samir — a Supply Chain Engineer and Data Scientist based in Paris, and founder of LogiGreen Consulting. I help companies improve their logistics operations using data, AI, and automation to reduce costs and minimize environmental footprint. > Let’s use n8n to automate order management for transportation companies! 📬 For business inquiries, you can add find me on LinkedIn Who is this template for? This workflow is designed for small transportation companies and carriers that handle their delivery request by email. Two AI Agent nodes and a connection to Openroute Service API are used to parse the content of pickup requests The results include driving time and driving distance in a comprehensive and concise reply generated by the second AI Agent. How does it work? This n8n workflow automates the processing of shipment request emails and enriches them with distance and driving time using the OpenRouteService API. 📥 Extract structured logistics data (pickup, delivery, contact) using an AI Agent 📌 Geocode pickup and delivery addresses into GPS coordinates 🚚 Query OpenRouteService using the truck (driving-hgv) profile 📏 Get the driving distance (in km) and estimated time (in minutes) 📤 Store all data in a connected Google Sheet 📧 Send back a professional confirmation email to the customer Steps: 📩 Trigger the workflow from a new Gmail message 🧠 Use the AI Agent to extract structured data from the email 📊 Record and enrich shipment details in a Google Sheet 🗺️ Geocode addresses into coordinates 🚦 Get driving distance & time via OpenRouteService 📬 Generate and send back a confirmation email using AI What do I need to get started? This workflow requires: A Gmail account to receive shipment requests A Google Sheet to log and update shipment info A free OpenRouteService API key 👉 Get one here OpenAI API access to use the AI Agent node Next Steps 🗒️ Follow the sticky notes inside the workflow canvas to: Plug your Gmail and Google credentials Add your OpenRouteService API key Test by sending a sample email and see the response! 🎥 Check the Tutorial This template was built using n8n v1.93.0 Submitted: June 5, 2025

An example workflow for a multilanguage Telegram bot. It allows adding many new languages to the bot without editing the workflow. Important note! Due to some breaking API changes in NocoDB some of its node options are not working at the moment (MAY 2022). These two nodes were replaced by HTTP request nodes. Functionality is still the same.

This n8n workflow automates the process of capturing and storing incoming email details in a structured spreadsheet format, such as Google Sheets or Excel. Whenever a new email is received, the workflow extracts key details—including the sender’s email, subject, email body, and optional attachments—and logs them as a new row in the spreadsheet. You can customise this workflow to extract additional details, filter emails based on specific criteria, or send notifications when new entries are added. Pre-conditions & Requirements Before setting up this workflow, ensure that: You have access to the email provider (e.g., Gmail, Outlook, or IMAP-supported email services). The Gmail Node must be enabled in n8n. You must authenticate n8n with Google OAuth2 to access your inbox. Ensure that the Gmail API is enabled in the Google Cloud Console. You have an existing Google Sheet where data will be stored. The Google Sheets API is enabled. You authenticate n8n with your Google account. Steps Step 1: Add the Gmail Trigger Node Click on "Add Node" and search for "Gmail". Select "Gmail Trigger" and click to add it. Under Authentication, click "Create New" and authenticate with your Google account. (If you have already connected your Google account, simply select it.) In the Trigger Event field, select "Message Received". Under Filters, you can specify: Label/Mailbox: If you want to listen to emails from a specific folder (optional). From Address: If you only want to receive emails from specific senders (optional). Click "Execute Node" to test the connection. Click "Save". What This Does: This node listens for new incoming emails in your Gmail inbox. Step 2: Store Email Data in Google Sheets Click on "Add Node" and search for "Google Sheets" (or Microsoft Excel, if applicable) Under Authentication, connect your Google account Select the target Spreadsheet and Sheet Name where the data will be stored Set the Operation to "Append Row" Map the extracted email data to the correct columns. Click "Execute Node" to test and verify data storage Click "Save" What This Does: This node automatically adds a new row for each incoming email, ensuring a structured and searchable email log. Final Step Attach both node and execute the workflow. Who’s behind this? WeblineIndia’s AI development team. We've delivered 3500+ software projects across 25+ countries since 1999. From no-code automations to complex AI systems — our AI team builds tools that drive results. Looking to hire AI developers? Start with us.

This workflow automates the process of analyzing emails and their attachments (PDFs and images) using AI models (DeepSeek, Gemini, and OpenRouter). It extracts and summarizes the content of emails and attachments, saves the summaries to Google Sheets, and sends a final consolidated summary via Telegram. This is a powerful tool for automating email analysis and summarization, saving time and ensuring that important information is easily accessible and actionable. Below is a breakdown of the workflow: 1. How It Works The workflow is designed to process incoming emails, analyze their content and attachments, and generate summaries. Here's how it works: Email Trigger: The workflow starts with the Email Trigger (IMAP) node, which monitors an email inbox for new emails. If an email contains attachments, the workflow processes them. Check for Attachments: The Contain Attachments? node checks if the email has attachments. If attachments are present, the workflow proceeds to process them. Process Attachments: The Get PDF and Images Attachments node extracts PDF and image attachments from the email. The Switch node separates PDFs and images for further processing: PDFs: The Extract from PDF node extracts text from PDFs, and the PDF Analyzer node summarizes the content. Images: The Analyze Image node uses AI to describe the content of images. Summarize Email Content: The Convert Text node converts the email's HTML content to plain text. The Email Summarization Chain node uses AI to generate a summary of the email's text content. Save Summaries: The Save Summary PDF, Save Summary Image, and Save Summary Text nodes save the summaries of PDFs, images, and email text, respectively, to Google Sheets. Consolidate Summaries: The All Summaries node aggregates the summaries of the email text, PDFs, and images. The Create Final Summary node uses AI to generate a unified summary of all the content. Send Final Summary: The Send Final Summary node sends the consolidated summary via Telegram to a specified chat ID. 2. Set Up Steps To set up and use this workflow in n8n, follow these steps: IMAP Configuration: Set up IMAP credentials in n8n for the Email Trigger (IMAP) node. Ensure the email account is accessible via IMAP. AI Model Configuration: Configure the DeepSeek, Gemini, and OpenRouter credentials in n8n for the Email Summarization Chain, PDF Analyzer, and Create Final Summary nodes. Ensure the AI models are set up to generate summaries. Google Sheets Integration: Set up Google Sheets credentials in n8n for the Save Summary PDF, Save Summary Image, and Save Summary Text nodes. Specify the Google Sheet and worksheet where the summaries will be saved. Telegram Integration: Set up Telegram credentials in n8n for the Send Final Summary node. Insert your Chat ID in the Telegram node to receive the final summary. Test the Workflow: Send an email with attachments (PDFs and images) to the monitored email account. The workflow will: Extract and summarize the email content and attachments. Save the summaries to Google Sheets. Send a consolidated summary via Telegram. Optional Customization: replace IMAP trigger with Gmail or Outlook trigger Modify the workflow to include additional features, such as: Adding more AI models for different types of analysis. Sending notifications via other channels (e.g., Slack, email). Integrating with other storage services (e.g., Dropbox, AWS S3). Need help customizing? Contact me for consulting and support or add me on Linkedin.

This workflow goes through the teachable webhook request types and adds a user, updates him and tags him with #unsubscribe or removes the #unsubscribe tag. It also tags the user with the tag of the name of the course. Enjoy!

This workflow is designed to manage the assignment and validation of unique QR code coupons within a lead generation system with SuiteCRM. How it Works This workflow automates the process of assigning unique QR code coupons to leads generated through a form submission, ensuring no duplicates are created, and validating the usage of coupons. Here's how it operates: Webhook Trigger: The workflow starts with a Webhook node that listens for incoming requests containing QR code data. A Set coupon node extracts the QR code value from the request parameters. Validation of QR Code: An If node checks if the QR code exists in the incoming data. If it does, the process proceeds; otherwise, a "No coupon" response is sent back. Coupon Lookup: The Get Lead node queries a Google Sheets document to check if the QR code corresponds to an existing lead. A subsequent Not used? node verifies whether the coupon has already been used by checking the "USED COUPON?" field in the sheet. Lead Duplication Check: When a new lead submits the form (On form submission), the Duplicate Lead? node checks if the email already exists in the system to prevent duplicates. Coupon Assignment: If the lead is not a duplicate, the Get Coupon node retrieves an available unassigned coupon from the Google Sheets document. The Token SuiteCRM node generates an access token for SuiteCRM, and the Create Lead SuiteCRM node creates a new lead entry in SuiteCRM, associating it with the assigned coupon. QR Code Generation and Email Notification: The Get QR node generates a QR code image URL for the assigned coupon. The Send Email node sends an email to the lead with the QR code attached. Response Handling: Depending on the validation results, the workflow responds with appropriate messages: "Coupon OK" if the coupon is valid and unused. "Coupon KO" if the coupon has already been used. "Coupon not valid" if the QR code does not exist. Set Up Steps To replicate this workflow in your own n8n environment, follow these steps: Configuration: Set up an n8n instance either locally or via cloud services. Import the provided JSON configuration file into your workspace. Configure all required credentials, such as: Google Sheets OAuth2 API for accessing the spreadsheet. SuiteCRM API credentials (e.g., SUITECRMURL, CLIENTID, CLIENTSECRET). SMTP credentials for sending emails. Customization: Adjust the Webhook URL to match your deployment environment. Modify the Google Sheets document ID and sheet name in nodes like Duplicate Lead?, Get Coupon, Update Sheet, and Update coupon used. Update the SuiteCRM API endpoint and credentials in nodes like Token SuiteCRM and Create Lead SuiteCRM. Customize the email template in the Send Email node to match your branding and messaging requirements. Ensure the QR code generation URL in the Get QR node points to a valid QR code generator service. By following these steps, you can effectively implement and customize this workflow to manage lead generation and coupon assignments in your organization.

🧩 Problem Solved Eliminates the slow, inconsistent, and error-prone process of manually replying to Facebook comments by automating it with AI, ensuring fast, accurate, and on-brand customer engagement 24/7. 📝 Description This workflow automatically monitors your latest Facebook post for new comments. For each new comment, an AI agent instantly generates a friendly, personalized reply in Egyptian Arabic, using your Notion knowledge base to ensure all product info is accurate. It prevents spam by never replying to the same comment twice. Simple Flow: New Comment → Duplicate Check → AI Analysis → Post Reply → Log Action. 🎯 Key Benefits 24/7 Instant Replies: Engage customers immediately, anytime. Perfect Brand Voice: Consistent, empathetic, natural Egyptian Arabic tone in every reply. Always Accurate: Pulls facts directly from your knowledge base; never invents details. No Duplicate Replies: Robust checks ensure each comment gets only one response. Huge Time Saver: Frees your team from constantly monitoring comments. 🛠️ Core Features Facebook API Integration (Read & Reply) Notion Database Integration (Knowledge Base & Logging) AI Response Generation (Google Gemini) Duplicate Comment Prevention Automated Workflow Logic 🔧 Requirements Facebook Access Token with pages_read_engagement and pages_manage_posts permissions. Two Notion Databases: One for your product knowledge, one to log processed comments. Google Gemini API Key for AI. n8n Credentials for Facebook, Notion, and Gemini. ⚙️ Quick Customization Tone & Style: Edit the prompt in the Generate Customer Reply node. Product Info: Add fields to your Notion Knowledge Base database. Escalation: Add a step to flag angry comments for a human agent. 🧠 Perfect For E-commerce: Answering product questions on promo posts. Healthcare: Providing accurate drug info with compassion. Local Businesses: Replying to queries about hours/menu items. Any Business that wants fast, professional customer engagement on social media. Need help? Connect on LinkedIn

Who we are We are Aprende n8n, the first n8n Spanish course for all n8n lovers. If you want to learn more, you can find out more at Aprende n8n. Task goal This task allows extracting data from any email body with a NoCode snippet. An small explanation You receive an email when a user submits a form from your website. All those emails usually have the same structure as the next one: Name: Miquel Email: miquel@aprenden8n.com Subject: Welcome aboard Message: Hi Miquel! Thank you for your signup! This task allows to parse any email body and assign all values to the defined labels, getting an output like this: { "Name": "Miquel", "Email": "miquel@aprenden8n.com", "Subject": "Welcome aboard", "Message" "Hi Miquel! Thank you for your signup!" } After importing it When you import the import, you get the next task in your n8n: We recommend importing this workflow into your current task and adapting it. You define a couple of variables in the "Set values" SET: body: the email body you want to parse. You can add this as an expression from previous variables. labels: the keywords you want to detect and parse. Labels are case insensitive. We define the next values: Body Name: Miquel Email: miquel@aprenden8n.com Subject: Welcome aboard Message: Hi Miquel! Thank you for your signup! Labels Name,Email,Subject,Message A screenshot of the Set output is the next one If we check the "Function item" Node, we get the next content after executing the task: Capabilities The task has the next features: You can detect as many labels as you want. Label detection is case insensitive. You can use the snippet as an independent workflow to call it generically, adding the Function item to the workflow and passing body and labels as paremeters. Limitations This task has limitations: The parser only accepts the multiline values at the end of the email. Help and comments If you have any doubt about this snippet, please, contact us at miquel@aprenden8n.com. You can contact us at Aprende n8n or in the Spanish n8n community

This workflow allows you to create, add an attachment, and send a draft using the Microsoft Outlook node. Microsoft Outlook node: This node creates a draft message with HTML content. You can either set the content as Text or HTML. You can also add the recipients to the draft in this node. HTTP Request node: This node fetches the logo of n8n from a URL and returns the binary data. You might want to fetch files from your machine or another email or a database. You can replace this node with the relevant node. Microsoft Outlook1 node: This node adds the attachment that we receive from the previous node to the draft message that we created. Microsoft Outlook2 node: This node sends the draft message to a recipient. Since we didn't mention the recipient in the Microsoft Outlook node, we add the recipient in this node. You can also enter multiple recipients.

This workflow allows you to find and verify emails and enrich your contact from a Google Sheet with Dropacontact and add them to Lemlist. Start node: The start node exists by default when you create a new workflow. Google Sheet node: This node will list all the records from Google Sheet. Dropcontact node: This node will find the verified email of the contact and enrich it to be able to contact him lemlist node: This node will add a contact to an existing campaign

This workflow allows you to send a message on Mattermost when a workflow is updated. Workflow Trigger node: The Workflow Trigger node will trigger the workflow when the workflow gets updated. Mattermost node: This node will send a message on Mattermost, notifying you about the update.