Count Records
odoo.search_count
ActionCRM & salesconnection required
Calls the Odoo API with the connection's credentials.
Count the records of a model that match a domain, without reading any of them.
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
2 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 |
domain Odoo search domain: a JSON array of conditions, e.g. [["is_company", "=", true]]. Leave it empty to match every record the user may read. | array | No | — | — | [["is_company","=",true]] |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"domain": [
[
"is_company",
"=",
true
]
],
"model": "res.partner"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
count How many records match the domain. | number | — |
model The model the call was made against. | string | — |
{
"count": 0,
"model": ""
}Notes
- Each call authenticates first unless the connection carries a 'uid', which halves the requests this node makes.
See Count 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.