Get Default Values
odoo.default_get
ActionCRM & salesconnection required
Calls the Odoo API with the connection's credentials.
Ask Odoo which values it would prefill for a new record of this model, so a create can start from the instance's own defaults.
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, 2 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 |
fields Field names to get defaults for, as a JSON array. | array | Yes | — | array of string | ["company_id","currency_id"] |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"fields": [
"company_id",
"currency_id"
],
"model": "res.partner"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
values The default values, keyed by field name. | object | — |
count How many defaults Odoo returned. | number | — |
model The model the call was made against. | string | — |
{
"count": 0,
"model": "",
"values": {}
}See Get Default Values 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.