HumationHuman + Automation
Back to Catalog

Manage Odoo CRM with natural language using OpenAI and MCP Server

Rohit DabraRohit Dabra
873 views
2/3/2026
HTTP TriggerEmail NotificationSubscription ManagementPipedream IntegrationData Validation
Official Page

Odoo CRM MCP Server Workflow

šŸ“– Overview

This workflow connects an AI Agent with Odoo CRM using the Model Context Protocol (MCP).
It allows users to manage CRM data in Odoo through natural language chat commands.
The assistant interprets the userā€™s request, selects the appropriate Odoo action, and executes it seamlessly.

šŸ”¹ Key Features

  • Contacts Management: Create, update, delete, and retrieve contacts.
  • Opportunities Management: Create, update, delete, and retrieve opportunities.
  • Notes Management: Create, update, delete, and retrieve notes.
  • Conversational AI Agent: Understands natural language and maps requests to Odoo actions.
  • Model Used: OpenAI Chat Model.

This makes it easy for end-users to interact with Odoo CRM without needing technical commandsā€”just plain language instructions.

ā–¶ļø Demo Video

Watch the full demo here:
šŸ‘‰ YouTube Demo Video

āš™ļø Setup Guide

Follow these steps to set up and run the workflow:

1. Prerequisites

  • An Odoo instance configured with CRM enabled.
  • An n8n or automation platform account where MCP workflows are supported.
  • An OpenAI API key with access to GPT models.
  • MCP Server installed and running.

2. Import the Workflow

  1. Download the provided workflow JSON file.
  2. In your automation platform (n8n, Langflow, or other MCP-enabled tool), choose Import Workflow.
  3. Select the JSON file and confirm.

3. Configure MCP Server

  1. Go to your MCP Server Trigger node in the workflow.
  2. Configure it to connect with your Odoo instance.
    • Set API endpoint.
    • Provide authentication credentials (API key).
  3. Test the connection to ensure the MCP server can reach Odoo.

4. Configure the OpenAI Model

  1. Select the OpenAI Chat Model node in the workflow.
  2. Enter your OpenAI API Key.
  3. Choose the model (e.g., gpt-5 or gpt-5-mini).

5. AI Agent Setup

  • The AI Agent node links the Chat Model, Memory, and MCP Client.
  • Ensure the MCP Client is mapped to the correct Odoo tools (Contacts, Opportunities, Notes).
  • The System Prompt defines assistant behaviorā€”use the tailored system prompt provided earlier.

6. Activate and Test

  1. Turn the workflow ON (toggle Active).
  2. Open chat and type:
    • "Create a contact named John Doe with email john@example.com."
    • "Show me all opportunities."
    • "Add a note to John Doe saying 'Follow-up scheduled for Friday'."
  3. Verify the results in your Odoo CRM.

āœ… Next Steps

  • Extend functionality with Tasks, Stages, Companies, and Communication Logs for a complete CRM experience.
  • Add confirmation prompts for destructive actions (delete contact/opportunity/note).
  • Customize the AI Agentā€™s system prompt for your organizationā€™s workflows.

Manage Odoo CRM with Natural Language using OpenAI and MCP Server

This n8n workflow demonstrates how to build an AI agent that can interact with an Odoo CRM system using natural language. It leverages OpenAI's chat models and the Model Context Protocol (MCP) to provide a conversational interface for managing CRM tasks.

What it does

This workflow sets up an AI agent that can understand natural language requests and, in conjunction with an MCP Client, potentially interact with an Odoo CRM.

  1. Listens for incoming chat messages: The workflow is triggered by an incoming chat message, acting as the user's natural language input.
  2. Initializes a conversational AI Agent: An AI Agent node is used to process the incoming chat message. This agent is configured with an OpenAI Chat Model and a simple memory to maintain context during the conversation.
  3. Utilizes an MCP Client Tool: The AI Agent is equipped with an "MCP Client Tool." This tool is designed to communicate with an MCP Server (which would typically be another n8n workflow or service) to perform specific actions, such as interacting with an Odoo CRM.
  4. Provides a server endpoint for the MCP Client: An "MCP Server Trigger" node is present, indicating that this workflow is also capable of receiving requests from an MCP Client. While not directly connected in this specific JSON, it suggests a potential for this workflow to act as a backend for another AI agent or system.

Prerequisites/Requirements

  • n8n Instance: A running instance of n8n.
  • OpenAI API Key: An API key for OpenAI to use the OpenAI Chat Model.
  • MCP Client/Server Setup: Understanding and potentially a separate n8n workflow or application acting as an MCP Client that would interact with the "MCP Server Trigger" in this workflow, and an MCP Server that the "MCP Client Tool" would communicate with.

Setup/Usage

  1. Import the workflow:
    • Copy the provided JSON code.
    • In your n8n instance, go to "Workflows" and click "New".
    • Click the three dots in the top right corner and select "Import from JSON".
    • Paste the JSON code and click "Import".
  2. Configure Credentials:
    • OpenAI Chat Model: Configure your OpenAI API key credentials in the "OpenAI Chat Model" node.
  3. Activate the workflow: Once configured, activate the workflow by toggling the "Active" switch in the top right corner.
  4. Interact via Chat: Send a chat message to the "When chat message received" trigger. The AI agent will process your request, use its tools (including the MCP Client Tool), and respond.
  5. MCP Server Interaction (Advanced): If you intend for this workflow to act as an MCP Server, ensure that another MCP Client is configured to send requests to the endpoint exposed by the "MCP Server Trigger" node.

This workflow serves as a foundational component for building intelligent, natural language interfaces for complex systems like Odoo CRM, leveraging the power of AI agents and the Model Context Protocol.

Related Templates

Automate loan document analysis with Mistral OCR and GPT for underwriting decisions

LOB Underwriting with AI This template ingests borrower documents from OneDrive, extracts text with OCR, classifies each file (ID, paystub, bank statement, utilities, tax forms, etc.), aggregates everything per borrower, and asks an LLM to produce a clear underwriting summary and decision (plus next steps). Good to know AI and OCR usage consume credits (OpenAI + your OCR provider). Folder lookups by name can be ambiguousā€”use a fixed folderId in production. Scanned image quality drives OCR accuracy; bad scans yield weak text. This flow handles PIIā€”mask sensitive data in logs and control access. Start small: batch size and pagination keep costs/memory sane. How it works Import & locate docs: Manual trigger kicks off a OneDrive folder search (e.g., ā€œLOBsā€) and lists files inside. Per-file loop: Download each file ā†’ run OCR ā†’ classify the document type using filename + extracted text. Aggregate: Combine per-file results into a borrower payload (make BorrowerName dynamic). LLM analysis: Feed the payload to an AI Agent (OpenAI model) to extract underwriting-relevant facts and produce a decision + next steps. Output: Return a human-readable summary (and optionally structured JSON for systems). How to use Start with the Manual Trigger to validate end-to-end on a tiny test folder. Once stable, swap in a Schedule/Cron or Webhook trigger. Review the generated underwriting summary; handle only flagged exceptions (unknown/unreadable docs, low confidence). Setup steps Connect accounts Add credentials for OneDrive, OCR, and OpenAI. Configure inputs In Search a folder, point to your borrower docs (prefer folderId; otherwise tighten the name query). In Get items in a folder, enable pagination if the folder is large. In Split in Batches, set a conservative batch size to control costs. Wire the file path Download a file must receive the current fileā€™s id from the folder listing. Make sure the OCR node receives binary input (PDFs/images). Classification Update keyword rules to match your region/lenders/utilities/tax forms. Keep a fallback Unknown class and log it for review. Combine Replace the hard-coded BorrowerName with: a Set node field, a form input, or parsing from folder/file naming conventions. AI Agent Set your OpenAI model/credentials. Ask the model to output JSON first (structured fields) and Markdown second (readable summary). Keep temperature low for consistent, audit-friendly results. Optional outputs Persist JSON/Markdown to Notion/Docs/DB or write to storage. Customize if needed Doc types: add/remove categories and keywords without touching core logic. Error handling: add IF paths for empty folders, failed downloads, empty OCR, or Unknown class; retry transient API errors. Privacy: redact IDs/account numbers in logs; restrict execution visibility. Scale: add MIME/size filters, duplicate detection, and multi-borrower folder patterns (parent ā†’ subfolders).

Vinay GangidiBy Vinay Gangidi
471

Automate sales order prioritization with ERP-WMS-TMS integration based on SLA tiers

This n8n workflow automates the prioritization and scheduling of sales orders based on customer SLAs, urgency, and profitability. It ensures that high-priority and SLA-critical orders are picked, packed, and dispatched firstā€”improving fulfillment speed, customer satisfaction, and operational efficiency across warehouses and logistics. --- Key Features Automated Order Fetching: Periodically retrieves all pending or confirmed sales orders from ERP systems. Dynamic SLA-Based Prioritization: Calculates order priority scores using urgency, customer tier, order value, and profit margin. Intelligent SLA Monitoring: Identifies SLA breaches and automatically flags them for immediate handling. Automated Task Creation: Generates urgent picking tasks and alerts warehouse managers in real-time. Smart Scheduling: Optimizes picking and dispatch timelines based on urgency and capacity. Seamless ERP & TMS Integration: Updates order statuses and schedules dispatches automatically. Operational Transparency: Sends end-of-cycle summary reports via email to operations teams. --- Workflow Process Schedule Trigger Runs every 15 minutes to ensure orders are frequently evaluated. Maintains real-time responsiveness without overloading systems. Fetch Pending Orders Retrieves all orders in pending or confirmed state from ERP API. Configurable limit (e.g., 100 orders per run) for controlled processing. Fetch Customer SLA Data Collects SLA tiers, delivery timeframes, and customer-specific priorities from ERP or CRM API. Supports dynamic customer segmentation (Gold, Silver, Bronze tiers). Calculate Priority Scores Assigns weighted priority scores based on multiple criteria: Urgency: 40% Tier: 30% Order Value: 20% Profit Margin: 10% Produces a composite score used for sorting and scheduling. Check if SLA Critical Detects if any order is close to or past SLA deadlines. Routes SLA-breached orders for immediate escalation. Create Urgent Picking Task Generates warehouse picking tasks for critical orders. Assigns to senior pickers or rapid response teams. Alert Warehouse Manager Sends instant SMS and email alerts for SLA-critical or high-priority orders. Ensures immediate managerial attention. Batch Normal Orders Groups non-critical orders into batches of 10 for optimized processing. Reduces load on WMS while maintaining steady throughput. Generate Picking Schedule Creates smart picking schedules based on urgency: High Priority: Same-day Normal: Within 1 day Low: Within 2ā€“3 days Create Bulk Picking Tasks Pushes picking tasks into WMS (Warehouse Management System). Uses auto-assignment and route optimization logic. Generate Dispatch Schedule Builds dispatch timelines according to delivery method: Express, Priority, or Standard. Syncs with transport capacity data. Schedule Dispatches in TMS Sends dispatch requests to TMS (Transport Management System). Books carriers and reserves capacity for each batch. Update Order Statuses Updates ERP with new order statuses, schedules, and expected delivery dates. Maintains a unified view across systems. Generate Summary Report Creates a summary JSON report including: Total orders processed SLA-critical cases Dispatch breakdowns Next deadlines Send Summary Notification Emails the operations team with execution summary and performance metrics. Ensures team alignment and SLA visibility. --- Industries That Benefit This automation is especially valuable for: E-commerce & Retail: To prioritize same-day or express deliveries for VIP customers. Logistics & 3PL Providers: For meeting tight SLAs across multiple clients and delivery tiers. Manufacturing & B2B Distribution: Ensures high-value or contractual orders are prioritized. Pharma & Healthcare: Critical for time-sensitive and compliance-driven deliveries. Consumer Goods & FMCG: Helps manage high-volume dispatch with smart scheduling. --- Prerequisites ERP system with API access (e.g., SAP, Odoo, NetSuite). WMS and TMS integrations with order/task APIs. SMTP and SMS gateway credentials for notifications. n8n instance with HTTP, Function, Email, and Scheduler nodes installed. --- Modification Options Customize priority scoring weights per business type. Integrate AI for predictive SLA breach forecasting. Add Slack/Teams channels for real-time operational alerts. Implement escalation routing for unassigned urgent tasks. Extend reports to include OTIF (On-Time-In-Full) metrics. --- Explore More AI-Powered Workflows: Contact us for customized supply chain and order management automation.

Oneclick AI SquadBy Oneclick AI Squad
149

Fetch a YouTube playlist and send new items Raindrop

This simple workflow will fetch a YouTube playlist every n minutes and send the new items s to a collection in Raindrop. You can connect any application at the end of the flow. Make sure to authenticate to YouTube using Google Auth, and to Raindrop using an API. Update the Playlist ID and the Raindrop collection.

Alejandro ARBy Alejandro AR
3767