· 4 min · TextMeFlow Team

Send WhatsApp Messages from Odoo with Zapier or Make

For many small businesses in Belgium and the Netherlands, Odoo is the ERP that runs everything — from sales and invoicing to inventory and CRM, all in one system. What Odoo doesn't have out of the box is a WhatsApp channel to the customer: a confirmed order or a posted invoice generates an email or an internal activity, but not a message on the device your customer actually opens. With Zapier or Make you can connect any Odoo trigger to a WhatsApp message through the TextMeFlow API, without writing a line of code.

This article shows the setup for two concrete triggers: a confirmed sales order and a new lead in the CRM module. The same pattern works for invoice reminders, delivery notifications or appointment confirmations.

Why not straight from Odoo

Odoo does have Automated Actions and webhooks in its own Automation module, but those are built to change internal records or send emails — not to send a formatted HTTP request to an external WhatsApp API. You can build that yourself with a server action in Python, but that takes development work and maintenance with every Odoo upgrade. Zapier or Make avoid that: both have an official Odoo connector with ready-made triggers ("Sale Order Confirmed", "Invoice Posted", "New Lead/Opportunity"), and you only map the fields to the WhatsApp action.

Step 1: connect Odoo in Zapier or Make

In Zapier you create a new Zap with Odoo as the trigger app and enter your instance URL and API credentials. Pick the trigger that fits your use case:

  • Sale Order Confirmed — send an order confirmation as soon as a quotation is converted into an order.
  • Invoice Posted — send an invoice notification with the due date.
  • New Lead/Opportunity — send a welcome message or confirm that you received the request.

In Make.com the same step is called a "Watch records" or "Watch" trigger within the Odoo module; you pick the model (sale.order, account.move, crm.lead) and the field that determines the status.

Step 2: add the WhatsApp action

Add a webhook action (Zapier: "Webhooks by Zapier" → POST; Make: the standard HTTP module) that sends to the TextMeFlow API:

POST https://api.textmeflow.eu/v1/messages
Authorization: Bearer JOUW_API_KEY
Content-Type: application/json

{
  "to": "{{partner_phone}}",
  "text": "Hi {{partner_name}}, your order {{order_reference}} is confirmed. You'll receive an invoice as soon as it's ready. Thanks for your order!"
}

Map the fields from the Odoo trigger (phone number, name, order number, amount, due date) in the body builder of Zapier or Make. The full API specification, including response codes and the optional media_url field for attaching a PDF invoice or photo, is at /en/docs/api.

Step 3: normalize phone numbers

Odoo has both a phone and a mobile field, and contacts are often entered the way the customer gave them: 0470 12 34 56, +32470123456 or without a country code. The TextMeFlow API expects E.164 format (+ followed by country code and number, without spaces or parentheses). Add a Formatter step in Zapier (or a built-in function in Make) that:

  • uses the mobile field if it's filled in, otherwise falls back to phone;
  • replaces a leading 0 with +32 (or your own country code);
  • removes spaces, dots and parentheses.

Messages with a number that is still wrong after normalization are rejected by the API — catch that error with an error-handling step in your Zap or scenario, so a failed send doesn't disappear silently.

Step 4: prevent duplicate or unwanted messages

A trigger like "Invoice Posted" can fire again on every status change of an invoice if your filter is too broad. Limit the Zap or scenario to the exact transition you mean, and add a filter step that blocks repeated runs on the same order or invoice within 24 hours.

These messages are transactional and one-to-one — an order confirmation, an invoice notification. This pattern isn't suitable for bulk sending to an entire customer list (a promotion announcement, for example): that is best handled through a separate opt-in file and falls under the risk score of the anti-spam pipeline, see /en/docs/anti-spam.

What this gives you

An order that triggers a WhatsApp confirmation right away, an invoice that sends a notification within seconds of being posted, a new lead that immediately receives an acknowledgement — all without anyone having to write the message by hand. Every message runs through the same pipeline as every other TextMeFlow integration: rate limiting, risk score, automatic STOP handling and quiet hours, so you don't have to configure anything extra yourself.

Start with one trigger — for example "Sale Order Confirmed" — and only expand once it runs stably. Start free on TextMeFlow: 50 messages a month, forever, enough to build and test the complete Odoo integration before you move to a paid plan.

Want to send WhatsApp messages via API yourself?

Free forever up to 50 messages/month. Scan a QR and send your first message within 5 minutes.

Free forever