β»οΈ AI multi-stop planner for circular logistics with GPT-4o & Open Route API
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 optimisation 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 create circular economies with AI-powered automation using n8n!
π¬ For business inquiries, you can 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
πΊ Learn More with n8n Tutorials
Get hands-on experience with automation through my comprehensive n8n tutorial playlist, featuring 18+ complete, step-by-step videos and ready-to-use templates.
This template was built using n8n v1.93.0
Submitted: June 7, 2025
n8n AI Multi-Stop Planner for Circular Logistics with GPT-4o and Open Route API
This n8n workflow automates the process of planning multi-stop circular logistics routes. It leverages a combination of Google Sheets for input, an AI Agent (likely powered by GPT-4o based on the directory name) for intelligent route planning, and an external Open Route API for actual route calculation. The workflow is designed to streamline the creation of optimized routes, potentially for tasks like waste collection, delivery, or resource redistribution in a circular economy model.
What it does
This workflow automates the following steps:
- Triggers on new emails: It listens for new emails in a specified Gmail account. This acts as the starting point, likely indicating a request for route planning or new data availability.
- Reads data from Google Sheets: Upon triggering, it reads relevant logistics data (e.g., stop locations, quantities, vehicle capacity) from a Google Sheet.
- Prepares data for AI Agent: It transforms and formats the data from Google Sheets into a structured input suitable for the AI Agent.
- Generates route plan using AI Agent: An AI Agent (likely using GPT-4o) processes the input data to generate an optimized multi-stop route plan, considering circular logistics principles.
- Splits AI output for API calls: The AI Agent's output, which might contain multiple route segments or stop sequences, is split into individual items for further processing.
- Calculates routes via HTTP Request: For each segment or stop sequence, it makes an HTTP request to an external Open Route API to get detailed route information (e.g., distance, duration).
- Merges API responses: The individual route calculation responses are merged back together.
- Finalizes output: The merged route data is processed and potentially formatted.
- Sends email notification: The final route plan or a summary is sent via Gmail, likely to the requester or a logistics manager.
- Optional Delay: A "Wait" node is present, which could be used to introduce a delay between operations, potentially to manage API rate limits or allow for manual review.
Prerequisites/Requirements
To use this workflow, you will need:
- n8n Instance: A running n8n instance.
- Google Account: A Google account with access to Gmail and Google Sheets.
- Google Sheets Credential: Configured n8n credential for Google Sheets.
- Gmail Credential: Configured n8n credential for Gmail.
- OpenAI API Key (or similar AI service): For the AI Agent node to function. This is inferred from the directory name "gpt-4o".
- Open Route API Key/Endpoint: Access to an Open Route API (e.g., OpenRouteService, HERE, Google Maps API) for route calculations.
Setup/Usage
- Import the workflow: Download the provided JSON and import it into your n8n instance.
- Configure Credentials:
- Set up your Google Sheets credential (OAuth2 recommended) to grant n8n access to your logistics spreadsheet.
- Set up your Gmail credential (OAuth2 recommended) for sending and receiving emails.
- Configure the AI Agent node with your OpenAI API key or the API key for your chosen AI service.
- Configure the HTTP Request node with the endpoint and any necessary authentication for your chosen Open Route API.
- Customize Nodes:
- Gmail Trigger: Configure the trigger to listen for specific emails (e.g., subject line, sender) that initiate the route planning process.
- Google Sheets: Specify the Spreadsheet ID and Sheet Name where your logistics data is stored. Adjust the read operation as needed.
- Edit Fields (Set): Modify this node to correctly map and transform your Google Sheet data into the format expected by the AI Agent.
- AI Agent: Define the prompt and any specific parameters for your AI model to generate optimal circular logistics routes.
- Structured Output Parser: Adjust the schema if the AI Agent's output structure changes.
- Loop Over Items (Split in Batches) and Split Out: These nodes handle iterating over the AI's output. Ensure they correctly process the route segments.
- HTTP Request: Update the URL, headers, and body to match the requirements of your chosen Open Route API for calculating routes.
- Merge: Ensure this node correctly combines the results from multiple HTTP requests.
- Code: If custom logic is required for data manipulation, update the JavaScript code within this node.
- Gmail: Configure the recipient, subject, and body of the email that will send the final route plan.
- Wait: Adjust the delay duration if necessary.
- Activate the workflow: Once configured, activate the workflow to start automating your circular logistics planning.
Related Templates
Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets
This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitorβs webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger β Manually start the workflow or schedule it to run periodically. Input Setup β Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) β Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring β Clean and convert GPT output into JSON format. Data Storage (Google Sheets) β Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the βSet Input Fieldsβ node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors β Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection β Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report β Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization β Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs β Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting Itβs a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.
Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax
Spark your creativity instantly in any chatβturn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. π What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing π§ Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation π Required Credentials OpenAI API Setup Go to platform.openai.com β API keys (sidebar) Click "Create new secret key" β Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai β Dashboard β API Keys Generate a new API key β Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) βοΈ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflowβchat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" π― Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration β οΈ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions
Automate invoice processing with OCR, GPT-4 & Salesforce opportunity creation
PDF Invoice Extractor (AI) End-to-end pipeline: Watch Drive β Download PDF β OCR text β AI normalize to JSON β Upsert Buyer (Account) β Create Opportunity β Map Products β Create OLI via Composite API β Archive to OneDrive. --- Node by node (what it does & key setup) 1) Google Drive Trigger Purpose: Fire when a new file appears in a specific Google Drive folder. Key settings: Event: fileCreated Folder ID: google drive folder id Polling: everyMinute Creds: googleDriveOAuth2Api Output: Metadata { id, name, ... } for the new file. --- 2) Download File From Google Purpose: Get the file binary for processing and archiving. Key settings: Operation: download File ID: ={{ $json.id }} Creds: googleDriveOAuth2Api Output: Binary (default key: data) and original metadata. --- 3) Extract from File Purpose: Extract text from PDF (OCR as needed) for AI parsing. Key settings: Operation: pdf OCR: enable for scanned PDFs (in options) Output: JSON with OCR text at {{ $json.text }}. --- 4) Message a model (AI JSON Extractor) Purpose: Convert OCR text into strict normalized JSON array (invoice schema). Key settings: Node: @n8n/n8n-nodes-langchain.openAi Model: gpt-4.1 (or gpt-4.1-mini) Message role: system (the strict prompt; references {{ $json.text }}) jsonOutput: true Creds: openAiApi Output (per item): $.message.content β the parsed JSON (ensure itβs an array). --- 5) Create or update an account (Salesforce) Purpose: Upsert Buyer as Account using an external ID. Key settings: Resource: account Operation: upsert External Id Field: taxid_c External Id Value: ={{ $json.message.content.buyer.tax_id }} Name: ={{ $json.message.content.buyer.name }} Creds: salesforceOAuth2Api Output: Account record (captures Id) for downstream Opportunity. --- 6) Create an opportunity (Salesforce) Purpose: Create Opportunity linked to the Buyer (Account). Key settings: Resource: opportunity Name: ={{ $('Message a model').item.json.message.content.invoice.code }} Close Date: ={{ $('Message a model').item.json.message.content.invoice.issue_date }} Stage: Closed Won Amount: ={{ $('Message a model').item.json.message.content.summary.grand_total }} AccountId: ={{ $json.id }} (from Upsert Account output) Creds: salesforceOAuth2Api Output: Opportunity Id for OLI creation. --- 7) Build SOQL (Code / JS) Purpose: Collect unique product codes from AI JSON and build a SOQL query for PricebookEntry by Pricebook2Id. Key settings: pricebook2Id (hardcoded in script): e.g., 01sxxxxxxxxxxxxxxx Source lines: $('Message a model').first().json.message.content.products Output: { soql, codes } --- 8) Query PricebookEntries (Salesforce) Purpose: Fetch PricebookEntry.Id for each Product2.ProductCode. Key settings: Resource: search Query: ={{ $json.soql }} Creds: salesforceOAuth2Api Output: Items with Id, Product2.ProductCode (used for mapping). --- 9) Code in JavaScript (Build OLI payloads) Purpose: Join lines with PBE results and Opportunity Id β build OpportunityLineItem payloads. Inputs: OpportunityId: ={{ $('Create an opportunity').first().json.id }} Lines: ={{ $('Message a model').first().json.message.content.products }} PBE rows: from previous node items Output: { body: { allOrNone:false, records:[{ OpportunityLineItem... }] } } Notes: Converts discount_total β per-unit if needed (currently commented for standard pricing). Throws on missing PBE mapping or empty lines. --- 10) Create Opportunity Line Items (HTTP Request) Purpose: Bulk create OLIs via Salesforce Composite API. Key settings: Method: POST URL: https://<your-instance>.my.salesforce.com/services/data/v65.0/composite/sobjects Auth: salesforceOAuth2Api (predefined credential) Body (JSON): ={{ $json.body }} Output: Composite API results (per-record statuses). --- 11) Update File to One Drive Purpose: Archive the original PDF in OneDrive. Key settings: Operation: upload File Name: ={{ $json.name }} Parent Folder ID: onedrive folder id Binary Data: true (from the Download node) Creds: microsoftOneDriveOAuth2Api Output: Uploaded file metadata. --- Data flow (wiring) Google Drive Trigger β Download File From Google Download File From Google β Extract from File β Update File to One Drive Extract from File β Message a model Message a model β Create or update an account Create or update an account β Create an opportunity Create an opportunity β Build SOQL Build SOQL β Query PricebookEntries Query PricebookEntries β Code in JavaScript Code in JavaScript β Create Opportunity Line Items --- Quick setup checklist π Credentials: Connect Google Drive, OneDrive, Salesforce, OpenAI. π IDs: Drive Folder ID (watch) OneDrive Parent Folder ID (archive) Salesforce Pricebook2Id (in the JS SOQL builder) π§ AI Prompt: Use the strict system prompt; jsonOutput = true. π§Ύ Field mappings: Buyer tax id/name β Account upsert fields Invoice code/date/amount β Opportunity fields Product name must equal your Product2.ProductCode in SF. β Test: Drop a sample PDF β verify: AI returns array JSON only Account/Opportunity created OLI records created PDF archived to OneDrive --- Notes & best practices If PDFs are scans, enable OCR in Extract from File. If AI returns non-JSON, keep βReturn only a JSON arrayβ as the last line of the prompt and keep jsonOutput enabled. Consider adding validation on parsing.warnings to gate Salesforce writes. For discounts/taxes in OLI: Standard OLI fields donβt support per-line discount amounts directly; model them in UnitPrice or custom fields. Replace the Composite API URL with your orgβs domain or use the Salesforce nodeβs Bulk Upsert for simplicity.



