Question 1

What exactly is ERPipe?

Accepted Answer

A hosted, multi-tenant Odoo gateway and control plane for MCP-compatible AI agents. It exposes structured Odoo capability and gives operators controls for identity, actions, approvals, audit, usage, events, and lifecycle.

Question 2

Can an agent change Odoo records automatically?

Accepted Answer

Writes start disabled. When write capability is enabled, create, write, and unlink operations can be previewed, validated, and routed to owner approval. Chatter notes and allowlisted methods use separate gates.

Question 3

Does ERPipe replace Odoo permissions?

Accepted Answer

No. The connected Odoo user's ACLs and record rules remain authoritative. ERPipe adds scopes, field policy, method allowlists, approval, limits, and operational controls on top.

Question 4

What happens if a write result is uncertain?

Accepted Answer

The operation is recorded as unknown and is not retried automatically, avoiding a blind duplicate mutation.

Question 5

What is stored in the audit trail?

Accepted Answer

Every tool call is audited with redacted and bounded operational detail. ERPipe does not claim to store complete raw request and response payloads.

Question 6

Do Odoo webhooks automatically trigger an agent?

Accepted Answer

No. Signed events enter a bounded queue. An approved client explicitly lists and acknowledges them; the client or orchestrator controls polling and execution.

Question 7

Which Odoo versions are intended to work?

Accepted Answer

The intended compatibility path covers Odoo 16–18 through XML-RPC and Odoo 19 through JSON-2. Setup probes the live instance before activation.

Question 8

How are credentials and workspaces handled?

Accepted Answer

Credentials are encrypted, OAuth tokens are bound to one workspace, and tenant workspaces remain isolated. Owners can revoke grants, drain sessions, pause individual connections, rotate webhook secrets, or request deletion.