Tameson Odoo icon

Tameson Odoo

Consume Odoo API
Join our community

Actions20

Overview

The Tameson Odoo node for n8n allows you to interact with the Odoo API, specifically targeting the "Opportunity" resource. The Update operation enables users to modify existing opportunity records in their Odoo system. This is useful for automating sales pipeline management, updating deal information, or synchronizing data between Odoo and other platforms.

Practical examples:

  • Automatically update the probability or expected revenue of an opportunity when a related event occurs in another system.
  • Change the priority or add internal notes to opportunities based on workflow triggers.
  • Update contact details (email, phone) for opportunities as part of a CRM integration.

Properties

Name Type Meaning
Opportunity ID String The unique identifier of the opportunity record to update.
Update Fields Collection A set of fields to update on the opportunity. Each field below can be included as needed:
└ Email String The email address associated with the opportunity.
└ Expected Revenue Number The anticipated revenue from this opportunity.
└ Internal Notes String Additional notes or comments about the opportunity.
└ Name String The name/title of the opportunity.
└ Phone String The phone number linked to the opportunity.
└ Priority Options The priority level of the opportunity (1, 2, or 3).
└ Probability Number The likelihood of closing the opportunity (0–100%).

Output

The node returns a JSON object representing the updated opportunity record. The structure typically includes all standard Odoo opportunity fields, plus any custom fields present in your Odoo instance. The output will reflect the new values after the update.

Example output:

{
  "id": 123,
  "name": "Updated Opportunity",
  "email_from": "contact@example.com",
  "expected_revenue": 5000,
  "description": "Internal note here",
  "phone": "+123456789",
  "priority": "2",
  "probability": 75,
  ...
}

Note: The actual fields returned depend on your Odoo configuration and the fields you choose to update.

Dependencies

  • Odoo API: Requires access to an Odoo server with API enabled.
  • Credentials: You must configure Odoo API credentials (url, username, password, and optionally db) in n8n.
  • n8n Configuration: The node requires the odooApi credential type to be set up and tested.

Troubleshooting

Common issues:

  • Invalid Credentials: If the Odoo API credentials are incorrect, the node will return an authentication error. Double-check your username, password, URL, and database name.
  • Missing Opportunity ID: The "Opportunity ID" property is required. If omitted or invalid, the node will fail to update the record.
  • Field Validation Errors: If you provide invalid data types (e.g., text instead of a number for "Expected Revenue"), Odoo may reject the update.
  • Permission Denied: Ensure the Odoo user has permission to update opportunities.

Error messages and resolutions:

  • "Credentials are not valid": Check your Odoo API credentials and ensure the user has sufficient permissions.
  • "Settings are not valid: ...": There may be a misconfiguration in the connection settings; verify the URL and database name.
  • "Record not found": The provided Opportunity ID does not exist in Odoo.

Links and References

Discussion