Appearance
Odoo integration
The Odoo integration reads and writes Odoo records from inside a playbook. It is the integration that turns a conversation or a document into something your business system actually holds.
What the Odoo integration can read and write
| Step | What it does |
|---|---|
odoo_read | Query any Odoo model with a domain filter, including time-relative filters like everything due in the next fourteen days |
odoo_bulk_create | Create records in bulk from a structured list, with a field map and a dry-run mode |
odoo_update | Write fields back to existing records |
sale_order_builder | Assemble a quotation with line items, quantities, unit prices and discounts from structured input |
line_item_editor | Amend the lines of a draft quotation before it is sent |
Reads and writes are separate steps on purpose. A playbook that only reads cannot accidentally be given write behaviour by a config change. odoo_bulk_create has a dry-run mode that logs every payload it would send without sending any of them, which is how you validate a field map before it touches live records.
Underneath, the client speaks three operations: create, write and search-read. There is no step that calls an arbitrary Odoo server action or workflow method, which keeps the blast radius of a misconfigured playbook to the records it names.
What the Odoo integration can be used for
Odoo can be used for automated quotation drafting, turning an intake form, an email or a transcript into a draft sale order with real product lines and real prices.
Odoo can be used for keeping project tasks in step with delivery, creating and updating tasks from the work that actually happened.
Odoo can be used for contact enrichment, writing back the details a workflow discovered rather than leaving them in a spreadsheet.
Odoo can be used for scheduled business reporting, reading records on a cadence and turning them into a report or a deck.
Odoo can be used with a human approval gate, so a generated quotation waits for a person before anything is written.
Odoo can be used as a grounding source for the company brain, so an assistant can answer what a customer ordered without anyone opening the ERP.
Odoo combined with other integrations
| Combination | What it gives you |
|---|---|
| Odoo + intake forms | A website enquiry becomes a draft quotation with line items, ready for review |
| Odoo + chat widget | A conversation on the site turns into a real quotation, gated on approval |
| Odoo + Google Sheets | Bulk operations prepared in a sheet and applied to Odoo in one run |
| Odoo + Slack | Quotation approvals in the channel the sales team already uses |
| Odoo + company brain | Answers about orders, projects and contacts, grounded in the ERP |
| Odoo + Shopify | Shop revenue and ERP revenue reconciled in one place |
What you need to connect Odoo
- Your Odoo instance URL and database name
- A dedicated integration user with only the access rights the playbook needs
- That user's API key
Use a dedicated user rather than a person's login. It scopes the blast radius and it makes the audit trail readable.
Frequently asked
Does it work with Odoo Online and self-hosted? Both, as long as the external API is reachable.
Can it delete records? No. Read, create and update only.
Can it confirm or send a quotation? Not directly. Studio builds and updates the draft; confirming and sending stay a human action in Odoo.
Which Odoo versions? The integration speaks the standard external API, so it is version tolerant. Model and field names are yours to supply, which is what makes it work across versions and custom modules.