Route and audit Odoo draft orders with GPT‑4o and Arabic semantic scheduling
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This AI workflow has 24 nodes and runs on a schedule (every 30 minutes). Along the way it connects Odoo and OpenAI Chat Model.
How it runs
Trigger: On a schedule (every 30 minutes).
- Get Sales Orders (Odoo): get many (custom)
- Get Customer Data (Odoo): get (custom)
- Get POS Order (Odoo): get many (custom)
- Merge: merges the data from its input branches
- Get many items (Odoo): get many (custom)
- Edit Fields (Edit Fields (Set)): sets 13 fields: id, name, partner_id…
- AI Agent: runs an AI agent, with model: OpenAI Chat Model; memory: Simple Memory
- Switch: routes items into 4 branches
- Get Source ID (Odoo): get many (custom)
- Get Source ID (Odoo): get many (custom)
…plus 11 more steps. See the full node list below.
Services it uses
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (11)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - Odoo
n8n-nodes-base.odoo - Merge
n8n-nodes-base.merge - Edit Fields (Set)
n8n-nodes-base.set - AI Agent
@n8n/n8n-nodes-langchain.agent - OpenAI Chat Model
@n8n/n8n-nodes-langchain.lmChatOpenAi - Simple Memory
@n8n/n8n-nodes-langchain.memoryBufferWindow - Switch
n8n-nodes-base.switch - Loop Over Items (Split in Batches)
n8n-nodes-base.splitInBatches - HTTP Request
n8n-nodes-base.httpRequest - If
n8n-nodes-base.if
From the author
What it is Manual order entry in retail and e-commerce often results in fragmented data. Sales representatives might skip mandatory address fields or write critical delivery instructions in unstructured, regional slang inside the POS notes. This workflow acts…