I’m currently evaluating using n8n.io within our freelancer network and our back office runs entirely on odoo (https://www.odoo.com/), an open source CRM and ERP. They got their source code on github and have got a pretty detailed developer documentation. Oddo is written in python.
Consequentially, I’d love to see an ODOO node in n8n - am open for any questions you might have!
Will add this to the backlog. Can you please let us know the use case you are interested in? So that when it gets created we make sure it has all you need.
Hi all! It really helps us when you can guide us on what the V1 functionality should be as usually there is a long tail of functionality that could be added to the node and we don’t usually have the domain insight that you might as a user of that tool.
Here are some great examples of this from @janbaykara:
Direct API functionality / endpoints from the API could definitely work as would the “jobs to be done” - so whichever is easiest for you. Very helpful context for these jobs/ endpoints would be typical options that are important to you - that might not be required for a basic operation but would be helpful most of the time.
For example in a CRM, adding or reading custom properties for a contact is usually important, but not required to make the call. Or if there is a “Get All” endpoint and you would typically require certain filters (like “Get all users who have past due charges”, if this were a payments app).
Odoo is an ERP CRM that does a lot of stuff… The API connections could be endless.
In a personal case, I’d want to connect Mautic to the CRM functionality of ODOO so that all leads generated in Mautic end up as ‘Cards’ in the CRM Leads section.
There seems to be strong interest from the community. Sadly, we are a small team with a lot of tasks. In the meantime, you can use the HTTP request. However, considering the number of votes, going to try to bump this up internally.