AI OCA Bridge
This module is used to create a bridge between Odoo and other AI systems like n8n.
Table of contents
Use Cases / Context
Right now, there are 2 different approaches for AI integration with Odoo:
Make everything inside Odoo.
Make it using other tools and integrate Odoo with these tools.
IMO, it would be better to make use of option 2 for different reasons:
Odoo server is intended as a transactional system. AI systems requires other kind of characteristics
Everything changes too fast. I am not confident that Odoo can keep the pace in this topic
There are OSS tools that fills the gap perfectly and are created just for this topic.
Anyway, OCA is open to everyone and we don’t intend to force an opinionated way of doing. For this reason, we have this module, that can be used as Bridge with AI systems.
Configuration
As an administrator access AI Bridge\AI Bridge.
Create a new bridge. Define the name, model, url and configuration.
In order to improve the view of the AI configuration, use groups and domain to set better filters.
Payload Configuration
On the external system, you will receive a POST payload. The data included will be the following:
General
_odoo: Standard data to identify the Odoo Database
_model: Model of the related object
_id: Id of the related object
_response_url: Url to call with the response in case of async calls
Record Payload
Adds a new item called record with all the fields.
Asynchronous and synchronous calls
The new system allows asynchronous and synchronous calls. Asynchronous calls makes sense when the task to be processed don’t need to be immediate. For example, reviewing an invoice and leave a comment with the result. The same would happen with a chat message. We expect that the system will leave time to the AI to answer and Odoo’s user can do other things.
Meanwhile, Synchronous calls will froze odoo system and wait for an answer. This makes sense when we expect some feedback from odoo user. It makes sense, when we open an action for example.
In the synchronous call, the result is processed when the AI system answers on the webhook. On the other hand, it will be processed automatically on the synchronous call.
Result processing
With the answers of the system we expect to do something about it. We have the following options:
No processing
In this case, the result will do nothing
Post a Message
We will post a message on the original thread of the system. The thread is computed by a function, so it can be overriden in future modules. It expects the keyword arguments of the message_post function.
Action
It expects to launch an action on the user interface. It only makes sense on synchronous calls.
It expects an action item with the following parameters:
action: xmlid of the action
context: Context to pass to the action (not required)
res_id: Id of the resource (not required)
Usage
Use the bolt widget in the chatter to execute the different AI options.
The options will be filtered according to the configuration.
Known issues / Roadmap
Define examples to use and import
Allow child fields. Right now, only first level fields are accepted.
Information popover is not working properly when there is large data.
Bug Tracker
Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us to smash it by providing a detailed and welcomed feedback.
Do not contact contributors directly about support or help with technical issues.
Credits
Contributors
-
Enric Tobella
-
Valentín Vinagre
-
Ariel Barreiros
Adria Hortoneda
Maintainers
This module is maintained by the OCA.
OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.
This module is part of the OCA/ai project on GitHub.
You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.
1 maintainer
Metadata
1 maintainer
Release files for odoo-addon-ai-oca-bridge 18.0.2.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| odoo_addon_ai_oca_bridge-18.0.2.0.1-py3-none-any.whl | Python 3 | none | any | Details for odoo_addon_ai_oca_bridge-18.0.2.0.1-py3-none-any.whl |
Release files / odoo_addon_ai_oca_bridge-18.0.2.0.1-py3-none-any.whl
| Download URL | odoo_addon_ai_oca_bridge-18.0.2.0.1-py3-none-any.whl |
|---|---|
| Size | 137.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a32a5ea01ae5ecaacf77e4dfe4eefe65cb81d105169b42f60cefb5586ec92c30
|
|
BLAKE2b-256 checksum How to use checksums |
d6f24a066f01d496ebb8e7148513964f023edb91272ac4b42a4affb361961adc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Security for odoo-addon-ai-oca-bridge 18.0.2.0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
