OdooWiki OCA HUB

Ai Oca Bridge Document Page

ai_oca_bridge_document_page folder_open OCA/ai open_in_new
Uncategorised License: AGPL-3

This module is intended for allowing users to use OCA's Knowledge app for as a source of knowledge for AI Agents, although this is not the only usage this module could have

auto_awesome What this module does

AI-generated from the code · Odoo 18.0

Connects Odoo Documents (Knowledge pages) to AI Bridges so that creating, updating or deleting a page can automatically notify an external AI service. It is a technical connector with no new screens.

This module links the Documents app (the document.page model) with the AI Bridge framework. It does not add any new menu, screen or button: it only makes document pages behave like AI bridge threads, so the AI Bridge rules already configured in Odoo can react to what happens to a page.

  • When a document page is created, an AI bridge configured with the "create" usage can be triggered.
  • When a document page is updated, an AI bridge configured with the "write" usage can be triggered.
  • When a document page is deleted, an AI bridge configured with the "unlink" usage can be triggered.

The module ships demo AI bridge records that show this behaviour. They target the document.page model and send the page content, its display name and its draft name to an external web service. The demo bridges use no authentication, send the record as payload, expect no result and run immediately. The URLs in the demo point to an example address, so they are only illustrations and must be replaced by real endpoints before use.

In short, the module adds no business rules of its own; it simply exposes document pages to the AI Bridge mechanism so that external AI services can be kept informed about page changes.

Depends on

ai_oca_bridgedocument_page
Models and fields (1)
  • document.page · new model

Text generated by AI (DeepSeek) from reading the Odoo 18.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub

Availability by version

Reviewed: 2026-11-03
Confirmed (verified in repository and branch) Estimated (unverified) No information

Confirmation status: 3 confirmed, 6 with no information of 9 versions.

terminal Installation and usage

OCA documentation · Odoo 18.0

Configuration

Source · Odoo 18.0

Configuration Guide

To use this module as intended, two components must be configured:

  • Bridge configuration on the Odoo side
  • An endpoint capable of handling bridge requests

For an agent to have updated RAG (Retrieval-Augmented Generation) capabilities, you must create at least three bridges for each active knowledge database:

  • Bridge with Usage = "AI Thread Create" Adds document pages to the external database used by agents.
  • Bridge with Usage = "AI Thread Write" Updates document pages already on the external database used by agents.
  • Bridge with Usage = "AI Thread Unlink" Removes document pages from the external database when those pages are deleted from Odoo.

For creating those bridges, apart from the usage of the bridge, the user must define:

  • Payload Type: it depends on the endpoint configuration, normally "Record" would work.
  • Result Type: for this case "No processing" is OK.
  • Model: select the "Document Page" model
  • Field: add at least the fields the endpoint is expecting on the other side.
  • Filter: add a domain for using the bridge only with the documents intended to trigger bridge

For context, you can download an example n8n workflow JSON file capable of handling the bridge with Usage = "AI Thread Create". This workflow includes a manual trigger for testing purposes. Remember to update the models and database knowledge as needed.

Usage

Source · Odoo 18.0

Depending on the bridges you have created, create, update or delete a Document Page mathing the bridge domain. You should see the execution on the AI Bridge Execution menu.

For testing the endpoint side, you can download this n8n workflow JSON, capable of inserting information on the database. Keep in mind that for this to work at least content, display_name and draft_name fields should be included on the list of fields

No verified information in OCA: Installation.

info

Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.