company logo

Help center

Go to Signitic
DashboardWebsiteLinkedin
All collectionsSettingsConnectorsOdoo Connector

Odoo Connector

Connect Odoo to Signitic to associate your users and push their email signatures into Odoo.

info icon
The Odoo connector allows Signitic to send the HTML of their signature in the Odoo signature field. This is a destination connector: it does not create a user in Signitic and does not retrieve the signature already present in Odoo.

Before you start

You must have:

  • administrator access to the Signitic workspace;

  • the Premium destination connectors add-on;

  • the HTTPS URL of your Odoo instance, without trailing slash;

  • the name of the Odoo database;

  • an API key authorized to read users and modify their signature;

  • the Odoo identifier if you are using Odoo 16 to 18.

The correspondence between Odoo and Signitic is based on the user's primary or secondary email address. No Signitic user is created automatically.

Connect Odoo

  1. Open Settings > Connectors > Available in your Signitic account.

  2. Open the Odoo card.

  3. Enter the HTTPS URL of the instance, the API key, and the database name.

  1. Enable I use Odoo 18 or an earlier version for Odoo 16 to 18, then enter the Odoo identifier.

  2. Click Connect.

Signitic tests reading a first user res.users. If the test succeeds, the connector is registered and user synchronization is started.

Choose the API mode

Odoo 19 and later: leave the Odoo 18 or earlier option disabled. Signitic uses the JSON-2 API with a Bearer API key and database header.

Odoo 16 to 18: enable the Odoo 18 or earlier option. Signitic uses JSON-RPC and requires the database, Odoo ID, and API key.

User synchronization

When signatures are pushed, only active Signitic users are affected. The HTML generated by Signitic then replaces the Odoo signature.

Multiple Odoo connectors can be configured in the same account. Each combination of instance URL + database is independent and the database is displayed on the connector card. A combination already in use cannot be added a second time.

Important

The connection test only verifies reading an Odoo user. It does not guarantee that the API key can write to res.users.signature. If the connection succeeds but signatures are not updated, check the API key's write permissions and email association.

If you already have a signature, be careful as it will be overwritten by the new one.

Frequently asked questions

Why does the Odoo connection fail?

Check the HTTPS URL, database name, selected version mode, Odoo identifier for versions 16 to 18, and API key permissions.

Does the connector create missing users in Signitic?

No. The user must already exist in the Signitic workspace and their email address must match the one in Odoo.

Does the test verify signature writing?

No. It only verifies reading a res.users user. The key must also be able to modify the res.users.signature field for the push to work.

How do I modify the API key or database?

Credentials cannot be modified on an installed connector. Delete the connector and then recreate it with the new parameters.

Did this answer your question?
😞
😐
😁