12 hours ago, Magd Almuntaser said:

Can someone here list the problems currently existing in MPWA 12.0.1?

I will start by fixing the issues first, any feature requests should be mentioned later, after we finish resolving the core problems and upgrading the libraries.

Thank you all for your patience

Main core issues that I am experiencing:

1. Connection:
   a. Sometimes, when linking an account on a different number, the MPWA status shows as connected, but on the user's phone it keeps loading until it eventually displays:
   "Couldn't link device. Something went wrong, please try again." This keeps happening repeatedly.

   b. Sometimes the WebSocket connection suddenly fails, even though it was previously normal and the node status is still running. The MPWA node app needs to be restarted first before it works normally again (case with aaPanel).

2. Webhook:
   a. Sometimes messages cannot be sent/replied to via the webhook because, upon inspection, some webhook payloads contain a from value that uses a LID instead of a phone number. As a result, messages cannot be sent/replied to if the from value is not a phone number (so it may require resolving something like LidToPhone). This might also be the reason why messages sometimes appear on the phone but do not enter live chat.

   b. The webhook sometimes returns a duplicate payload, with one of the payloads looking like this:

{
  "message": "",
  "bufferImage": null,
  "from": "190116794812130",
  "name": "John Doe",
  "participant": "[email protected]",
  "data": {
    "key": {
      "remoteJid": "190116794812130@lid",
      "fromMe": false,
      "id": "AC79B58E31A6170305DF2D3663BF84F1",
      "senderPn": "[email protected]"
    },
    "messageTimestamp": 1770012201,
    "pushName": "John Doe",
    "broadcast": false,
    "messageStubType": 2,
    "messageStubParameters": [
      "No matching sessions found for message"
    ]
  }
}

This is not really a problem if our webhook app already filters out payloads like this, but if it does not, then automated reply messages may also be duplicated.

Edited February 28Feb 28 by utm
additional description clearance

We need to implement the following upgrades and fixes in the system. Please review the points carefully and prioritize accordingly:

1. Add Group Chat Operations

   • Enable full group chat management features (create, manage, send/receive messages, etc.).

   • Ensure smooth handling of group messages through both panel and API.

2. Campaign Module Issues

   • Fix the Pause button (currently not functioning).

   • Fix the View button (not opening campaign details properly).

3. Template Video Sending Issue

   • Resolve the problem where videos are not being sent properly through message templates.

   • Ensure video templates work correctly across all supported devices.

4. API Enhancement – Send Template with Normal Message

   • Update the API to allow sending a template message along with a normal text message in a single request.

5. Subscription Plan Feature Allocation Issue

   • Currently, when a user subscribes to a plan and we manually allocate additional features, the system removes existing features and reassigns only plan-based features.

   • This must be fixed so that manually added features remain intact and merge properly with plan features instead of overwriting them.

6. Cron Job Page Improvements

   • Add functionality to:

     • Set a cron job on button click.

     • Remove a cron job on button click.

   • Integrate cron job creation using cron-job.org (as it is completely free).

   • Ensure proper status tracking (active/inactive).

7. Additional Feature Enhancements

   • Contact import/export functionality.

   • Invoice auto-generation system.

   • Payment reminder email automation.

   • Auto-reply workflow builder (drag & drop).

   • Keyword-based automation.

   • Chatbot flow builder.

   • Drip campaign automation.

   • Conditional message triggers (if/else logic).

   • When a message cannot be sent due to a disconnected device, trigger an automatic email notification to the user.

   • Queue operations (queue management, retry logic, and monitoring dashboard).

8. Reference for Implementation

   • Please review Maytapi for inspiration regarding API structure and feature handling.

Kindly provide an estimated timeline for completion of these updates. Let me know if any clarification is required.

Misi sedulur, ada yang tau parameter quote di dalam grup?
saya pakai "msgid" tidak bisa, itu sepertinya hanya berlaku untuk japri saja.

On 27/2/2026 at 18.59, Magd Almuntaser said:

Bisakah seseorang di sini mencantumkan masalah-masalah yang saat ini ada di MPWA 12.0.1?

Saya akan mulai dengan memperbaiki masalah terlebih dahulu, permintaan fitur apa pun akan dibahas kemudian, setelah kita selesai menyelesaikan masalah inti dan meningkatkan pustaka.

Terima kasih atas kesabaran Anda semua.

Tidak bisa menjalankan kampanye dalam waktu bersamaan, status akan terus pending tidak terkirim

8 hours ago, MD Raditya said:

Misi sedulur, ada yang tau parameter quote di dalam grup?
saya pakai "msgid" tidak bisa, itu sepertinya hanya berlaku untuk japri saja.

kalau ada bahanya coba sini saya test

udah lama gk join, udh 319 page aja,

Okay, I've reviewed the old and new pages and received all your messages.

about the new features, they will be postponed.
As for the fixes, that's my main focus.

Version 13.0.0, which will contain many modifications and fixes (not features), will be released today or tomorrow.
The libraries have been updated, including Baileys, and all (Node codes) has been changed to the ESM system.

After version 13.0.0, I will implement some actual improvements, such as reducing the number of commands in the database and modifying the cronjob to use the default Laravel and more..

1 hour ago, Magd Almuntaser said:

Baik, saya sudah meninjau halaman lama dan baru serta menerima semua pesan Anda.

Mengenai fitur-fitur baru, itu akan ditunda.
Sedangkan untuk perbaikan bug, itu fokus utama saya.

Versi 13.0.0 , yang akan berisi banyak modifikasi dan perbaikan (bukan fitur), akan dirilis hari ini atau besok.
Pustaka telah diperbarui, termasuk Baileys, dan semua (kode Node) telah diubah ke sistem ESM.

Setelah versi 13.0.0 , saya akan menerapkan beberapa peningkatan nyata, seperti mengurangi jumlah perintah dalam basis data dan memodifikasi cronjob untuk menggunakan Laravel default dan banyak lagi.

Thanks Dev..❤️

8 hours ago, Magd Almuntaser said:

Okay, I've reviewed the old and new pages and received all your messages.

about the new features, they will be postponed.
As for the fixes, that's my main focus.

Version 13.0.0, which will contain many modifications and fixes (not features), will be released today or tomorrow.
The libraries have been updated, including Baileys, and all (Node codes) has been changed to the ESM system.

After version 13.0.0, I will implement some actual improvements, such as reducing the number of commands in the database and modifying the cronjob to use the default Laravel and more..

Thanx u Sir

I’d like to share some feedback based on my experience using MPWA. Hopefully this can help improve the platform going forward:

Fixes (Bugs & Security)

1. Potential security risk via File Manager (malicious file upload)
Currently, there is a potential security risk where users can upload harmful files (e.g., malicious scripts) through the file manager.
👉 Suggestions:

• Restrict allowed file types (whitelist: .jpg, .png, pdf, txt, etc.)

• Block executable/script files (.php, .js, .exe, .sh, etc.)

• Add MIME type validation + basic malware scanning

2. AI Bot context mixing between different accounts
I’ve encountered cases where:

• Account A uses the system prompt/instructions from Account B
  This is risky and can cause wrong AI responses and potential data/context leakage between users.
  👉 Suggestions:

• Ensure strict isolation of AI context per account/device/session

• Reset AI memory when switching accounts/sessions

• Add logging/tracing to detect context leakage

Feature Requests

1. AI Bot response delay
To make replies feel more natural (less “bot-like”):

• Configurable delay (e.g., 3–10 seconds)

2. Update Gemini AI model
Currently, Gemini models are only available up to version 2.5.
👉 Suggestion:

• Add support for the latest Gemini models

3. Scheduled auto follow-up
This would be very useful for sales & customer support workflows:

• Automatic follow-up on Day +1 if there is no reply

• Reminder on Day +3

• Customizable follow-up templates

• Enable/disable per campaign

Thanks a lot! 🙌

I haven’t used the script for a long time, but I plan to install version 13 when it is released and start using it again.
I would like to ask the experts: is there any ban related to sending campaigns, and how can I avoid it?

On 3/1/2026 at 6:46 PM, Magd Almuntaser said:

Okay, I've reviewed the old and new pages and received all your messages.

about the new features, they will be postponed.
As for the fixes, that's my main focus.

Version 13.0.0, which will contain many modifications and fixes (not features), will be released today or tomorrow.
The libraries have been updated, including Baileys, and all (Node codes) has been changed to the ESM system.

After version 13.0.0, I will implement some actual improvements, such as reducing the number of commands in the database and modifying the cronjob to use the default Laravel and more..

@Magd Almuntaser 



Waiting for the update........??

33 minutes ago, jjsons said:

@Magd Almuntaser 



Waiting for the update........??

Waitin since yesterday but still not rolling up

Waiting for the update........?? when isit dropping

On 3/1/2026 at 7:16 PM, Magd Almuntaser said:

Okay, I've reviewed the old and new pages and received all your messages.

about the new features, they will be postponed.
As for the fixes, that's my main focus.

Version 13.0.0, which will contain many modifications and fixes (not features), will be released today or tomorrow.
The libraries have been updated, including Baileys, and all (Node codes) has been changed to the ESM system.

After version 13.0.0, I will implement some actual improvements, such as reducing the number of commands in the database and modifying the cronjob to use the default Laravel and more..

Please also fixed why name variable is not working in campaign please fixed it in next version if possible Thanks 🙏

@Magd Almuntaser

Waiting for the New Updated Version.... Please release it soon as possible Thanks 🙏 @Magd Almuntaser

Edited March 5Mar 5 by Rahman Khan

@Magd Almuntaser

Thanks for the effort to resolve the bugs and to make the application seamless. We await the updated version.

On 2/27/2026 at 5:29 PM, Magd Almuntaser said:

the

share .env fill file share any one please

Version 13.0.0 has been released

What's new in version 13.0.0:

- Added Image Inputs In Buttons & Lists Messages (Mandatory).
- Fixed List Message (AutoReply Page).
- Fixed Campaign Queue.
- Fixed System Instraction (AI).
- Fixed The LID Problem.
- Fixed Vulnerability In Laravel File Manager.
- Converted Node Libraries To ESM.
- Updated Api-Docs (Buttons & Lists).
- Updated Node Libraries.
- Updated Vendor Libraries.
- Updated AI Models List.

37 minutes ago, Magd Almuntaser said:

Version 13.0.0 has been released

What's new in version 13.0.0:

- Added Image Inputs In Buttons & Lists Messages (Mandatory).
- Fixed List Message (AutoReply Page).
- Fixed Campaign Queue.
- Fixed System Instraction (AI).
- Fixed The LID Problem.
- Fixed Vulnerability In Laravel File Manager.
- Converted Node Libraries To ESM.
- Updated Api-Docs (Buttons & Lists).
- Updated Node Libraries.
- Updated Vendor Libraries.
- Updated AI Models List.

wah makasi bang, akhirnya LID di fixing ❤️❤️❤️

Thanks 🙏 @Magd Almuntaser for the updates... 💕

46 minutes ago, Magd Almuntaser said:

Version 13.0.0 has been released

What's new in version 13.0.0:

- Added Image Inputs In Buttons & Lists Messages (Mandatory).
- Fixed List Message (AutoReply Page).
- Fixed Campaign Queue.
- Fixed System Instraction (AI).
- Fixed The LID Problem.
- Fixed Vulnerability In Laravel File Manager.
- Converted Node Libraries To ESM.
- Updated Api-Docs (Buttons & Lists).
- Updated Node Libraries.
- Updated Vendor Libraries.
- Updated AI Models List.

Alhamdulillah..yeaay..❤️❤️❤️❤️

1 hour ago, Magd Almuntaser said:

Version 13.0.0 has been released

What's new in version 13.0.0:

- Added Image Inputs In Buttons & Lists Messages (Mandatory).
- Fixed List Message (AutoReply Page).
- Fixed Campaign Queue.
- Fixed System Instraction (AI).
- Fixed The LID Problem.
- Fixed Vulnerability In Laravel File Manager.
- Converted Node Libraries To ESM.
- Updated Api-Docs (Buttons & Lists).
- Updated Node Libraries.
- Updated Vendor Libraries.
- Updated AI Models List.

Thanks alot, pelase see the security :D thanks for your amazing work :DDD

Does anyone have mirror of the update? My speed to download stuck on 10kbps.

On 3/1/2026 at 7:16 PM, Magd Almuntaser said:

Okay, I've reviewed the old and new pages and received all your messages.

about the new features, they will be postponed.
As for the fixes, that's my main focus.

Version 13.0.0, which will contain many modifications and fixes (not features), will be released today or tomorrow.
The libraries have been updated, including Baileys, and all (Node codes) has been changed to the ESM system.

After version 13.0.0, I will implement some actual improvements, such as reducing the number of commands in the database and modifying the cronjob to use the default Laravel and more..

Thanks Dev..❤️

As of now in India, from March 1, 2026, this new rule has come into effect on WhatsApp that if anyone logs in to the web WhatsApp, it will be valid for 6 hours, after that it will be automatically logged out. What solution do you suggest for this?

Edited March 6Mar 6 by Shivendra Kr. Sahu