Connect Odoo 19 or 20
Authorise connection from Odoo, configure bots, prompts, and languages, monitor minutes, and restrict permissions.
The BeAI app for Odoo allows you to prepare calls without copying an API key or entering BeAI's technical URL. A single connection links your entire Odoo database to a BeAI organisation: connection, bots and credits are shared across all of its companies. Switching companies in Odoo does not require a new connection.
The connector's menus, buttons and statuses follow the Odoo user's language.
Model and voice names are displayed with human-readable labels, without
technical keys. The BeAI catalogue provides French and English labels;
an unavailable language falls back to the English label. Refreshing the bot
updates these labels without changing its voice, instructions or call language.
The API /api/v1/bots/{id}/odoo-configuration exposes the same options in
label (depending on Accept-Language) and label_translations (Odoo languages).
First connection
- In the BeAI settings in Odoo, click Connect to BeAI.
- Log in to BeAI and select an organisation you manage.
- Check the Odoo database name and address, then authorise the shared link.
- Back in Odoo, the bot and its business access are prepared automatically.
- Open the bot's details to select an existing line or enter your SIP configuration, then click Test configuration.
On the authorization page, first check the database, the instance URL and the requested permissions. Then select the BeAI organisation, followed by Authorise connection in the action bar below the form. Decline exits this request without establishing a connection.
The test does not dial any number. "Connected" means the link is established, not that telephony is operational. Odoo access, configuration, telephony status and calling capacity are checked separately. A bot quota limit or the lack of an available voice model must be resolved by an administrator: no subscription, top-up or phone number rental is carried out automatically.
The connection creates a default bot. The bots menu allows you to add more within your quota limits. A bot already configured in a previous setup can be reused without recreating it. Old shared keys are not revoked automatically.
Ready-to-use prompt templates
The module provides six active presets available to all companies: payment reminder, invoice follow-up, ticket resolution confirmation, missing ticket information collection, quotation follow-up and contact details verification. Helpdesk and Sales templates are loaded only if the corresponding app is installed.
After installing an additional app, Load missing presets in the template list adds any newly available templates, without overwriting your texts, bot selections or archived items. These templates do not trigger calls on their own: select them explicitly in a Studio action or follow-up level. If no bot is specified, the default shared bot is used; you can choose another synchronised bot.
Presets do not create payments or orders, nor do they grant any additional permissions. Contact details updates are logged for human validation. A quotation follow-up can use document values and record the response on the contact; reading additional models directly always requires explicit administrator authorization.
Synchronised configuration
From Odoo, you can edit the name, instructions, default language, AI model and voice. The drop-down lists reflect the account’s actual capabilities. An available existing line can be assigned without purchasing a new one. The SIP password can be entered, but is never returned in plain text.
BeAI remains the source of truth. Refresh reloads its configuration. If another user has modified it in the meantime, reload the record before saving: revision tracking prevents silent overwrites. Notifications and periodic synchronisation complement this refresh.
Configure more, restricted to Odoo BeAI Managers, opens limited temporary access to the bot. It does not sign in to the owner's personal account and does not grant access to API keys or other organisations.
Prompts, Studio, and languages
A prompt template selects the relevant document, the bot and the instructions. Then select this template in the Studio action or follow-up level: no additional bot ID is required.
The preview displays the contact actually called, their normalised number, the bot, the language and the rendered prompt. For invoices, it adheres to the customer's payment reminder contacts. For a ticket, the contact is deduced from the ticket record.
The language expression is {{ object.lang }} for a contact, or the partner's
language for another document. If it is empty, the contact's language
and then the bot's language will apply. The requested language is passed for this call
only, including the greeting: it does not alter the bot's global setting.
Missing a preprompt for a language does not block the call; the actual
language and voice capabilities remain those of the selected model.
The context is recalculated immediately before dispatch. An already submitted campaign will not be overwritten by a subsequent modification to the ticket or prompt.
Authorised data and actions
The link uses the Odoo user initiating the connection: no new user or extra Odoo licence is required. Their dedicated key is limited to connector actions and to the companies this user has access to, without modifying their groups or broadening their existing permissions. It does not grant access to the general Odoo API. If this user loses access to a company, documents from that company will no longer be accessible to the bot. If the user is archived or deactivated, reconnect BeAI with an authorized user. Sharing the integration does not share documents: native Odoo rules and the connector's authorized scope continue to apply. Closing a ticket upon customer confirmation first posts a customer message and then switches the status to resolved, with duplicate protection. A payment promise never marks an invoice as paid.
The Odoo administrator can authorize additional business models, their readable fields and optionally internal notes. These models must belong to a company. Configuration models, secrets and administrator permissions cannot be authorized. After making changes, use the permission synchronisation button. This does not permit automatic payments or deletions. BeAI cannot grant itself permissions that the Odoo connector denies.
Minutes and credit
Included, used, reserved and available minutes are separate from prepaid credits. BeAI applies the billing period, reservations, overage and any call charges. A zero balance (0 €) does not on its own prevent a call covered by included minutes.
The availability check is informational and does not reserve credit. The final decision and atomic reservation take place when the call actually starts. A concurrent call can therefore change availability. Existing purchases and auto-recharge policies remain under your control.
Tracking and security
Callbacks update Odoo statuses immediately. Periodic synchronisation complements them in case a callback is missed. An unknown status or lack of callback does not mean the call did not take place.
The Odoo connections page in BeAI allows you to view, test, renew and revoke your links. Revocation blocks new dispatches and advanced sessions, without clearing history or attempting to cancel an ongoing conversation. Connection secrets remain server-side.
A duplicated or restored Odoo database must be explicitly reactivated. Links are tied to the database identity and URL. Developer mode, accessible to administrators in developer mode, uses separate credentials and bots; pending calls are not transferred to Production.
API and authorisation
Business operations are exposed under /api/v1/odoo/connections,
/api/v1/bots/{id}/odoo-configuration and
/api/v1/bots/{id}/call-capacity. The detailed specification is documented in OpenAPI.
A link key requires the headers X-Odoo-Instance and
X-Odoo-Installation and does not allow account management.
Starting the protocol uses POST /integrations/odoo/connect/start
with instance_url, installation_id, scope: "database", company_id: "database",
company_name (database name, retained for backwards compatibility),
state and code_challenge (PKCE S256). The response contains a
authorization_url. After consent, the browser redirects back to the fixed Odoo
callback with a single-use code valid for two minutes.
POST /integrations/odoo/connect/token exchanges code and
code_verifier server-to-server. The browser never receives the API key.
These transports and callbacks are not business operations authenticated by
API key: their exact purpose is to obtain this authorization.
A declined, expired or interrupted request must be restarted from Odoo. Requests are rate-limited by origin and network address; a temporary refusal indicates that you should try again later.
Return after connection
If you are not yet logged in to BeAI, sign in with Microsoft, Google, or your BeAI account. You are then returned to the Odoo authorisation prompt: signing in to the account does not constitute authorisation of the link.
View and manage connections
In Odoo connections, each company displays the instance, the authorization or revocation status, and the expiry date of its connection. For each bot, telephony status and Odoo access remain visible. Test access, telephony and capacity without calling runs this test without placing a call.
Add bot remains subject to account quotas and permissions. Renew connection and Revoke connection require an explicit action; revocation requires confirmation and does not cancel calls already in progress. Viewing the page or opening a menu does not trigger these operations.