Describe Fields

odoo.fields_get

ActionCRM & salesconnection required

Calls the Odoo API with the connection's credentials.

Return the model's field definitions — type, label, required flag and selection values — so a create or write can be built against what the instance actually has.

Ask about Odoo All Odoo nodes Provider API docs ↗

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

3 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
fields Field names to describe, as a JSON array. Leave it empty to describe every field on the model.	array	No	—	array of string	["name","email"]
attributes Which attributes of each field to return, such as ["string", "type", "required", "selection"].	array	No	—	array of string	["string","type","required"]

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "attributes": [
    "string",
    "type",
    "required"
  ],
  "fields": [
    "name",
    "email"
  ],
  "model": "res.partner"
}

Output

One shape.

result

Field	Type	Example
fields Field definitions, keyed by field name.	object	—
names The field names, sorted.	array	—
count How many fields were described.	number	—
model The model the call was made against.	string	—

{
  "count": 0,
  "fields": {},
  "model": "",
  "names": []
}

Related Odoo nodes

See Describe Fields 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.

Book a technical demo Talk to sales