​

Odoo

With the Odoo integration, your ChatNorris agent works with the real data in your Odoo ERP (self-hosted, Odoo.sh or Online). Depending on what you turn on and the modules your instance has, the agent:

• creates a contact and an opportunity in your Odoo CRM for each new lead it confirms;
• tells the status of a sales order, only after verifying that it belongs to the visitor;
• searches products and variants and answers the current sales price and stock;
• builds a shopping list with the visitor and sends them the link to each product in your store;
• creates tickets in your Odoo Helpdesk, with the visitor’s confirmation, and looks up their status in a verified way.

It works in the web widget, WhatsApp, Instagram, Messenger, Telegram, Email, and the API.

​

Requirements

• A ChatNorris account on the Premium plan. Odoo is exclusive to Premium: on Free or Standard it doesn’t appear as connectable and the Action appears locked as “Coming soon” in the picker. You can see the plans at chatnorris.ai/pricing or write to us at hola@chatnorris.ai.
• At least one agent created in ChatNorris. If you don’t have one yet, follow Create an agent.
• An Odoo instance (self-hosted, Odoo.sh or Online), an Odoo user, and an API key for that user.
• The Odoo modules each capability needs (see Configure the Action).
• The Owner or Admin role in your ChatNorris organization.

​

Connect Odoo

Each agent connects to one Odoo instance. You connect it only once in Integrations, and the Odoo Action uses that connection. The API key is stored encrypted: the hub only shows its last 4 characters. If you rotate it in Odoo, use Replace key in the row’s ··· menu; the connection stays the same, so the Action is not affected.

​

Configure the Action

Connecting Odoo doesn’t turn anything on yet. To choose what the agent does: If your instance doesn’t have the corresponding module installed, that capability appears disabled.

​

Sync leads to Odoo CRM

When the agent confirms a new lead in the conversation, a contact and an opportunity are also created in your Odoo CRM (crm.lead). It’s automatic: it doesn’t depend on what the visitor says.

​

Check order status

The visitor checks the status of a sales order by giving the order number and the email or phone they used for the purchase. The agent answers with the order’s status, total and products. In the web widget, when the agent detects that the visitor wants an order’s status, it shows an embedded form inside the chat with two fields — Order number and Email or phone used for the purchase. The form and the answer are shown in the widget’s language (Spanish, English, or Portuguese), and it’s the same for WooCommerce and Odoo. While the form is pending, the visitor can’t write another message until they fill it in or cancel it. In WhatsApp and Instagram (where there are no embedded forms), the agent asks for these same details conversationally. To protect your customers’ data:

• if the details don’t match, the agent says it couldn’t verify the order and asks the visitor to check the number and the contact detail — it never shows unverified information;
• an order that doesn’t exist and a detail that doesn’t match get the same answer, so no one can guess order numbers;
• after 5 failed attempts in the same conversation, order lookup is blocked.

​

Check stock and price

The agent searches products and variants in your Odoo and answers with the current sales price and stock. It queries Odoo every time it’s about to talk about a product’s price or stock, even if it already looked it up earlier in the conversation: it never answers with data from the knowledge base. If the visitor asks for a recommendation without naming a product (“what do you recommend for 5 people?”), the agent queries the live catalog and suggests one or two specific options with their price, avoiding those that are out of stock. With this capability on, the Knowledge Base source list also shows the informational row Live Odoo catalog, with the Live label and the View action link. It isn’t a source: it indicates that the agent checks price and stock directly in your Odoo in every conversation, so it doesn’t use characters or need syncing.

​

Build a purchase

With Build a purchase on, when the visitor wants to buy they receive a 🛒 block with each line (quantity × product = amount), a 🔗 link to each product’s page in your store, and a reference Total ≈, without shipping. Before sending it, the agent reviews the list: it removes products that are no longer sold, updates prices, and flags those that are out of stock. If a product has no page in your store, the agent tells the visitor to search for it by name. ChatNorris doesn’t create orders or charge: your store handles the final total, shipping and payment. Cart changes are recorded as internal notes in the conversation.

​

Create support ticket

The visitor can ask for help and, after confirming, a ticket is created in the Odoo Helpdesk (the official Enterprise one or the OCA community one, depending on what your instance has installed). Before creating it, the agent gathers the visitor’s subject, description, name and email, shows them a summary, and waits for an explicit “yes”.

• Assigned team: choose which Helpdesk team new tickets are assigned to. With Automatic (first available team), the first team your Odoo returns is used.
• When to create a ticket: instructions for the agent about when to offer support via ticket. It comes with default text that you can edit; Restore default text brings it back.

Ticket actions (Odoo, Zendesk and Freshdesk) follow a fixed rule, above whatever you write in When to create a ticket:

• If the visitor describes a problem or asks a question without asking for a ticket, the agent answers with the knowledge base. If it can’t solve it, or the visitor says the answer didn’t help, it offers to create the ticket.
• If the visitor asks for a ticket directly, the agent first offers help (with the answer, if it has one, or by asking what’s going on) and asks whether they still prefer the ticket.
• The ticket is started if the visitor insists, if the agent already tried and didn’t have the information, or if the answer didn’t help.

During a ticket flow, the agent doesn’t offer the Lead Form or a transfer to a person, so as not to confuse the visitor. And if the visitor asks to open a ticket or a support case, the agent uses this action instead of transferring to a person with Human Handoff.

​

Check ticket status

The visitor can check the status of a ticket already created by this agent, by giving the ticket number and the email they used when creating it. The agent only reports on tickets it created itself, not any ticket in your Helpdesk. Checking the status of an existing ticket doesn’t go through the “resolve first” rule.

​

Credits

Connecting and testing Odoo doesn’t use credits. Each agent response that queries your Odoo live (orders, or price and stock) adds 0.5 AI credit to the response’s normal cost, only once per response. Tests in the Playground don’t add this charge. See AI models and credits.

​

Pause or disconnect

• Pause: turn off the Active switch on the Odoo row in Integrations. The API key is kept, but the Action can’t call your Odoo until you reactivate it.
• Disconnect: from the ··· menu or the Odoo detail, click Disconnect. The Odoo Action is turned off, but its configuration is kept, and the API key is deleted from ChatNorris.

To use the Action again, connect Odoo again and reactivate it. What was already created in Odoo (contacts, opportunities and tickets) stays in your instance. If you’re no longer going to use the API key, delete it in Preferences → Account Security of your Odoo user.

​

Frequently asked questions