Send a WhatsApp Message for a New Exact Online Invoice
Exact Online is the accounting package of choice for many small businesses in Belgium and the Netherlands. When an invoice is sent or paid, it generates an email by default — if that doesn't already end up in the customer's spam folder. WhatsApp, on the other hand, gets read right away. With Zapier or Make you can connect any invoice status in Exact Online to a WhatsApp message through the TextMeFlow API, without writing code yourself or wading through Exact's own API documentation.
This article shows the setup for two concrete triggers: a sent invoice and a payment confirmation. The same pattern works for reminders when a due date is approaching or a notification for a new quotation.
Why not straight from Exact Online
Exact Online has its own REST API and can send webhooks to your own endpoint, but that requires you to build a piece of server yourself that receives that payload, validates it and turns it into a WhatsApp message — plus maintenance with every change to Exact's API. Zapier or Make avoid that: both have an official Exact Online connector with ready-made triggers ("New Sales Invoice", "Invoice Paid"), and you only map the fields to the WhatsApp action.
Step 1: connect Exact Online in Zapier or Make
In Zapier you create a new Zap with Exact Online as the trigger app and sign in with your Exact account. Pick the trigger that fits your use case:
- New Sales Invoice — send a notification as soon as an invoice is finalized and sent.
- Invoice Paid — confirm receipt of a payment.
In Make.com the same step is called a "Watch" trigger within the Exact Online module; you pick the document type (SalesInvoice) and the status field that determines the trigger.
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": "{{klant_telefoon}}",
"text": "Hi {{klant_naam}}, your invoice {{factuurnummer}} ({{bedrag}}) has been sent. Due date: {{vervaldatum}}.",
"media_url": "{{factuur_pdf_url}}"
}
With the optional media_url field you send the invoice PDF along directly as an attachment, up to 100 MB — handy so the customer doesn't have to log in to a customer portal separately to find the document. The full API specification, including response codes, is at /en/docs/api.
Step 3: normalize phone numbers
Exact Online stores phone numbers the way they were once entered: 0470 12 34 56, with country code, without country code, with spaces. 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 contact's mobile number if it's filled in, otherwise falls back to the landline;
- replaces a leading
0with+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 notifications
An invoice in Exact Online can be edited several times before it's finally sent, and every intermediate save can fire a trigger like "New Sales Invoice" again if your filter is too broad. Limit the Zap or scenario to the exact status transition (for example "status = sent" instead of "record changed"), and add a filter step that blocks repeated runs on the same invoice number within 24 hours.
These messages are transactional and one-to-one — an invoice notification, a payment confirmation. This pattern isn't suitable for bulk sending to an entire customer list: 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 invoice that triggers a WhatsApp notification within seconds of being sent, a payment that immediately produces a confirmation — all without anyone having to write the message by hand or the customer having to check an email they won't open anyway. 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 "Invoice Paid" — and only expand once it runs stably. Start free on TextMeFlow: 50 messages a month, forever, enough to build and test the complete Exact Online 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