Odoo Node still uses deprecated RPC endpoints (Odoo 19+)

[Mika9999]

Bug Description

I’m currently using n8n v1.118.1 with Odoo 19.0 in a local Docker setup. Everything technically works, but Odoo now throws the following warning every time the node runs:

odoo.addons.rpc.controllers.jsonrpc: The /xmlrpc, /xmlrpc/2 and /jsonrpc endpoints are deprecated in Odoo 19 and scheduled for removal in Odoo 20. Please report the problem to the client making the request.
Mute this logger: --log-handler odoo.addons.rpc.controllers.jsonrpc:ERROR

Basically, the Odoo node in n8n is still using the old XML-RPC/JSON-RPC API, which has now been deprecated. Starting with Odoo 19, they’ve introduced a new JSON-2 API, and the old endpoints are planned to be removed completely in Odoo 20.

Official Odoo docs on this change:
https://www.odoo.com/documentation/latest/developer/reference/external_api.html#migrating-from-xml-rpc-json-rpc

Would love to see this updated before Odoo 20 comes out to keep compatibility intact 🙏

To Reproduce

1. Run Odoo 19 and n8n 1.118.1 in Docker.
2. Add any Odoo node (e.g., “Find Record” or “Create Record”).
3. Execute the workflow.
4. Check the Odoo logs — you’ll see the deprecation warning above.

Expected behavior

The Odoo node should communicate with Odoo using the new JSON-2 API to avoid future compatibility issues.

Debug Info

The node still uses the deprecated RPC endpoints (/xmlrpc, /xmlrpc/2, /jsonrpc), which will stop working entirely once Odoo 20 is released:

odoo.addons.rpc.controllers.jsonrpc: The /xmlrpc, /xmlrpc/2 and /jsonrpc endpoints are deprecated in Odoo 19 and scheduled for removal in Odoo 20. Please report the problem to the client making the request.
Mute this logger: --log-handler odoo.addons.rpc.controllers.jsonrpc:ERROR

Operating System

Debian 12.12

n8n Version

1.118.1

Node.js Version

10.9.4

Database

SQLite (default)

Execution mode

main (default)

Hosting

self hosted

[n8n-assistant]

Hey @Mika9999,

Thank you for reaching out! We’ve received your issue and are looking into it. To help us track this internally, we’ve created a Linear ticket with the reference: "GHC-5349".

We’ll keep you updated as we make progress, but if you have any additional details or context to share, feel free to add them here - it’s always helpful!

Thanks for your patience and for bringing this to our attention.

---

For INTERNAL use only: GHC-5349

[n8n-assistant]

Hi @Mika9999 👋

Thanks so much for your patience while we’ve been improving n8n. We know it’s taken some time to review this issue, and we’re currently updating our triage process to better keep up with our growth.

There have been a lot of improvements in recent releases, so we’d really appreciate it if you could check whether this issue still occurs in the latest release.

When you have a moment, please copy and paste the checklist below as a comment so our system can update the status automatically:

[ ] I have updated to the latest stable version of n8n [please specify version number] and I am still experiencing this issue
[ ] Please close this issue – I am no longer experiencing it
[ ] Please close this issue – [please specify a reason]

If we don’t hear from you in the next 14 days this issue will be automatically closed, feel free to reopen - don’t forget to add the checklist above so that our automated systems notify us of the issue.

Thanks again for helping us keep n8n healthy and up-to-date 💚

[Mika9999]

[ x ] I have updated to the latest stable version of n8n 1.122.5 and I am still experiencing this issue
[ ] Please close this issue – I am no longer experiencing it
[ ] Please close this issue – [please specify a reason]

[chrisandrewmann]

I'd like to add my own thoughts on this @Mika9999
I agree that n8n should be updated to utilise the new JSON-2 API for versions of Odoo 19.0 or above.
However, there should be a mechanism to fall back to the existing (legacy) API for the multitude of users who will remain on versions prior to V19. Currently this makes up the majority and there will always be those on older releases which shouldn't be ignored.
Maybe a configurable switch in the node to set the Odoo version?

[codeagencybe]

I'd like to add my own thoughts on this @Mika9999
I agree that n8n should be updated to utilise the new JSON-2 API for versions of Odoo 19.0 or above.
However, there should be a mechanism to fall back to the existing (legacy) API for the multitude of users who will remain on versions prior to V19. Currently this makes up the majority and there will always be those on older releases which shouldn't be ignored.
Maybe a configurable switch in the node to set the Odoo version?

I agree with this. There are plenty of users still running odoo versions 15.0-18.0 as well. Maybe a new node version would be best for v19.0 and newer and rename the current one as "legacy" or something. I believe this is also how zapier handles it with a also a variation for *.odoo.com saas databases and another one for self hosters.

[tamy-commits]

#triage:in-progress

[tamy-commits]

Hi @Mika9999 !

I'm here to help you.
Are you still experiencing the issue on the latest stable version? If so, please share your compose file (with any sensitive keys or passwords redacted) and the workflow JSON so we can take a closer look.
Thanks :)

#triage:needs-info