Apps › Sell online and connect platforms

NocoDB Connector

NocoDB's bases and tables come into Odoo as a catalog with their row counts, and Row Sync binds one NocoDB table to one Odoo model so that rows and records follow each other, one way or both.

Open the live demo Read the manual

Odoo 16Odoo 17Odoo 18Odoo 19Odoo 20

A NocoDB instance in Odoo: the server's address, the API token sent as xc-token, the API path api/v2 and the state Connected, next to the health block and the tabs Safety, Import, Reconciliation, Webhook and Monitoring
A NocoDB instance in Odoo: the server's address, the API token sent as xc-token, the API path api/v2 and the state Connected, next to the health block and the tabs Safety, Import, Reconciliation, Webhook and Monitoring
Runs onOdoo 16 to 20Community or Enterprise, self-hosted or Odoo.sh
NeedsOdoo onlyno Enterprise module
Price89 EURone-time, per series, on the Odoo Apps Store
Demodemo20.bambooforge.devlogin page already filled in
Supportsupport@bambooforge.devfirst reply within one business day
Version20.0.1.0.15bambooforge_nocodb_connector

123 automated checks run before every release of this app, the same suite on every series it ships for. The complete list is in the source you receive; run it yourself with --test-enable.

How you use it

Four flows, in the order you will meet them

Flow 01

Connect: one instance per NocoDB server, dry-run first

Test Connection proves the address and the token, and the first import writes nothing.

  1. In Odoo: NocoDB Connector > Configuration > Instances > New. Enter the server's address and an API token.
  2. Press Test Connection. The state turns Connected.
  3. On the Import tab press Queue Base Import, then Queue Table Import.
  4. Read Operations > Logs, untick Dry Run Mode and import again, bases first.
The NocoDB instance form: the server's address, the API token, the API path api/v2, the state Connected and the Safety tab with Dry Run Mode
Flow 02

Bases and tables, with their row counts

Odoo's copy of NocoDB's names, ids and row counts, searchable and grouped.

  1. Imported Data > Bases lists each base with its NocoDB id and its number of tables.
  2. Imported Data > Tables lists each table with its base, physical name, row count and NocoDB id.
  3. A row count is NocoDB's total for the table at its last import; the list sums them.
The Tables list: 13 tables of three bases, each with its physical name, row count and NocoDB id, 884 rows in all
Flow 03

Row Sync: one NocoDB table, one Odoo model

A Settings administrator makes the mapping under Configuration > Row Sync; nothing moves before.

  1. Pick an imported table, an Odoo model, a direction (Import, Export or Bidirectional) and a key column with its Odoo field.
  2. On the Field Mappings tab, list the columns and the Odoo fields they fill.
  3. Press Run Now in dry-run: the notification says what the run would create and update.
  4. Tick Run on Schedule: the NocoDB Row Sync action queues the mapping every 15 minutes.
Flow 04

A failed job lands in a list

Every job is retried, set aside after its last try, and shown with its error.

  1. Open the Control Tower: one card per instance with its backlog, dead letters and conflicts.
  2. Open Dead-letter, fix the cause the error names, select the jobs and use Requeue Jobs.
  3. For Row Sync, Operations > Logs names each row and record that failed, and each pair changed on both sides.

Price and where to buy

89 EUR, one payment per Odoo series, on the Odoo Apps Store. Pick your series:

Twelve months of support by the people who wrote the code; bug fixes and improvements within the series free for as long as it is published. Report a bug within two months of purchase and, if it is not resolved within fifteen days, you get a full refund. Full source under OPL-1, no licence key, no phone-home. The whole promise.