Odoo node - bug on Get Many for contacts?

Describe the problem/error/question

I’m creating a workflow to look for contacts and if they don’t exist, create them.
My contacts are B2B: I want to create A/ a company and then B/ a contact within that company.

So the workflow is:

  • A node to lookup for a company
  • If data was found, continue
  • If data was not found, create the company

And of course, same process for contacts.

I’m stuck at the contact lookup step.
I want to query my contact list to find a non-company contact based on an email.

What is the error message (if any)?

No error appears.

Please share your workflow

Share the output returned by the last node

So this is the weird part.
My node is configured to always output data (otherwise it would stop execution).

1/ If I run the node to lookup for an email I know exists, data is properly returned:

2/ But if I lookup an email I know does not exist and test the step, the node executes but nothing is returned despite my config!

3/ Even weirder: now when I go back to an email I know exists (same setup as 1), nothing is returned again (same output as 2). Even using query conditions that I know for a fact yield an output. Every test of the node fails without output.

4/ And, weirderer: this lasts until I refresh my browser page. Then I can go back to testing the node to query a contact I know exists.

My initial foray was into looking up contacts that are not companies but individuals. My tests lead me to fear that the node itself is buggy in test mode and that I can’t actually configure it.

Oddly enough, the very same setup works fine for companies (targeting the Odoo table Companies):

Did I misconfigure something? Or is there something wrong in n8n/Odoo?

Information on your n8n setup

  • n8n version: 1.76.1
  • Running n8n via (Docker, npm, n8n cloud, desktop app): n8n cloud
  • Operating system: Browser is Edge on Windows.

It looks like your topic is missing some important information. Could you provide the following if applicable.

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:

No idea what the DB or PATH var values are.

Hi @Kyll,

I’m trying to reproduce your use case and I’m also not being able to receive the correct contact information systematically. The return changes with nearly every execution.

I’m going to dig a little deeper and check internally for similar reports and get back to you once I know more.

Thanks for bringing this up!

2 Likes

Thanks @mariana-na !
At least now it’s certain I wasn’t going insane when trying this out :slight_smile:

1 Like

Hi @mariana-na,

It seems patch 1.82 fixed the odd behaviour I was noticing. Thank you!

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.