Open-source ERP and CRM platform for business management, including sales, accounting, inventory, and project management
Open-source ERP and CRM platform for business management, including sales, accounting, inventory, and project management On Nagent, Odoo is exposed as a fully-configurable crm integration that any agent can call — 10 actions, and API key authentication. No code is required to wire Odoo into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Odoo to automate the kinds of tasks crm teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Odoo into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Odoo, with input parameters and output schema. Drop these into any step of an agent built in Helix.
ODOO_CALL_ODOO_JSONRPCJSON-RPC endpoint for Odoo external API calls. Provides the same functionality as XML-RPC but with JSON encoding. DEPRECATED in v19.0 and scheduled for removal in v20.0 (Fall 2026). Use JSON-2 API at POST /json/2/{model}/{method} instead.
Input parameters
Arguments to pass to the method. The structure depends on the service and method being called. For example, authenticate requires \[db, login, password\], execute_kw requires \[db, uid, password, model, method, args, kwargs\].
The method to call on the service (e.g., 'version', 'authenticate', 'execute', 'execute_kw'). For 'common' service: version, authenticate, login. For 'object' service: execute, execute_kw.
The service to call (e.g., 'common', 'object', 'db'). Common services include 'common' for version/authentication and 'object' for model operations.
The database name to connect to. If not provided, defaults to 'openerp' for Odoo.com instances or attempts to extract from metadata.
JSON-RPC request ID used to match responses with requests. Can be any integer.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ODOO_GET_APPLICANT_RESULTTool to retrieve parsing results for a previously submitted resume/applicant document. Use when you need to check the status and get extracted fields (name, email, phone, mobile) from a resume that was previously submitted for parsing.
Input parameters
API version number to use for the request
IAP (In-App Purchase) account token for authentication
Token received from the parse response that identifies the document to retrieve results for
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ODOO_GET_BANK_STATEMENT_RESULTTool to retrieve parsing results for a previously submitted bank statement. Returns extracted fields including balance_start, balance_end, date, and bank_statement_lines. Use when you need to check the status and get extracted data from a bank statement document using Odoo's Extract API.
Input parameters
API version number. Use 1 for current version.
IAP account token for authentication.
Token received from the bank statement parse submission response. Use this to retrieve parsing results.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ODOO_GET_EXPENSE_RESULTRetrieve parsing results for a previously submitted expense document. Returns extracted fields including description, country, date, total, and currency. Use this after submitting an expense document to get the OCR/extraction results.
Input parameters
API version number to use for the request
IAP account token for authentication and billing
Token identifying the document, returned from the parse/submit request
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ODOO_GET_INVOICE_RESULTTool to retrieve parsing results for a previously submitted invoice from Odoo Extract API. Use when you need to check the status and get extracted data from an invoice. Poll this endpoint until the status field is 'success' - processing may take time depending on document complexity.
Input parameters
API version number (must match the version used in the parse request)
IAP (In-App Purchase) account token used for the original parse request
Token returned from the invoice parse request. Used to identify the document being processed.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ODOO_LIST_DATABASESTool to list all available Odoo databases on the server. Use when you need to see which databases are available on the Odoo instance.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ODOO_PARSE_APPLICANTTool to submit a resume/CV document for OCR parsing and data extraction via Odoo Extract API. Extracts name, email, phone, and mobile from applicant resumes. Returns a document_token to poll for results. Cost: 1 IAP credit per successful parse.
Input parameters
API version number. Latest version is 102. Use this to ensure compatibility with the Extract API.
Base64-encoded resume/CV document (PDF or image format). The document should be encoded as a base64 string before submission.
JSON-RPC request identifier for tracking. Can be any unique string to identify this request.
IAP (In-App Purchase) account token for billing. Each successful parse consumes 1 IAP credit.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ODOO_PARSE_BANK_STATEMENTTool to submit a bank statement document for OCR parsing and data extraction via Odoo Extract API. Extracts balance_start, balance_end, date, and bank_statement_lines. Returns a document_token to poll for results. Cost: 1 IAP credit per successful parse.
Input parameters
API version number to use. Latest version is 100. Required to ensure compatibility with response format.
Array containing exactly one Base64-encoded document. Supported formats: PDF, PNG, JPG. The document will be parsed to extract bank statement fields (balance_start, balance_end, date, bank_statement_lines).
JSON-RPC request ID. Auto-generated UUID if not provided. Used to match responses with requests.
IAP (In-App Purchase) account token for billing. Each successful parse costs 1 IAP credit.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ODOO_PARSE_EXPENSETool to submit an expense document for OCR parsing and data extraction. Extracts description, country, date, total, and currency from expense receipts. Returns a document_token to poll for results. Use when you need to process expense documents using Odoo's Extract API.
Input parameters
API version to use. Latest version is 132.
Array containing one Base64-encoded document image to parse. Only the first document in the array will be processed.
IAP account token for billing. Cost: 1 IAP credit per successful parse.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ODOO_PARSE_INVOICETool to submit an invoice document for OCR parsing and data extraction via Odoo Extract API. Uses AI-based algorithms to extract fields like total, due date, invoice lines, VAT numbers, IBAN, supplier, client, and currency. Returns a document_token to poll for results. Cost: 1 IAP credit per successful parse.
Input parameters
Unique identifier of the Odoo database. Used for tracking and analytics.
API version number to use. Latest version is 123. Required to ensure compatibility with response format.
Array containing exactly one Base64-encoded document. Supported formats: PDF, PNG, JPG. The document will be parsed to extract invoice fields.
JSON-RPC request ID. Auto-generated UUID if not provided. Used to match responses with requests.
Optional user information to enhance OCR accuracy.
URL to receive a POST notification when parsing is complete. Useful for asynchronous processing.
IAP (In-App Purchase) account token for billing. Each successful parse costs 1 IAP credit.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 73 agents privately built on Nagent that already use Odoo.
Build on Nagent
Connect Odoo to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Odoo, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Odoo is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Odoo is connected, you configure its 10 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Odoo steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Odoo event fires, the agent kicks off automatically.
Every Odoo action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Odoo ships with 10 pre-built crm actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Odoo together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Odoo-based workflows tailored to your business.