Skip to main content
Belcenter AIHelp center
Configure a bot

Connect Odoo and CRMs

Configure Odoo, prepare CRM context prior to the call, and control searches and follow-up notes.

CRM integrations allow the bot to search for a contact, read authorised information, or create an item such as a ticket or lead.

Using actions in messaging channels

Odoo actions enabled on the bot are also available across text and voice WhatsApp, Messenger, and website chat. Configure the connection and its actions within the same Odoo skill, then save the bot; no channel-by-channel duplication of the configuration is needed. Skill settings saved via the public API apply in the same manner.

A booking must be preceded by the checks specified in your instructions, then confirmed by a successful Odoo write operation. In the conversation details, review the odoo tool calls and their technical outcome to verify both search and creation. A simple message from the bot does not prove that a booking exists. In the event of an error or uncertain result, verify Odoo before re-attempting creation to prevent duplicates. Completed conversations are not replayed automatically.

Each channel retains the same connections, actions, and authorised fields. Disabling the skill or removing an action grants no additional access to messaging channels; Odoo controls continue to be enforced server-side.

Successful Odoo operations are also recorded in Actions performed, as with a SIP call, and in the actions returned by the conversation API. A check for availability and a record creation remain two distinct operations. An Odoo error does not count as a successful action. The recap and the technical details are two complementary pieces of information: the booking must be verified from the creation result, not solely from the summary text.

Using an Odoo preset

After creating the Odoo connection, select Add a preset. Search for the relevant use case and choose a ready-to-use configuration: caller identification, tickets, CRM, appointments, or customer account lookup, depending on your Odoo version.

The guided form initially displays the name, enabled status, and description of each action, along with a summary of the model and method. Open Technical action settings to modify the models, fields, filters, and parameters understood by the AI. Advanced JSON configuration remains available for special cases; the guided form and the JSON stay synchronised. Closing a panel preserves its configuration.

Odoo 18, Odoo 19, and Odoo 20

Select the exact version of your environment. BeAI adjusts API methods and preset fields accordingly. Do not manually add a field that does not exist in your Odoo model.

For a custom action targeting a record, the legacy format args: [[id]] remains compatible with both versions: it is retained in XML-RPC for Odoo 18 and converted to a named parameter ids by the JSON-2 API of Odoo 19. The flattened format args: [id], occasionally generated by the model, is normalised in the same way. Other method parameters must remain named arguments in kwargs.

For a chatter message with multiple paragraphs or a list, use simple HTML in body (<p>, <ul>, <li>) with body_is_html=true. The Customer account and invoices and Ticket management presets require this format for their internal notes. If a legacy action supplies HTML tags without explicitly enabling body_is_html, BeAI converts them into readable plain text so that Odoo does not display them literally.

The Customer account and invoices preset first retrieves the exact invoice, then reads its lines (account.move.line) to explain products, descriptions, quantities, and amounts. It can then log the contact’s response in its chatter. Both searches require an explicit JSON Odoo domain to avoid accidentally reading another invoice.

Before calling Odoo, BeAI converts unambiguous variants into canonical form: native arrays, serialised domains or clauses, nested JSON encoding, extra wrappers, omitted outer brackets, JSON Markdown blocks, and clauses in field/operator/value format. Logical operators are validated according to Odoo prefix notation; a genuinely redundant binary operator is removed and an unambiguous simple infix expression is converted. An empty domain where one is required, an incomplete operator, an invalid clause length, or a scalar value with in/not in is rejected locally with an actionable format error. In all cases, the strict whitelist of permitted fields and operators is enforced after normalisation and before any call to Odoo.

A search condition must contain exactly three elements: field, operator, and value, for example ["active", "=", true]. If an operator is omitted, BeAI rejects the search before any access to Odoo and indicates the syntax to correct; it does not guess the condition or remove the customer filter. The bot must answer any remaining follow-up questions before wrapping up: logging a note or announcing human follow-up is no substitute for providing the requested information.

Logging the call summary on a contact

Configure an action res.partner.message_post with subtype_xmlid=mail.mt_note set in the action parameters, then explicitly specify in the instructions to create a single note on the identified contact. Identification alone and tool availability do not trigger this write operation. The BeAI summary and an Enreach note do not replace this Odoo note.

For a normal call conclusion, the bot must log the note before requesting hang-up. If the caller hangs up first, silent wrap-up still allows authorised reads of the contact, the sales representative, and existing notes, followed by this internal note, before the final report. This window is limited to processing the report; it does not permit transfers, quote modifications, or any other late actions. Odoo permissions, models, and configured fields remain identical whether configured via the interface or the API.

Instruct the bot to wait for Odoo confirmation and avoid duplicates if the note has already been recorded before a transfer. An uncertain result must be verified before retrying. A created note does not prove that it was read or that a notification was delivered; any failure must remain visible in the summary.

Selecting the execution language

The language used by the Odoo API is independent of the language spoken by the bot. In the connection, choose Fetch languages: BeAI queries res.lang using the API account and displays only the active languages on that instance. Then select the desired language.

BeAI passes this choice in context.lang with each operation, using XML-RPC for Odoo 18 as well as JSON-2 for Odoo 19 and Odoo 20. Without an explicit choice, the fallback value is en_US. A language deactivated in Odoo must be removed or replaced after refreshing the catalogue.

Caller identification

The fixed identification preset normalises the incoming number prior to lookup. It can thereby match a national number with its international format. The retrieved name is used to personalise the greeting without injecting all the contact's details.

Prepare CRM context before the call

In the Odoo connection, enable Caller identification, then tick Inject additional CRM context for the matched contact (Contact, CRM, Invoices, Quotations, ...). This second option is disabled by default and becomes inactive if identification is disabled. Save using the bot's usual button.

BeAI prepares data via fixed API reads before the conversation starts: the contact, their company, and their account manager, up to three ongoing quotes and twenty-four quote lines, three open opportunities, three outstanding invoices, and five recent interactions on these files. The bot receives this context directly in its call instructions; it does not need to call a tool to perform this preparation. It can greet the person by name and ask whether their call relates to their quote, without assuming the purpose of the call or spontaneously quoting amounts.

The full number must match a single contact. A shared number, multiple Odoo lookup directories, or an approximate match will prevent the file from loading. Data is limited to the matching contact and their commercial organisation; BeAI preserves the Odoo API account permissions and does not alter any records. Number recognition is not a substitute for identity confirmation before disclosing financial or confidential details.

Data preparation has an overall three-second timeout. An inaccessible or excessively slow section is marked as unavailable without preventing the greeting; it does not mean the customer has no records. The context contains its retrieval timestamp and remains a limited preview. The bot can then use permitted actions to request missing details, check more recent information, or log the call note.

The public API exposes the same setting in PATCH /api/v1/bots/{id}/skills/odoo. Return existing connections with their connectionKey, keeping their actions, and add the two booleans:

{
  "enabled": true,
  "connections": [{
    "connectionKey": "0123456789abcdef0123456789abcdef",
    "enabled": true,
    "version": "20",
    "baseUrl": "https://odoo.example.com",
    "callerIdentificationEnabled": true,
    "callerContextEnabled": true
  }]
}

The response and GET read endpoint return these same options. The stored API key is preserved when you do not return apiKey. With callerIdentificationEnabled: false, callerContextEnabled is saved as false in both the interface and the API. No customer context is added to public configuration responses.

Create an actionable ticket

The ticket preset transmits at minimum a title, a description derived from the conversation, and the identified customer when this information is available. Add your team's mandatory fields to the instructions.

Security

  • Use a dedicated API account.
  • Fetch languages again after installing or disabling a language in Odoo.
  • Only allow required models and methods.
  • Avoid deleting data.
  • Test searches with multiple contacts sharing the same name.
  • Check the actual result in the CRM after each change.

Verify invoice contents

An invoice's source field and reference do not necessarily describe the billed services. The bot must read the lines of the exact invoice before explaining its contents. Configure a read action on account.move.line restricted to that invoice; BeAI does not add permissions or automatic background reads.

If lines cannot be accessed, the bot states that it cannot confirm details. If the header, lines, or customer statements contradict each other, it highlights the discrepancy and offers human follow-up. An intervention for the same customer is not automatically linked to the invoice; a past scheduled date does not prove completion. A posted entry must not be re-submitted to announce success.

Searches and field service intervention follow-up

Search filters submitted by the bot feature explicit field, operator, and value fields. For example, {"field":"is_fsm","operator":"=","value":true} represents the condition ["is_fsm","=",true]. Both formats undergo the same validation. A customer filter, a boolean, and an ID list retain their meaning; an omitted operator is never guessed. Full action descriptions remain available to the model, including restrictions indicating which record a note must be posted to.

A scheduled date indicates planning, not proof of completion. An intervention not marked as completed may have started. If the record provides no confirmed upcoming date, the bot must explain this rather than announcing an elapsed date or stating that nothing has taken place. A logged note does not prove that the team has read it, that a notification was delivered, or that an appointment was scheduled.

Documentation updated with the application