# Send WhatsApp messages (Zender plugin) \[Free\] now recieve messages

**URL:** <https://forum.mautic.org/t/send-whatsapp-messages-zender-plugin-free-now-recieve-messages/32774>\
**Category:** 3rd Party Addons\
**Created:** [July 16, 2024, 4:17am UTC](https://forum.mautic.org/t/send-whatsapp-messages-zender-plugin-free-now-recieve-messages/32774 "2024-07-16T04:17:56Z")\
**Posts on this page:** 15\
**Page:** 1

<div class="post-metadata">

**Author:** ![rcarabelli](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/rcarabelli/32/6807_2.png) [@rcarabelli](https://forum.mautic.org/u/rcarabelli)\
**Post date:** [July 16, 2024, 4:17am UTC](https://forum.mautic.org/t/send-whatsapp-messages-zender-plugin-free-now-recieve-messages/32774/1 "2024-07-16T04:17:56Z")

</div>

The new version of Mautic Plugin for Zender is free to be downloaded, find it at:  
[https://github.com/rcarabelli/Mautic-Zender-Plugin/tree/v1.1.14](https://github.com/rcarabelli/Mautic-Zender-Plugin/tree/v1.1.14)

This new version connects to Zender API thus let you fetch all messages you have already sent, the status (failed, successful/sent) and saves in a Mautic DB all JSONs of every API call, giving you the option to build reports.  
Also it let’s you fetch the recieved answers. YES! the answers clients/users give you via WhatsApp.

Also, it saves in the leads table the last event per user regarding sent or recieved WhatsApp messages, so you can use them to create segments or events.

Hope you enjoy this new release and please, I am open to suggestions.

Next step: AI to rewrite outgoing messages (more personalization), fetch received messages and errors sending as the event happens and **if someone helps me to understand how, auto answer on received messages.**

Please, let me know if there is something else you would like or if you need some help configuring this or a Zender installation. We can provide with a Zender server so you don’t have to have your own or other configuration/installation/marketing services.

Regards,

Renato

(release post of previous plugin is in here: [Send WhatsApp messages (Zender plugin) [Free]](https://forum.mautic.org/t/send-whatsapp-messages-zender-plugin-free/32494))

---

<div class="post-metadata">

**Author:** ![alexzlobin](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/alexzlobin/32/13606_2.png) [@alexzlobin](https://forum.mautic.org/u/alexzlobin)\
**Post date:** [December 26, 2025, 2:28pm UTC](https://forum.mautic.org/t/send-whatsapp-messages-zender-plugin-free-now-recieve-messages/32774/2 "2025-12-26T14:28:47Z")

</div>

It works on 5.2.x but not working on 6.x:(

---

<div class="post-metadata">

**Author:** ![rcarabelli](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/rcarabelli/32/6807_2.png) [@rcarabelli](https://forum.mautic.org/u/rcarabelli)\
**Post date:** [December 26, 2025, 4:26pm UTC](https://forum.mautic.org/t/send-whatsapp-messages-zender-plugin-free-now-recieve-messages/32774/3 "2025-12-26T16:26:07Z")

</div>

Version in main now supports 6.0.x

> **[GitHub - rcarabelli/Mautic-Zender-Plugin: Plugin to use Mautic with Zender to send WhatsApp...](https://github.com/rcarabelli/Mautic-Zender-Plugin)**
>
> Plugin to use Mautic with Zender to send WhatsApp messages

Have tried up to 6.0.6

If still doesn’t work, let me know and I’ll send you a version through this forum… but currently I am using the same version in main, so will be sending you the same file.

---

<div class="post-metadata">

**Author:** ![alexzlobin](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/alexzlobin/32/13606_2.png) [@alexzlobin](https://forum.mautic.org/u/alexzlobin)\
**Post date:** [December 26, 2025, 7:40pm UTC](https://forum.mautic.org/t/send-whatsapp-messages-zender-plugin-free-now-recieve-messages/32774/4 "2025-12-26T19:40:48Z")

</div>

Hello Renato  
I know about version 1.1.2 — it works on Mautic 6.0.x, but it doesn’t support the receiving function like version 1.1.14 does.  
There are already some automations that we use for our companies, so we have to stay on Mautic 5.2.x. and plugin v1.1.14

---

<div class="post-metadata">

**Author:** ![rcarabelli](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/rcarabelli/32/6807_2.png) [@rcarabelli](https://forum.mautic.org/u/rcarabelli)\
**Post date:** [December 26, 2025, 8:11pm UTC](https://forum.mautic.org/t/send-whatsapp-messages-zender-plugin-free-now-recieve-messages/32774/5 "2025-12-26T20:11:09Z")

</div>

TBH, I can’t remember that function, did that code too many months ago… if you help me remember I’ll be happy to implement that in mautic’s 5 version.

Maybe in the github documentation is something.

---

<div class="post-metadata">

**Author:** ![alexzlobin](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/alexzlobin/32/13606_2.png) [@alexzlobin](https://forum.mautic.org/u/alexzlobin)\
**Post date:** [December 27, 2025, 5:26pm UTC](https://forum.mautic.org/t/send-whatsapp-messages-zender-plugin-free-now-recieve-messages/32774/6 "2025-12-27T17:26:17Z")

</div>

Your plugin version **1.1.14** ([GitHub - rcarabelli/Mautic-Zender-Plugin at v1.1.14](https://github.com/rcarabelli/Mautic-Zender-Plugin/tree/v1.1.14))is already working successfully on **Mautic 5.2.x** — both for **sending and receiving**.

The problem is that plugin version **1.1.2** ( [GitHub - rcarabelli/Mautic-Zender-Plugin: Plugin to use Mautic with Zender to send WhatsApp messages](https://github.com/rcarabelli/Mautic-Zender-Plugin/tree/main)), which is officially marked as compatible with **Mautic 6** , does **not** have the **receive/inbound** functionality. It looks like the code responsible for receiving is missing (or was not included) in that version.

Unfortunately, I’m not a developer, so I can’t implement the missing part myself — but I **can help with testing** on real, live installations.

---

<div class="post-metadata">

**Author:** ![rcarabelli](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/rcarabelli/32/6807_2.png) [@rcarabelli](https://forum.mautic.org/u/rcarabelli)\
**Post date:** [December 27, 2025, 9:59pm UTC](https://forum.mautic.org/t/send-whatsapp-messages-zender-plugin-free-now-recieve-messages/32774/7 "2025-12-27T21:59:47Z")

</div>

Will take a look at it on Friday. Have already placed in my queue.

Will came back to you once I work in it.

---

<div class="post-metadata">

**Author:** ![alexzlobin](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/alexzlobin/32/13606_2.png) [@alexzlobin](https://forum.mautic.org/u/alexzlobin)\
**Post date:** [January 12, 2026, 2:32pm UTC](https://forum.mautic.org/t/send-whatsapp-messages-zender-plugin-free-now-recieve-messages/32774/8 "2026-01-12T14:32:48Z")

</div>

Hi

Did you check it?

---

<div class="post-metadata">

**Author:** ![rcarabelli](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/rcarabelli/32/6807_2.png) [@rcarabelli](https://forum.mautic.org/u/rcarabelli)\
**Post date:** [January 12, 2026, 3:16pm UTC](https://forum.mautic.org/t/send-whatsapp-messages-zender-plugin-free-now-recieve-messages/32774/9 "2026-01-12T15:16:13Z")

</div>

Hello yes, my team is on it. Will have some news this week.

---

<div class="post-metadata">

**Author:** ![rcarabelli](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/rcarabelli/32/6807_2.png) [@rcarabelli](https://forum.mautic.org/u/rcarabelli)\
**Post date:** [January 29, 2026, 5:45am UTC](https://forum.mautic.org/t/send-whatsapp-messages-zender-plugin-free-now-recieve-messages/32774/10 "2026-01-29T05:45:55Z")

</div>

Hi Alex — sorry for the delay.

You’re right: **the current “Mautic 6 compatible” plugin branch does not include inbound/receive handling**. I reviewed older revisions and there are only **partial / unfinished experiments** , not a complete inbound implementation.

**Inbound is absolutely doable** , but there are two different “inbound” goals people usually mean, and the implementation depends on which one you need:

1. **Capture inbound messages and store them in Mautic** (log them, attach to the contact, keep the conversation history).

2. **Use inbound messages to trigger automation** (keyword triggers, “reply with 1/2/3”, capture data like name/email, etc.).

Zender already stores inbound messages and provides **API + webhook** , so the missing part is not “getting the message”, it’s **how we map inbound events into Mautic** in a useful way (and without duplicating Zender as a database of record).

* * *

If you share your use case, I can **evaluate the best approach** and see whether it makes sense to add inbound support (and in what scope). A few quick questions to understand what you actually need:

- Do you need **automation triggers** , **message logging** , or both?

- Is **webhook delivery** available in your setup, or would you prefer a **polling/cron sync** approach?

- How do you identify the contact: **phone only** , or do you also rely on a custom field like `id_whatsapp_in_zender`?

- What’s the **minimum viable behavior** you’d want first (e.g., “log inbound + tag contact when message contains keyword X”)?

Once I have that context, I can **outline a possible implementation path** and you can help validate it with testing on a live installation.

* * *

Inbound can be approached in two ways: **(1) webhook-based** (real-time) or **(2) cron/polling** (periodic sync).

Either way, the flow is: **receive message → normalize sender phone (E.164) → match a Mautic contact → log/update contact fields → optionally trigger automation** (tags/segments/campaign logic).

The main design choice is whether you want **simple logging** or **automation triggers** (keyword/reply-driven).

We can keep it minimal (store only “last inbound message/date” + tags) to avoid duplicating Zender as the system of record.

Again, your use case is needed so I can recommend which path fits your setup best.

* * *

---

<div class="post-metadata">

**Author:** ![rcarabelli](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/rcarabelli/32/6807_2.png) [@rcarabelli](https://forum.mautic.org/u/rcarabelli)\
**Post date:** [January 29, 2026, 6:03am UTC](https://forum.mautic.org/t/send-whatsapp-messages-zender-plugin-free-now-recieve-messages/32774/11 "2026-01-29T06:03:09Z")

</div>

I want to add a bit more context on what I mean by “use case”, because it’s the difference between “receiving messages” and “receiving messages that actually create value inside Mautic”.

A good example is another plugin I built: **7 Cats – Shopping2Mautic**.

**Concrete use case (very clear):**

- When a customer places an order in WooCommerce (or when orders are imported from Magento), the plugin pushes that event into Mautic by **creating/updating the contact** and enriching it with **purchase intelligence**.

- Mautic ends up “knowing” things like: **last order date, last order amount, last order status, lifetime revenue, lifetime order count, purchase frequency, last order categories, and last order items (as JSON)**.

- With that data, you can build campaigns like:

- Optionally, the plugin can also send **WhatsApp notifications via Zender** , and store each payload to a **file channel** for auditing.

That is a _complete_ use case: **event → data model → Mautic fields → segmentation → automation outcomes**.

So for inbound WhatsApp in the Zender plugin, I’m looking for the same clarity. “Receive messages” alone is not the goal; the goal is **what you want Mautic to do with those inbound messages**.

Documentation / README here: [GitHub - rcarabelli/7-Cats-Woocommerce-to-Mautic-Plugin: Wordpress plugin to send Woocommerce purchase info to Mautic in a way ready for campaigns.](https://github.com/rcarabelli/7-Cats-Woocommerce-to-Mautic-Plugin)

---

<div class="post-metadata">

**Author:** ![alexzlobin](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/alexzlobin/32/13606_2.png) [@alexzlobin](https://forum.mautic.org/u/alexzlobin)\
**Post date:** [January 29, 2026, 9:17pm UTC](https://forum.mautic.org/t/send-whatsapp-messages-zender-plugin-free-now-recieve-messages/32774/12 "2026-01-29T21:17:25Z")

</div>

In Mautic 5 we had fields (I may be slightly off on the exact names) like **“last message date”** and \*\*“last message text.”\*\*We used this in Mautic for a hotel workflow: we would send a WhatsApp message to the customer to confirm an action — for example **parking** or confirming some other request.

Because those values were stored as **custom contact fields** , we could build **segments** based on the message content using **regular expressions**. That made the scenario quite flexible: you can drive different automations depending on what the inbound message contains, and when it arrived.

---

<div class="post-metadata">

**Author:** ![rcarabelli](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/rcarabelli/32/6807_2.png) [@rcarabelli](https://forum.mautic.org/u/rcarabelli)\
**Post date:** [January 30, 2026, 3:45pm UTC](https://forum.mautic.org/t/send-whatsapp-messages-zender-plugin-free-now-recieve-messages/32774/13 "2026-01-30T15:45:31Z")

</div>

I like that idea but we have an issue with that, I mean, probably 30% of the persons tend to write in multi messages, like

- Message 1: ”Yes”…
- Message 2: ”Option 3”
- Message 3: “Thanks”

And that will save only the last message, only if we use whatsapp buttons that can be prevented in most of the cases.

This behavior might break the usage, because you won’t have the correct, we have several ways to handle this:

1. Make a middleware to better process from Zender’s database directly or from all messages sent from zender via hooks when there is an incoming message, we do this all the time, mostly with WABA but works with Zender. Just define the rules, and when an event happens, then this middleware will send the correct payload to Mautic
2. Enhance a bit the plugin with the capability of processing several messages from the same WA number in a definied short range of time, like “all messages sent by a lead in the last 30 seconds” and find in it the data you are looking for… or even send instructions via API to an AI tool including the outbound messages + all the inbound package to make AI decide what’s the correct answer

In any case, yes, I can do what you are asking for, get and insert the last inbound message from a WA number, and just update the field or have a JSON that instead of updating the field will add content to the JSON in the field, but I think that will generate a lot of errors.

Probably I am wrong somewhere, your feedback is needed.

Adding a note: We can add a JSON will all answers from the lead since the last message from the brand.

---

<div class="post-metadata">

**Author:** ![alexzlobin](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/alexzlobin/32/13606_2.png) [@alexzlobin](https://forum.mautic.org/u/alexzlobin)\
**Post date:** [February 2, 2026, 1:59pm UTC](https://forum.mautic.org/t/send-whatsapp-messages-zender-plugin-free-now-recieve-messages/32774/14 "2026-02-02T13:59:47Z")

</div>

With this approach, unlike the official WhatsApp integration, we can’t use interactive buttons. Links are still possible, but we need to test them — in practice, only a small percentage of users actually click.

One more idea is to store not just the last message, but a few recent ones so there’s a short conversation history.

This solution won’t realistically scale beyond roughly 3,000 WhatsApp contacts, so the load should remain low — even if we store 4–5 recent messages per contact in the Mautic database.

---

<div class="post-metadata">

**Author:** ![rcarabelli](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/rcarabelli/32/6807_2.png) [@rcarabelli](https://forum.mautic.org/u/rcarabelli)\
**Post date:** [February 2, 2026, 2:50pm UTC](https://forum.mautic.org/t/send-whatsapp-messages-zender-plugin-free-now-recieve-messages/32774/15 "2026-02-02T14:50:39Z")

</div>

How can we save the last “x” messages in a field in the table?  
Like a json? 5 fields to keep it extra clean, 1 field per message?

Probably we will need the last message sent by us (datetime included) + the last 5 messages we got from the lead (but only the ones that are after our last sent message)

Then we can decide what to do with all that information.

Is that right?
