ERP & Finance · 64 pre-built actions
Odoo integration with Nexus
Run Odoo sales, invoicing and product steps under control. Products, customers, sales orders, invoices and employee actions become governed steps that connect Odoo to commerce, CRM and identity.
Pre-built actions
What you can automate
64 pre-built Odoo actions, grouped by what they work on.
64
PRE-BUILT ACTIONS
- 01Sales Orders and Invoice actions support order-to-cash steps.
- 02Products and Customer actions keep master data aligned with other systems.
- 03Employee actions bring people data into onboarding and access processes.
Workflow
How it fits into a Nexus workflow
Odoo steps run as pre-built actions. A run that uses them starts from a webhook, a schedule, a request in Nexus or another system's trigger source.
A trigger source starts work. A connector action performs work. Both run inside the same governed execution.
Beyond pre-built actions
When the pre-built action is not enough
Move down one step: an API, protocol or database call, then custom logic in Python, Bash, Go, Java, .NET, PHP, PowerShell or JavaScript/TypeScript with any library. Every step uses the same secrets, approvals, history and audit.
01
Call the Odoo API with the HTTP Request node, or use GraphQL, SOAP or a database node where the system exposes one.
02
Write custom integration logic in Python, Bash, Go, Java, .NET, PHP, PowerShell or JavaScript/TypeScript, with the libraries your team already uses.
03
Direct calls and code use the same vault-backed secrets, approvals, run history and audit as pre-built actions.
Examples
Workflow examples
Commerce order to Odoo
An online order is validated and created as an Odoo sales order, then invoiced.
Customer master alignment
Customer records are checked against CRM and differences go to review rather than overwrite.
Invoice exceptions to finance
Invoices outside tolerance pause for a finance owner before posting.
Deployment, trust and audit
Governance, audit and deployment
Deployment
Nexus runs on-premises, in private or sovereign cloud, or air-gapped. The step needs network reach to the system it calls, and nothing else changes.
Secrets and identity
Credentials are referenced through vault-backed secret handling and role-based access, never embedded in workflow logic.
Audit
Inputs, outputs, approvals and outcomes are written to the execution history for every run.
FAQ
Odoo connector questions
- Which Odoo actions are pre-built?
- Nexus includes 64 pre-built Odoo actions across Products (13), Customer (14), Sales Orders (12), Invoice (10) and Employee (15).
- Can Odoo start a workflow?
- Runs that use Odoo start from a webhook, a schedule or another trigger source. Odoo steps run as actions inside the workflow.
- What if the operation I need is not pre-built?
- Use the Odoo API through the HTTP Request node, or write the step in Python, Bash, Go, Java, .NET, PHP, PowerShell or JavaScript/TypeScript. It runs in the same workflow with the same approvals and audit.
Related reading
Continue from here
- Shopify connector
Orders, customers, products and inventory.
- Stripe connector
Products, core resources and billing.
- Salesforce connector
Leads, accounts, opportunities and cases.
- Integration patterns
How systems work together in a complete process.
Integration review
Discuss how Odoo fits your process.
Bring the operation you need. We will map it to a pre-built action, or to the API, protocol or code step that covers it.