Skip to Content
This question has been flagged
2 Replies
120 Views
Avatar
Anisha

While trying to create or update a custom resource (such as a lead), the node does not seem to load all the available fields properly and showing server issue "Issues:

  • There was a problem loading the parameter options from server: "[object Object]" "

Because of this, some required fields are missing from the configuration, which is impacting the workflow execution.

I have already verified the connection credentials, base URL, and overall configuration, and everything appears to be set up correctly from my end. 

Avatar
Discard
Kunjan Patel

Hello, Yes, it's an n8n version regression bug - not your fault. Fix options:
- Downgrade n8n to your last working version
- Use the HTTP Request node with /jsonrpc as a workaround
- Report/upvote the bug on n8n GitHub issues Your config is fine. Wait for n8n to patch it, or downgrade.

Avatar
Anisha
Author Best Answer

The configuration I made in odoo native node was working absolutely fine until n8n was not updated, with the recent two versions of n8n, it is giving this server issue. 

I am using api key only instead of password and no trailing slash to setup the connection and it's successful.

Is this any version compatibility issue? 

Avatar
Discard
Avatar
Kunjan Patel
Best Answer
Hello Anisha,
I hope you are doing well

The error [object Object] in n8n's Odoo node means the API call to fetch fields is failing. Most likely causes:
1. Wrong model name - Use the exact technical name like crm.lead, not "Leads"
2. Insufficient permissions - The API user needs read access to the model
3. URL issue - No trailing slash, correct https://, no proxy blocking /xmlrpc/
4. Use API Key (Odoo 14+) instead of password

Workaround: Skip the native Odoo node and use n8n's HTTP Request node with Odoo's JSON-RPC endpoint (/jsonrpc) instead - it's more reliable.

I hope this information helps you

Thanks & Regards,
Kunjan Patel
Avatar
Discard