Odoo Integration

​

Setup

1. Go to Project Settings → Project Integrations
2. Select Odoo from the list
3. Enter your Odoo credentials:
   • Odoo Instance URL - Your Odoo instance URL (e.g., https://your-instance.odoo.com)
   • Database Name - Your Odoo database name
   • Username - Your Odoo username
   • Password/API Key - Your Odoo password or API key
   • User ID (UID) - Click “Authenticate” to automatically get your UID
4. Test the connection
5. Start using Odoo in your prompts

​

How It Works

​

HelloLeo Middleware

​

How It Works

1. Frontend makes request - Your HelloLeo-generated frontend sends API requests to the HelloLeo Middleware
2. Middleware forwards request - The middleware forwards the request to Odoo using your stored API credentials
3. Odoo responds - Odoo processes the request and sends a response back through the middleware
4. Frontend receives data - The response is returned to your frontend application

​

Benefits

• No CORS Issues - Requests work immediately without CORS configuration. The middleware handles all cross-origin requests seamlessly.
• Secure API Keys - Your Odoo API keys are encrypted and stored securely on the backend. They’re never exposed to the frontend or end users.
• Automatic Authentication - The middleware automatically includes your Odoo credentials in every request, so you don’t need to manage authentication in your frontend code.
• Permission Management - (Coming soon) You’ll be able to manage permissions and access control through the middleware, giving you fine-grained control over what data each user can access.

​

Technical Details

• Encrypts and stores your Odoo credentials securely
• Handles Odoo’s JSON-RPC protocol automatically
• Manages session authentication and MFA
• Provides a consistent API interface for your frontend
• Logs all requests for debugging (visible in Network Monitor)

​

MCP Operations

​

execute_method

• model (required): The Odoo model name (e.g., 'res.partner', 'sale.order', 'product.product')
• method (required): The method name to execute (e.g., 'search', 'read', 'create', 'write', 'unlink', 'search_read', 'search_count')
• args (optional): List of positional arguments
• kwargs (optional): Dictionary of keyword arguments

• success: Boolean indicating success/failure
• result: The method result (if successful)
• error: Error message (if failed)

• Domain normalization for search methods (search, search_count, 'search_read')
• Supports multiple domain formats (lists, dictionaries with conditions, JSON strings)
• Handles Odoo domain operators (&, |, !)

​

Common Methods

​

Search Records

• search: Find records by domain
• search_read: Search and read in one call
• search_count: Count records matching domain

​

Read Records

• read: Get record details by IDs

​

Create Records

• create: Create new records

​

Update Records

• write: Update existing records

​

Delete Records

• unlink: Delete records

​

Custom Methods

• Any custom method defined on the model

​

Example Usage

​

Search and Display Products

Show all products from Odoo where quantity is greater than 0. 
Display product name, price, and available quantity.

​

Create a Customer

Create a new customer in Odoo with name "Acme Corp", 
email "contact@acme.com", and phone "555-1234".

​

Update an Order

Update order SO001 in Odoo to set the status to "confirmed".

​

Search Partners

Find all companies in Odoo and show their name, email, and phone.

​

Example MCP Command

mcp odoo execute_method {"model":"res.partner","method":"search_read","args":[[["is_company","=",true]]],"kwargs":{"fields":["name","email","phone"]}}

​

Authentication

​

Admin Authentication (Setup)

​

Portal User Authentication

​

How Portal Authentication Works

1. Portal User Login - End users log in using their Odoo portal credentials (email/password) through your HelloLeo-generated frontend
2. Session Creation - The frontend authenticates with Odoo’s /web/session/authenticate endpoint through the HelloLeo Middleware
3. Session Management - Odoo returns a session ID that identifies the portal user
4. Data Access - All subsequent API requests use this session to access data according to the portal user’s permissions in Odoo

​

Implementing Portal Authentication

Create a login page where portal users can authenticate with their 
Odoo credentials. After login, store the session and use it for 
all Odoo API calls. Show only data the portal user has access to 
based on their Odoo permissions.

​

Portal User Permissions

• Record Rules - Odoo’s record-level security rules
• Access Rights - Model-level read/write permissions
• Portal Groups - Portal user group membership

​

Security Considerations

• Portal users authenticate directly with Odoo, not with HelloLeo
• Session data is managed securely through the middleware
• All Odoo security rules and permissions are enforced
• API keys used by the middleware are separate from portal user sessions

​

Best Practices

• Be specific about models - Always mention which Odoo model you’re working with (e.g., “products”, “customers”, “orders”)
• Specify fields - Tell Leo which fields to display or update
• Use domain filters - Describe what records you want to find (e.g., “active products”, “confirmed orders”)
• Mention the integration - Always say “from Odoo” or “to Odoo” so Leo knows which integration to use

​

Troubleshooting

​

Authentication Issues

• Check credentials - Verify your URL, database name, username, and password are correct
• MFA enabled - If MFA is enabled, make sure to complete the MFA verification
• UID missing - Click “Authenticate” to get your User ID

​

Data Not Showing

• Check model name - Ensure you’re using the correct Odoo model name
• Verify permissions - Make sure your user has access to the model and records
• Check domain - Review your search criteria