# Odoo - Workflow node | Docs - nodulz

Source: https://nodulz.com/docs/nodes/odoo

Language: en

Run any permitted public method on an Odoo model through JSON-2.

## Usage and specifics

This connector uses JSON-2, available from Odoo 19. Set baseUrl, database, model and public method. The Odoo user permissions and plan API access apply.

Technical type : `odoo`. Runtime : `nodulz`.

## Credentials and prerequisites

- [Create and configure the credential : odoo](/docs/credentials/odoo)

Create credentials in your nodulz instance’s Credentials area, then select them on the node. Availability depends on ownership and sharing. See the [credentials guide](/docs/credentials) for access and rotation.

## Parameters

Names below are technical keys. Defaults are not a ready-to-run configuration: complete fields required by your operation. Paths containing [] describe list items; some fields depend on the selected mode.

| Parameter | Type | Default | Values / limits |
| --- | --- | --- | --- |
| `credentialId` | `string` | `""` | - |
| `baseUrl` | `string` | `""` | - |
| `database` | `string` | `""` | - |
| `model` | `string` | `"res.partner"` | - |
| `operation` | `enum` | `"search_read"` | `search_read`, `search_count`, `read`, `create`, `write`, `unlink`, `fields_get`, `name_search`, `custom` |
| `method` | `string` | `""` | - |
| `parameters` | `string` | `"{}"` | - |

## Configuration help

| Setting | Purpose and guidance |
| --- | --- |
| `credentialId`<br>Odoo credential | API key created in Odoo user preferences. |
| `baseUrl`<br>Odoo URL | Root URL of your Odoo instance, without /json/2. |
| `database`<br>Database | Technical Odoo database name; leave blank for a single database. |
| `model`<br>Model | Choose a common model or enter a custom technical name. Available models depend on your instance modules and permissions. |
| `operation`<br>Operation | Choose a common or custom method. |
| `method`<br>Method | Exact name of the model public method. |
| `parameters`<br>JSON parameters | JSON object sent to Odoo. For creation, use vals_list with a field object or list. For updates, use ids and vals. Workflow expressions supported. |

## Initial configuration

Initial catalog configuration example, to adapt before running. Keep secrets in credentials.

```json
{
  "credentialId": "",
  "baseUrl": "",
  "database": "",
  "model": "res.partner",
  "operation": "search_read",
  "method": "",
  "parameters": "{}"
}
```

## Verification

Test with representative data. Check node output in the inspector and logs, then use editor mapping for downstream fields. A trigger test with a simulated payload does not validate external service delivery.

See also : [Expressions and data](/docs/expressions), [Executions](/docs/executions), [Node catalog](/docs/nodes).

## Explore further

- [Features - nodulz](https://nodulz.com/product/overview)
- [Node catalog - nodulz](https://nodulz.com/product/catalog)
- [MCP server - nodulz](https://nodulz.com/product/mcp)
- [Pricing - nodulz](https://nodulz.com/pricing)
- [Use cases and workflow automation - nodulz](https://nodulz.com/use-cases)
- [Choose what your workflows can do. - nodulz](https://nodulz.com/compare)
- [Documentation - nodulz](https://nodulz.com/docs)