🤖🚚 AI agent for transportation orders management with GPT-4o and Open Route API

Open on n8n.io

$20/month : Unlimited workflows

2500 executions/month

Try free

THE #1 IN WEB SCRAPING

Scrape any website without limits

Try free

HOSTINGER

Early Deal
DISCOUNT 20%

Self-hosted n8n

Unlimited workflows - from $4.99/mo

Try free

#1 hub for scraping, AI & automation

6000+ actors - $5 credits/mo

Try free

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

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 foun...

Best for

Ticket Management automation workflows
AI Summarization automation workflows
advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.gmailtrigger, @n8n/n8n-nodes-langchain.outputparserstructured, @n8n/n8n-nodes-langchain.agent, n8n-nodes-base.googlesheets, n8n-nodes-base.wait, n8n-nodes-base.httprequest, n8n-nodes-base.set, @n8n/n8n-nodes-langchain.lmchatopenai

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Samir Saci.

Original n8n.io source

1.1 Workflow description

Title: 🤖🚚 AI agent for transportation orders management with GPT-4o and Open Route API
Workflow name: 🤖🚚 AI agent for transportation orders management with GPT-4o and Open Route API

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

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - Gmail Trigger

Type / Role: n8n-nodes-base.gmailTrigger - gmailTrigger
Config choices: Version 1.2

Block 2 - Structured Output Parser

Type / Role: @n8n/n8n-nodes-langchain.outputParserStructured - outputParserStructured
Config choices: Version 1.2

Block 3 - AI Agent Parser

Type / Role: @n8n/n8n-nodes-langchain.agent - agent
Config choices: Version 1.9

Block 4 - Record Email Content

Type / Role: n8n-nodes-base.googleSheets - googleSheets
Config choices: Version 4.6

Block 5 - Collect Addresses

Type / Role: n8n-nodes-base.googleSheets - googleSheets
Config choices: Version 4.6

Block 6 - 5 sec

Type / Role: n8n-nodes-base.wait - wait
Config choices: Version 1.1

Block 7 - Query Open Route API Pickup

Type / Role: n8n-nodes-base.httpRequest - httpRequest
Config choices: Version 4.2

Block 8 - Save Pickup GPS

Type / Role: n8n-nodes-base.googleSheets - googleSheets
Config choices: Version 4.6

Block 9 - GPS Pickup

Type / Role: n8n-nodes-base.set - set
Config choices: Version 3.4

Block 10 - Query Open Route API Delivery

Type / Role: n8n-nodes-base.httpRequest - httpRequest
Config choices: Version 4.2

Block 11 - GPS Delivery

Type / Role: n8n-nodes-base.set - set
Config choices: Version 3.4

Block 12 - Save Delivery GPS

Type / Role: n8n-nodes-base.googleSheets - googleSheets
Config choices: Version 4.6

Block 13 - Collect Coordinates

Type / Role: n8n-nodes-base.googleSheets - googleSheets
Config choices: Version 4.6

Block 14 - Request Open Route API

Type / Role: n8n-nodes-base.httpRequest - httpRequest
Config choices: Version 4.2

Block 15 - Save Results

Type / Role: n8n-nodes-base.googleSheets - googleSheets
Config choices: Version 4.6

Block 16 - Collect Shipment Information

Type / Role: n8n-nodes-base.googleSheets - googleSheets
Config choices: Version 4.6

Block 17 - Driving Time & Distance

Type / Role: n8n-nodes-base.set - set
Config choices: Version 3.4

Block 18 - OpenAI Chat Model

Type / Role: @n8n/n8n-nodes-langchain.lmChatOpenAi - lmChatOpenAi
Config choices: Version 1.2

Block 19 - AI Agent Reply

Type / Role: @n8n/n8n-nodes-langchain.agent - agent
Config choices: Version 1.9

Block 20 - Reply

Type / Role: n8n-nodes-base.gmail - gmail
Config choices: Version 2.1

Block 21 - Sticky Note

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 22 - Sticky Note1

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 23 - Sticky Note2

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 24 - OpenAI Chat Model2

Type / Role: @n8n/n8n-nodes-langchain.lmChatOpenAi - lmChatOpenAi
Config choices: Version 1.2

Showing the first 24 of 26 workflow blocks. Download the JSON for the full node graph.

3. Summary Table

Workflow	🤖🚚 AI agent for transportation orders management with GPT-4o and Open Route API
Complexity	advanced
Nodes	26
Categories	Ticket Management, AI Summarization
Author	Samir Saci
Published	05 Jun 2025

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

Use the JSON export at /data/workflows/4692/4692.json as the source template for this automation.
2. Import the template into n8n

Open n8n, import the downloaded JSON, and review each node before activating the workflow.
3. Configure credentials and variables

Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
4. Test with sample data

Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
5. Activate and monitor

Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Download workflow JSON Original n8n.io source Ticket Management workflows AI Summarization workflows

Frequently asked questions

What does 🤖🚚 AI agent for transportation orders management with GPT-4o and Open Route API do?

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 foun...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Ticket Management, AI Summarization use case.

Samir Saci

31 workflows

Nodes

n8n-nodes-base.gmailtrigger @n8n/n8n-nodes-langchain.outputparserstructured @n8n/n8n-nodes-langchain.agent n8n-nodes-base.googlesheets n8n-nodes-base.wait n8n-nodes-base.httprequest n8n-nodes-base.set @n8n/n8n-nodes-langchain.lmchatopenai

Complexity

advanced

Published 05 Jun 2025

Likes 0

View on n8n.io Download Workflow

Install path: /data/workflows/4692/4692.json

Share Your Workflow

Have a useful automation to share? Publish it and help the community.

Submit Your Template How to Submit

Related Workflows

Track post-therapy wellness with GPT-4o-mini, Telegram, Slack and Sheets

## Quick Overview This workflow uses Google Sheets, OpenAI, Telegram, and Slack to send post-therapy check-in messages, analyze patient replies for sentiment and risk, alert therapists to at-risk responses, and log non-urgent replies for ongoing wellness tracking. ## How it works 1. Runs every hour on a schedule trigger. 2. Reads session records from Google Sheets and keeps only sessions that have a session date and have not been marked as check-in sent. 3. Uses OpenAI (gpt-4o-mini) to generate a personalized, non-clinical Telegram check-in message from the patient’s session details. 4. Sends the check-in to the patient via Telegram and updates the Google Sheets session row to store the message and mark the check-in as sent. 5. Triggers on incoming Telegram messages, looks up the patient in a Google Sheets master list by Telegram ID, and selects the most relevant recent session to provide context. 6. Sends the patient reply and session context to OpenAI for JSON-formatted sentiment classification and parses the result into structured fields. 7. If the sentiment is classified as at-risk, posts an urgent alert to a Slack channel; otherwise, appends the reply and sentiment details to a Google Sheets wellness log. ## Setup 1. Connect Google Sheets OAuth credentials and update the spreadsheet document ID and sheet names for Sessions, Patients_Master, and Wellness_Log. 2. Create and connect a Telegram bot credential, set up the Telegram trigger webhook, and ensure patient Telegram chat IDs are stored in Google Sheets. 3. Add an OpenAI API key credential and confirm the selected model (gpt-4o-mini) meets your requirements. 4. Connect Slack OAuth credentials and replace the placeholder Slack channel ID used for therapist alerts, and confirm the error-alert channel is set correctly. 5. Verify your Google Sheets columns match the workflow’s expected fields (for example session_id, checkin_sent, checkin_message_sent, therapist_slack_id) before activating.

View

Detect and route customer escalations with Claude, Slack and Linear

## Quick Overview This workflow receives support messages via a webhook, normalizes payloads from Gmail, Zendesk, Intercom, and HelpScout, and uses Anthropic Claude to detect escalation signals and severity, then posts alerts to Slack and creates Linear tickets for actionable cases. ## How it works 1. Receives an inbound support message via a POST webhook. 2. Normalizes the incoming payload (Gmail, Zendesk, Intercom, HelpScout, or a raw test payload) into a consistent schema with customer details, subject, body text, and a source URL. 3. Sends the normalized message to Anthropic Claude and parses the response into structured JSON containing escalation flags, severity, trigger phrases, a summary, and a suggested reply opening. 4. Stops processing silently when the message is not an escalation (severity is none). 5. Builds a formatted Slack alert and Linear issue payload, including SLA guidance, detected signals, and links back to the original conversation. 6. Posts the escalation alert to a configured Slack channel. 7. Creates a Linear ticket for critical, high, and medium severity escalations and sends a Slack DM to a manager for critical and high cases. ## Setup 1. Add an Anthropic API credential for the Anthropic Chat Model node. 2. Add a Slack OAuth2 credential, set the target channel (for example, #escalations), and set the manager’s Slack user ID for direct messages. 3. Add a Linear OAuth2 credential and replace the placeholder Linear team ID used when creating tickets. 4. Copy the webhook URL from the webhook trigger and configure Gmail/Zendesk/Intercom/HelpScout (or your custom source) to POST message payloads to it in one of the supported formats.

View

Triage construction incidents with GPT-4o, Slack, Gmail and Google Sheets

## Quick Overview This workflow ingests construction incident webhooks, normalizes the payload, and uses OpenAI GPT-4o-mini to classify each incident by type and urgency, then routes alerts to Slack and Gmail and logs incidents to Google Sheets, with a daily Slack digest generated from the sheet. ## How it works 1. Receives an incoming incident via a POST webhook. 2. Normalizes the incoming Procore/Fieldwire-style payload into a consistent incident object (ID, title, description, location, reporter, assignee, and timestamps). 3. Sends the incident details to OpenAI (GPT-4o-mini) to classify issue type and urgency and generate a short summary, recommended action, and tags. 4. Routes incidents by urgency, sending Critical incidents to Slack with an @channel mention and emailing details to a project manager via Gmail. 5. Sends High-urgency incidents to Slack as a formatted notice. 6. Appends every incident to a Google Sheets log with status set to open. 7. Runs daily at 18:00 server time, reads the incident log from Google Sheets, builds an urgency-grouped digest, and posts it to a Slack channel. ## Setup 1. Add credentials for OpenAI, Slack (OAuth2), Gmail (OAuth2), and Google Sheets (OAuth2). 2. Copy the webhook URL from the Webhook trigger and register it in your source system (for example, Procore or Fieldwire) as the incident-created endpoint. 3. Replace the placeholder Slack channel IDs for Critical, High, Digest, and Error alerts. 4. Update the Gmail recipient address ([email protected]) to your real project manager email. 5. Set the Google Sheets spreadsheet (document ID) and ensure the target sheet exists with columns that match the incident log fields used by the workflow. 6. Confirm the schedule trigger time (cron: 0 18 * * *) matches your desired timezone/server time for the daily digest.

View

Need Custom Automation?

Get help designing a custom n8n workflow that connects your stack and fits your process.

🤖🚚 AI agent for transportation orders management with GPT-4o and Open Route API

Workflow preview

Important notice

1. Workflow Overview

Best for

Tools used

Source and attribution

1.1 Workflow description

Context

Who is this template for?

How does it work?

Steps:

What do I need to get started?

Next Steps

1.2 Logical Blocks

2. Block-by-Block Analysis

Block 1 - Gmail Trigger

Block 2 - Structured Output Parser

Block 3 - AI Agent Parser

Block 4 - Record Email Content

Block 5 - Collect Addresses

Block 6 - 5 sec

Block 7 - Query Open Route API Pickup

Block 8 - Save Pickup GPS

Block 9 - GPS Pickup

Block 10 - Query Open Route API Delivery

Block 11 - GPS Delivery

Block 12 - Save Delivery GPS

Block 13 - Collect Coordinates

Block 14 - Request Open Route API

Block 15 - Save Results

Block 16 - Collect Shipment Information

Block 17 - Driving Time & Distance

Block 18 - OpenAI Chat Model

Block 19 - AI Agent Reply

Block 20 - Reply

Block 21 - Sticky Note

Block 22 - Sticky Note1

Block 23 - Sticky Note2

Block 24 - OpenAI Chat Model2

3. Summary Table

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

2. Import the template into n8n

3. Configure credentials and variables

4. Test with sample data

5. Activate and monitor

5. General Notes & Resources

Frequently asked questions