Tameson Odoo icon

Tameson Odoo

Consume Odoo API

Actions20

Overview

The Tameson Odoo node for n8n allows you to interact with the Odoo API, specifically targeting various resources such as Contacts.
For the Contact → Update operation, this node updates an existing contact in your Odoo system using the provided Contact ID and any fields you wish to modify (such as address, email, phone, etc.).

Common scenarios:

  • Keeping contact information up-to-date automatically from another system.
  • Bulk updating contacts based on changes in a CRM or ERP workflow.
  • Enriching contact data with additional details from external sources.

Example use case:
When a user's profile is updated in your web application, you can trigger this node to update the corresponding contact record in Odoo, ensuring both systems remain synchronized.

Properties

Name Type Meaning
Contact ID String The unique identifier of the contact to update. Required.
Update Fields Collection A set of fields to update for the contact. You can specify one or more of the following:
— Address FixedCollection Structured address information including City, Country, State, Street, Street 2, and Zip Code.
— Email String The contact's email address.
— Internal Notes String Any internal notes or comments about the contact.
— Job Position String The job position or function of the contact.
— Mobile String The contact's mobile phone number.
— Name String The full name of the contact.
— Phone String The contact's main phone number.
— Tax ID String The contact's VAT or tax identification number.
— Website String The contact's website URL.

Output

  • The output will be a JSON object representing the updated contact as returned by the Odoo API.
  • The structure of the output JSON depends on the fields present in the Odoo contact model and the fields you requested to update.
  • If the update is successful, the output contains the updated contact data.
  • In case of error (and if "Continue On Fail" is enabled), the output will include an error field with the error message.

Example output:

{
  "id": 123,
  "name": "John Doe",
  "email": "john.doe@example.com",
  "phone": "+1234567890",
  "address": {
    "city": "Amsterdam",
    "country_id": 21,
    "state_id": 5,
    "street": "Main St 1",
    "zip": "1000AA"
  },
  ...
}

Dependencies

  • Odoo API: Requires access to an Odoo instance with valid credentials (URL, username, password, and database name).
  • n8n Credentials: You must configure Odoo API credentials in n8n under the name odooApi.

Troubleshooting

Common issues:

  • Invalid Credentials: If the Odoo credentials are incorrect, the node will return an authentication error.
  • Missing Contact ID: The operation requires a valid Contact ID; missing or invalid IDs will result in errors.
  • Field Validation Errors: If you provide invalid values for certain fields (e.g., non-existent country/state IDs), Odoo may reject the update.
  • API Connectivity Issues: Network problems or incorrect Odoo URL can cause connection failures.

Error messages and resolutions:

  • "Credentials are not valid": Double-check your Odoo API credentials in n8n.
  • "Settings are not valid: ...": Review the configuration, especially the Odoo URL and database name.
  • "Record not found" or similar: Ensure the Contact ID exists in your Odoo instance.
  • "Field ... does not exist": Check that the field names and values match those expected by your Odoo setup.

Links and References

Discussion