Read Records
odoo.read
ActionCRM & salesconnection required
Calls the Odoo API with the connection's credentials.
Read named fields of records whose ids you already have, for example the ids a previous search or create step produced.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- API key
- Providers
- Odoo
- Secret shape
- the API key, or {"api_key": "…"} — Odoo takes it in place of the password
- Config it needs
- base_url, db, username, uid
- Resolved by
- config.connection_id, else node.connection_id
Configuration
4 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
model Technical name of the Odoo model to act on, such as 'res.partner' or 'sale.order'. | string | Yes | — | — | res.partner |
ids Record ids to act on, as a JSON array of whole numbers. | array | No | — | array of number | [1,2] |
id A single record id — the convenient form when only one record is affected. | number | No | — | ≥ 1 | — |
fields Field names to return, as a JSON array. Leave it empty for every readable field, which is slower and much larger. | array | No | — | array of string | ["name","email"] |
- At least one of ids, id must be set.
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"fields": [
"name",
"email"
],
"ids": [
1,
2
],
"model": "res.partner"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
records The records Odoo returned, one object per record. | array | — |
count How many records the call returned or affected. | number | — |
missing_ids Requested ids Odoo did not return, because they no longer exist or the user may not read them. | array | — |
model The model the call was made against. | string | — |
{
"count": 0,
"missing_ids": [],
"model": "",
"records": []
}Notes
- A read is a partial success when 'missing_ids' is not empty: the step succeeds and names the ids that were dropped.
- A many2one field comes back as a [id, display name] pair and is written as a bare id; one2many and many2many fields are written with Odoo's command triplets, e.g. [[6, 0, [1, 2]]] to replace the whole set.
See Read Records run in a workflow.
In a technical demo we add the Odoo connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.