Apps › Sell online and connect platforms

Listmonk Connector

Listmonk's lists and subscribers come into Odoo's Email Marketing, and with opt-out sync on, an unsubscribe on one side becomes an opt-out on the other.

Open the live demo Read the manual

Odoo 16Odoo 17Odoo 18Odoo 19Odoo 20

A Listmonk instance in Odoo: the server's address, the API user and token fields and the state, next to the health block and the tabs Safety, Import and Opt-out / Compliance
A Listmonk instance in Odoo: the server's address, the API user and token fields and the state, next to the health block and the tabs Safety, Import and Opt-out / Compliance
Runs onOdoo 16 to 20Community or Enterprise, self-hosted or Odoo.sh
NeedsEmail Marketingno 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.12bambooforge_listmonk_connector

141 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 Listmonk server, dry-run first

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

  1. In Odoo: Listmonk Connector > Configuration > Instances > New. Enter the server's address, the API user and its token.
  2. Press Test Connection. The state turns Connected.
  3. On the Import tab, set Import Subscribers Limit above your number of subscribers, then press Queue List Import and Queue Subscriber Import.
  4. Read Operations > Logs and Validation Results, untick Dry Run Mode and import again, lists first.
The Listmonk instance form with the server's address, the API user fields and the state
Flow 02

Lists and subscribers come into Email Marketing

Each Listmonk record lands where Odoo sends from.

  1. A list becomes a mailing list with its Listmonk id, type, opt-in mode and subscriber count.
  2. A subscriber becomes a mailing contact with its name, e-mail and status, on the imported lists it is on.
  3. Each import writes Listmonk's name and e-mail again, and adds list links; it removes none.
Flow 03

Opt-outs travel both ways

Switched on per instance, on the Opt-out / Compliance tab.

  1. Tick Sync Opt-out / Suppression; keep Use Email Blacklist for an address-wide stop.
  2. A subscriber Listmonk shows disabled, blocklisted or unsubscribed from a list is opted out of every list in Odoo at its import, and blacklisted.
  3. An opt-out or a blacklist entry made in Odoo queues a push: the subscriber is blocklisted in Listmonk, or its lists are unsubscribed and added back as Odoo keeps them.
  4. A newer Odoo opt-out wins over an enabled subscriber, and is pushed again.
Flow 04

A failed job lands in a list, not in silence

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.

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.