OdooWiki OCA HUB

AI OCA Bridge Field Service

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

This module is a glue module between AI OCA Bridge and Field Service.

auto_awesome What this module does

AI-generated from the code · Odoo 16.0

Connects Field Service orders to the AI OCA Bridge so an AI service can be triggered from a field service order. It adds the AI bridge conversation capability to fsm.order records.

This is a glue module that links two other modules: the AI OCA Bridge and Field Service. Its only code change is to make the Field Service Order model (fsm.order) also behave as an AI bridge thread, by inheriting the ai.bridge.thread behaviour. In practice this means a field service order can be used as the record that an AI bridge configuration points to.

Because of this, users can set up an AI bridge (in the AI OCA Bridge configuration) whose target model is the Field Service Order, and then have that bridge run against field service orders. The module itself adds no new menus, buttons, reports, business rules, checks, computed fields, emails or scheduled jobs.

The demo data shows an example configuration: an AI bridge named "FSM Order AI Bridge - Demo" aimed at the fsm.order model, using the "ai_thread_create" usage, sending a record payload to an external URL, with no authentication and no result handling. The demo also creates a sample location, person and field service order to illustrate the setup. These demo records are only examples and are not active business logic.

In short, the module touches the Field Service Order area and the AI Bridge configuration, allowing field service orders to be sent to an AI service through the bridge.

Models and fields (1)
  • fsm.order · new model

Text generated by AI (DeepSeek) from reading the Odoo 16.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: 1 confirmed, 8 with no information of 9 versions.

terminal Installation and usage

No verified information

Installation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.

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.