AI agents

Connecting Odoo to an AI agent, without handing it the keys

An AI agent can answer questions from your live Odoo data, draft invoices and replies, and chase overdue work. The question every owner asks is what stops it from doing something wrong. The answer is to build the agent inside Odoo's own security, not around it.

How we connect Odoo to an agent

No.PointWhat it means in practice

01Its own loginThe agent gets its own Odoo user with an API key, never an admin password. Odoo's normal access rules decide what it can read and write.

02Odoo's APIThe agent talks to Odoo through its official API (JSON-2 in Odoo 19, JSON-RPC and XML-RPC in older versions), the same way any integration does.

03Approval queueAnything that changes data, such as a draft invoice, an email or a status change, waits for a person to approve it.

04Consent and scopeRecords can be marked as inside or outside the agent's reach, for example only clients who have agreed in writing.

05Where staff talk to itInside Odoo Discuss, so staff message the agent like a colleague and the conversation stays in Odoo.

06Log of everythingEvery question, every tool the agent used and every answer is recorded for review.

What it is good for

Answering "who owes us the most and since when?" from live data. Drafting reminder emails for overdue invoices. Summarising a client's file before a meeting. Preparing a first draft of a job, a quote or a reply for a person to finish.

We built exactly this for a chartered accountancy firm: see the case study.

Questions people ask

Which AI does it use?

We usually use Claude through the Anthropic API, on your own account so the data and the bill are yours. The same design works with other models.

Does it work with Odoo Community?

Yes. The firm in our case study runs Odoo 19 Community.

Can the agent make mistakes in our books?

It cannot post anything on its own. Every change it drafts waits in the approval queue.