Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Odoo

Open source all-in-one management software

CategoryOther
Authenticationcustom
Version0.1.7
Published scopes0 published scopes
Last updatedSeptember 30, 2026

Overview

Connect Odoo with Flows360

Open source all-in-one management software

Use the Odoo connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 7 actions and no declared triggers.

Available actions

  • Get contacts
  • Create contact
  • Create company
  • Custom Search and read records
  • Custom Create Record
  • Custom Update Record
  • Custom API Call

Available triggers

  • No triggers are declared in this pinned package.

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Odoo
  • Package: @activepieces/piece-odoo@0.1.7
  • Exact artifact digest: sha256:6e0c8a0c57be817ca157a8413a22ab183801238a5baf7a1aa790df70e873edab
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

CUSTOM AUTH. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Get contacts (get_contacts), Get contacts on Odoo Classification: read.
  • Create contact (create_contact), Create/Update contact on Odoo Classification: read.
  • Create company (create_company), Create/Update company on Odoo Classification: read.
  • Custom Search and read records (get_records), Records can be listed and filtered Classification: read.
  • Custom Create Record (create_record), Create a new record in the specified model Classification: read.
  • Custom Update Record (update_record), Update an existing record in the specified model Classification: read.
  • Custom API Call (custom_odoo_api_call), Make a custom XML-RPC API call to Odoo Classification: read.

Trigger contracts

  • No trigger delivery contracts are declared.

Verification

Runtime execution evidence is managed separately from package metadata.

Capability summary

Authenticationcustom
Supported objects7
Supported actions7
TriggersNone published

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • Odoo URL Required
  • Odoo Database Required
  • Odoo Username Required
  • Odoo API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Get contacts Yes No Get contacts on Odoo
Create contact Yes No Create/Update contact on Odoo
Create company Yes No Create/Update company on Odoo
Custom Search and read records Yes No Records can be listed and filtered
Custom Create Record Yes No Create a new record in the specified model
Custom Update Record Yes No Update an existing record in the specified model
Custom API Call Yes No Make a custom XML-RPC API call to Odoo

Supported actions

Get contacts · Read

Get contacts on Odoo

get_contacts · Risk: low · Retry: safe

Inputs

  • type · string · Required, Select which contact type to get
  • name · string · Optional, Would you like to search any specific name?
Create contact · Read

Create/Update contact on Odoo

create_contact · Risk: low · Retry: safe

Inputs

  • name · string · Required
  • phone · string · Required
  • email · string · Required
  • company · string · Required
  • title · string · Required
Create company · Read

Create/Update company on Odoo

create_company · Risk: low · Retry: safe

Inputs

  • name · string · Required
  • phone · string · Required
  • email · string · Required
Custom Search and read records · Read

Records can be listed and filtered

get_records · Risk: low · Retry: safe

Inputs

  • model · string · Required, Model name. e.g.: res.partner
  • domain · object · Optional, A domain is a list of criteria, each criterion being a triple of (field_name, operator, value). See https://www.odoo.com/documentation/17.0/developer/reference/backend/orm.html#reference-orm-domains for details.
  • fields · array · Optional, Returns the requested fields of the records. When undefined, returns all fields.
  • offset · number · Optional
  • limit · number · Optional
Custom Create Record · Read

Create a new record in the specified model

create_record · Risk: low · Retry: safe

Inputs

  • model · string · Required, Model name. e.g.: res.partner
  • fields · object · Required, JSON object of field names and their corresponding values
Custom Update Record · Read

Update an existing record in the specified model

update_record · Risk: low · Retry: safe

Inputs

  • model · string · Required, Model name. e.g.: res.partner
  • recordId · number · Required, ID of the record to update
  • fields · object · Required, JSON object of field names and their corresponding values
Custom API Call · Read

Make a custom XML-RPC API call to Odoo

custom_odoo_api_call · Risk: low · Retry: safe

Inputs

  • model · string · Required, The Odoo model to interact with (e.g., res.partner, product.product)
  • method · string · Required, The method to call on the model (e.g., search_read, create, write)
  • method_params · object · Required

Setup

Setup

  1. Add the Odoo connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • Odoo URL (base_url), required.
  • Odoo Database (database), required.
  • Odoo Username (username), required.
  • Odoo API Key (api_key), required; stored as a sensitive connection value.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-odoo@0.1.7; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 7 actions and 0 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Runtime execution evidence is managed separately from package metadata.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Odoo connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-odoo@0.1.7 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com