This guide explains what Odoo 20 ERP Automation means for the way your business runs each day. For years, automation in Odoo meant simple rules that sent an email, assigned a user or created an activity when a field changed. The new release adds three mechanisms on top of that foundation. AI agents can now act inside workflows, MCP lets outside AI assistants work with your Odoo data, and marketing journeys are built on a redesigned visual flow. Below you will find what each one does, where human review still matters, and how to tell if you are ready.
Key Takeaways
- Rules still do most of the work. Odoo 20 adds agents that read context and propose or make changes, started by the same rules
- MCP lets external AI assistants connect to Odoo through scoped keys or OAuth, with the same access rights as the user they act for
- Agent writes pass through a confirmation step, but approvals, audit and data quality remain your responsibility
- AI automation runs on IAP credits, so treat it as an operating cost and start with one measurable process
Table of Contents
- What Changes in Odoo 20 ERP Automation
- How Odoo 20 ERP Automation Uses AI Agents
- MCP and Connecting Odoo to External AI
- Odoo 20 ERP Automation by Module
- Visual Marketing Automation Journeys
- What Changes for Admins and Developers
- Where Automation Needs Human Review
- A Readiness Checklist for Odoo 20 ERP Automation
- Automate Now or Wait for Odoo 20
- FAQs
What Changes in Odoo 20 ERP Automation
Odoo 20 keeps rules and scheduled actions as the foundation and adds a reasoning layer on top. For every feature difference between the two releases, read the Odoo 19 vs Odoo 20 comparison.
| Automation Layer | Earlier Releases | Odoo 20 |
|---|---|---|
| Rules and scheduled actions | Trigger emails, activities and field updates | The same rules can now start AI agents |
| AI inside records | First agents, search in plain language and drafting help | Agents create and update records and use files and reusable skills |
| External AI | Custom API integrations built case by case | A standard MCP connection with scoped access |
| Marketing | A workflow of activities and triggers | A redesigned flow view, dynamic lists and AI drafted campaigns |
The shift is from "if this, then that" to "if this, then think". Rules still decide when something happens. Agents decide what the right next step looks like, within limits you set.
How Odoo 20 ERP Automation Uses AI Agents
An agent is not a chat window that waits for someone to type. In Odoo 20 ERP Automation, an agent is a configured worker that a rule can call at the right moment in a process.
How an Agent Is Put Together
- Instructions. Guidance in plain language that describes the job, the tone and the limits.
- Skills. Reusable sets of instructions and tools that define what the agent can do, such as drafting a reply or updating a field.
- Knowledge sources. Documents and records the agent can draw on, such as policies, price lists or past tickets.
- Triggers. Automation rules and scheduled actions that start the agent, so it runs as part of a process rather than waiting to be asked.
What That Looks Like in Practice
- A new support ticket arrives, and an agent sets its priority and drafts a first reply for the team to review.
- Every Monday, a scheduled agent summarises last week's lost deals for the sales manager.
- A user uploads a supplier instruction file as a PDF and asks the agent to create the matching records.
Choosing Your First Agent
- Pick a task people already dislike. Ticket triage, weekly summaries and data entry from documents have clear inputs and outputs.
- Keep the scope narrow. One agent, one job and one trigger.
- Write instructions like a handover note. State what good output looks like, what the agent must never do, and when it should stop and ask a person.
- Measure for a month. Compare time saved and corrections needed against the credits used before adding a second agent.
Every agent run consumes credits. AI features run on IAP credits. Estimate how often each rule will start an agent before you activate it.
MCP and Connecting Odoo to External AI
MCP widens Odoo 20 ERP Automation beyond the Odoo screen, because assistants your team already uses can now read and act on Odoo data.
- What MCP is. The Model Context Protocol is an open standard that lets AI assistants call external tools. Odoo 20 exposes its tool layer through MCP.
- Why it matters. Teams that already use an external AI assistant can connect it to Odoo data without building a custom API bridge for every use case.
- How access works. Connections use API keys scoped for MCP or an OAuth flow for registered clients.
- Same rules as a user. An external assistant gets the access rights of the user it acts for, and its changes go through the same confirmation step.
Treat MCP as an Access Decision First
- Decide which users may connect an external assistant, and which may not.
- Use dedicated users with narrow rights for automated connections, never an administrator account.
- Check where the external assistant stores conversation data and whether that fits your data policies.
- Rotate and revoke keys as you would any other integration credential.
Odoo 20 ERP Automation by Module
- Accounting. A tax return flow with automated checks, an agent that reviews the ledger the way an auditor would, and reconciliation matching rules with tolerances. Changes for India are covered in our guide to the Odoo 20 accounting module.
- Helpdesk. Search for similar tickets, drafted answers, automatic closing reminders and SLA conditions reduce manual triage.
- Sales, Purchase, Inventory and Project. AI prompts inside records help users draft, summarise and update without leaving the screen.
- HR and Timesheets. A timesheet assistant proposes entries from calendar, browser activity and email.
Start where volume is high and rules are clear. Ticket triage, bill sorting and reconciliation suggestions are repetitive, easy to check, and show results within weeks.
Visual Marketing Automation Journeys
From Sequences to Journeys
- Linear sequences send the same message to everyone. A welcome email, then a reminder, then an offer, on a fixed timetable.
- Journeys branch on behaviour. A contact who opens and clicks takes one path. A contact who ignores the message takes another. Buyers leave the flow automatically.
- A redesigned flow view. Odoo 20 redesigns the Marketing Automation flow view, which makes branching campaigns easier to build and read.
- An AI campaign assistant. Describe the goal, and the assistant drafts a flow you can then review and adjust.
A drafted flow is a starting point, not a campaign. Check every branch, delay, exit condition and message before launch, and confirm consent and unsubscribe handling for every audience.
What Changes for Admins and Developers
Admin Responsibilities Grow
- Agent governance. Someone must own agent instructions, skills, knowledge sources and the rules that start them.
- Credit budgets. Monitor IAP credit consumption by agent and by department.
- Activity review. Read automation chats to see how agents handled a task, and adjust instructions where results drift.
Developer Changes That Affect Automation
- Access rights. The way record access is defined changes in this release. Since agents act with user permissions, getting access right matters more than before.
- Field tracking. Changes to how tracked values are stored mean any server action or report that reads old tracking data needs testing and possibly a rewrite.
- Custom server actions. Actions written in Python and custom modules need porting and testing, so budget developer time where logic is complex.
- Configuration first. Many automations that once needed code can now be built through settings or Odoo Studio without a developer.
Where Automation Needs Human Review
Odoo 20 ERP Automation can draft, sort and suggest at speed, but some decisions still need a person who is accountable for the outcome.
Keep a Person in the Loop for These
- Financial postings. Journal entries, tax returns, payments and write offs should be reviewed before posting, whatever an agent suggests.
- Pricing and discounts. Changes to price lists, margins or terms for individual customers need a named approver.
- Messages to customers. Drafted replies and campaigns should be reviewed until the agent has a track record on that task.
- HR and payroll. Salary changes, attendance corrections and offboarding affect people directly and carry legal risk.
Set Review Levels by Risk
- Low risk, applied automatically. Tagging, sorting, internal summaries and activity reminders.
- Medium risk, confirmed before saving. Record updates, drafted customer replies and ticket priorities.
- High risk, signed off by a named approver. Anything that posts money, changes prices or affects pay.
Use the confirmation step on purpose. Agent writes go through a confirmation card. Make sure the person confirming understands what they approve.
A Readiness Checklist for Odoo 20 ERP Automation
| Check | Ready When | Not Ready When |
|---|---|---|
| Process clarity | Steps, owners and outcomes are written down | Each person does it differently |
| Data quality | Clean products, partners and accounts | Duplicates and missing fields |
| Access rights | Roles reviewed and least privilege applied | Many users with admin rights |
| Approvals | Named approvers for sensitive steps | No one owns the final check |
| Credit budget | Expected volume estimated and funded | No idea how often agents will run |
| External apps | Vetted and compatible with Odoo 20 | Unknown apps touching the same records |
External apps and automation can collide. An app that writes to the same records as an agent can produce loops or conflicting changes. Before you activate agents, check whether your third party Odoo apps are safe to keep.
Automate Now or Wait for Odoo 20
Do These Now, on Any Version
- Document processes and clean master data. Every future automation depends on both.
- Automate clear steps with automation rules and scheduled actions, which carry forward to Odoo 20 after testing.
- Review access rights and remove unnecessary administrator accounts.
Wait Until You Are on Odoo 20
- AI agents that act inside workflows, since they depend on the new release.
- MCP connections to external AI assistants.
- Marketing journeys built on the redesigned flow view.
- Complex custom automation, which would otherwise be built twice. Use a clear plan to migrate to Odoo 20 before you invest in it.
Prefer configuration over code. Standard rules and light customisation survive upgrades far better than heavy custom logic. Our Odoo consulting services help you rank which processes to automate first and which to leave alone.
Odoo 20 Automation
Want Automation That Saves Time Without Creating New Risks?
Tatvamasi Labs maps your processes, cleans the data underneath them, and sets up automation rules, AI agents and approvals that your team can trust and measure.
Get an Automation Readiness Review →Frequently Asked Questions
Odoo 20 ERP Automation lets AI agents work inside business workflows, started by the same automation rules and scheduled actions teams already use. It adds an MCP connection so external AI assistants can work with Odoo data, and it redesigns the Marketing Automation flow view.
MCP stands for Model Context Protocol. It is an open standard that lets AI assistants call external tools. In Odoo 20 it lets an outside assistant connect to your database through scoped API keys or OAuth, with the same access rights as the user it acts for.
Agent changes pass through a confirmation step before records are written, and agents respect the access rights of the user they act for. You should still name human approvers for sensitive processes.
Standard automation rules and scheduled actions do not use credits. AI features, including agents, run on credits bought through In App Purchase (IAP), so AI automation carries an ongoing usage cost.
Not for most needs. Automation rules, scheduled actions, Marketing Automation flows and agent instructions are set up through configuration. Developers are still needed for complex logic and integrations.
Most configured rules carry over, but each one should be tested on a copy of your database. Changes to access rights and field tracking can affect older server actions.
Fix process clarity and data quality now, and automate simple rule based tasks on your current version. Hold AI agent and MCP projects until you are on Odoo 20, because those capabilities depend on the new release.
Prefer a quick chat? Talk to Tatvamasi Labs about automating your workflows in Odoo 20.
CHAT ON WHATSAPP
