Odoo native node was working perfectly fine until two new versions of n8n launched. With the latest version, odoo node is giving server error in loading options. I have attached a screenshot for reference. Kindly look into this.
Which n8n version were you on before, and which one are you on now? That way we can narrow down exactly which release broke it. If you can, check your Odoo server logs too as they’ll show the real error that n8n is swallowing.
we are on 2.12.3 right now and exact error is :error is : "Issues:
There was a problem loading the parameter options from server: “[object Object]” " in odoo native node.
it was working fine in the version with no auto save and no publish , it has toggle active/inactive button.
The version with the active/inactive toggle is n8n 1.x. Going from 1.x to 2.12.3 is a major version jump with significant internal changes, not just two minor updates. That’s likely why the Odoo node broke.
Try this first: go to Settings > Credentials, open your Odoo credential, and hit Save without changing anything. After the 1.x to 2.x migration, credentials sometimes need to be re-saved to work properly with the new internal format.
If that doesn’t fix it, check what Odoo is actually returning. Run this from your server:
docker logs <your-odoo-container-name> --tail 100
Replace <your-odoo-container-name> with the name of your Odoo container (you can find it with docker ps). The real error will be there, the “[object Object]” on n8n’s side is just hiding it.
As a workaround, you can replace the Odoo node with an HTTP Request node using JSON-RPC directly. This bypasses the native node’s parameter loading entirely and is actually how several users work around known Odoo node limitations.
just to add: the ‘loading parameter options’ error is about the node UI fetching available fields from Odoo, not the execution itself. so even if the credentials are fine, this specific dropdown error can persist in 2.x if the field-fetch endpoint changed. the http request + json-rpc workaround houda mentioned actually sidesteps this entirely. worth trying if re-saving doesnt fix it
