View File

Whatsapp Gateway | Multi Device

---

This script has been completely modified and many important features and fixes have been added by @Magd Almuntaser
He is now responsible for the updates of this script and has full intellectual property rights
So no one will violate the terms of use that he has set

Latest Features:
1. WhatsApp Account Connectivity

All types of WhatsApp Accounts to be able to connect with WhatsApp Gateway (Multi Number & Multi Device);
Ease of the WhatsApp Account connectivity process with a QRcode Scan or with an Authentication Code directly from your device.

2. Message

Availability of various types of (text messages, media, polls, lists, locations, VCard) can easily be used by you;
You can send mass messages for your marketing campaign activities, promotions or business programs easily and on a scheduled basis;
Setup automatic message replies with more natural (alami) and selected keywords for operational optimization of use;
Manage sent message history with automatic and scheduled deletions.

4. Integration

You can easily integrate your WhatsApp Account with various (AI) artificial intelligence services, namely ChatGPT, DALL-E, Gemini, and Cloude with API authentication codes only;
You can easily activate Ai for Single or Multiple use on your WhatsApp Account;
You can easily select Ai in your WhatsApp messages for WhatsApp Group, Private, or Both types;
You can easily setup call rejection automatically if there is a (Call) call and provide a specific response or information;
Setup your WhatsApp and Ai accounts more naturally (alami) with "Already read" status";
Setup your WhatsApp and Ai accounts more naturally (natural) with the status "Typing...".
You can easily integrate and communicate your services with the Webhook mechanism of WhatsApp Gateway | Multi Device.

5. Application Settings

Nowadays you can easily and quickly carry out the process of setting up the WhatsApp Gateway | Multi Device* application by Magd Almuntaser with the settings panel;
You can easily set up applications based on server ecosystem, smtp, etc quickly;
Multi language support (english, Indonesian, Indian, Spanish and Arabic) for easy use.

6. Developer Options

Currently WhatsApp Gateway | Multi Device* by Magd Almuntaser has provided various API services for your easy development consisting of:
        1). Send Message API
        2). Send Media API
        3). Send Poll API
        4). API Send Button
        5). Send API Templates
        6). Send List message API
        7). Send Location API
        8). Send VCard API
        9). Generate QR API
        10). Disconnect devices
        11). Create User API
        12). User Info API
        13). Device Info API
        14). Check Number API
        15). Webhook Example

Ease of setup and availability of the (API Key) API Key for authentication and authorization of your development process.

7. Security

Currently there is a 2 factor authentication (2FA) service available to maintain the security and comfort of application access;
A password reset service is available if you forget your account login information.


Coming Soon:

1. Landing page for Software as Service services (Subscription Services);
2. Payment gateway page management (QRIS, BCA virtual account, PayPal, Stripe);
3. Added user account management;
4. (ticket) obstacle reporting service for users and managers;
.. And many more.

---

• Submitter
  Magd Almuntaser
• Submitted
  09/03/2024
• Category
  Scripts
• Demo

Update Whatsapp Gateway Multi Device (Magd Version) v8.0.0

Quote

• 31
• 18
• 9
• 3

51 minutes ago, adhiete said:

9.0.1 nya download dimana? di file keknya belum update ya?

Update langsung dari updater-nya bang

1 hour ago, Aidil Aryanto said:

Update langsung dari updater-nya bang

Sipppp, langsung test and ….. Running Well, the campaign has been sent succesfully.

2 hours ago, adhiete said:

9.0.1 nya download dimana? di file keknya belum update ya?

setelah install v9 nanti terus update

When click cronjob menu in application, error like this.
please help

14 minutes ago, adhiete said:

Sipppp, langsung test and ….. Running Well, the campaign has been sent succesfully.

bang barangkali tau cara fixnya

15 minutes ago, Aidil Aryanto said:

bang barangkali tau cara fixnya

Bukannya di halaman sebelah disuruh untuk dm pembuat aplikasinya langsung?

I'm trying the expired status in the user account. in the status view is appropriate. But the device is still connected and can still send messages even though the status has expired. please check mr @Magd Almuntaser

Hello master @magd Almuntaser, if there are 10 users who create a campaign at the same time, will the messages be sent simultaneously at the same time (asynchronously) or in turns/queue?

Atau mungkin teman2 ada yang tahu?

16 minutes ago, badas said:

Bukannya di halaman sebelah disuruh untuk dm pembuat aplikasinya langsung?

Yg dikerjain di hosting 1 ku. Tp sampe sekarang gak bisa ngirim media kalau yg itu.

1 hour ago, pak kacung said:

2 hours ago, adhiete said:

9.0.1 nya download dimana? di file keknya belum update ya?

Aman Om, terimakasih hehee. udah update juga ini.

1 hour ago, Aidil Aryanto said:

bang barangkali tau cara fixnya

Perasaan sudah dibantu kok sama Magd. Ini yang mana lagi?
Itu keluar gitu di menu yang mana dah?
Atau pas ngapain?
Install di apa? OS?

1 hour ago, Jei Grey said:

I'm trying the expired status in the user account. in the status view is appropriate. But the device is still connected and can still send messages even though the status has expired. please check mr @Magd Almuntaser

kalau engga salah ini setiap 10 menit di running sama cronjob. Jadi engga langsung expired. tergantung dari cronjob nya di set berapa menit.
/usr/bin/curl -s "http://webwamu/en/subscription-check" >/dev/null 2>&1
Biasa kalau mau lihat error apa engga nya bisa di -S atau —show-error
kalau di -s itu silent.
Tapi pasti bakal expired kok.

1 hour ago, Ipo Kane said:

Hello master @magd Almuntaser, if there are 10 users who create a campaign at the same time, will the messages be sent simultaneously at the same time (asynchronously) or in turns/queue?

Atau mungkin teman2 ada yang tahu?

If i look at the cronjob and database, it seems the messages will be sent on queue. Except the 10 users create and saving at the same second.
Already try on the scheduled time, three user creating campaign and saving up on the same time 14:15. User A saving is 14:10:36, User B saving is 14:11:29, and User C 14:12:44. The campaign execution ended on User A first, then User B, and last User C.

CMIIW

Edited Thursday at 07:23 AM3 days by adhiete

ada yg bisa bantu instalasi? terima beres nanti ada feenya, boleh langsung DM aja

2 hours ago, badas said:

When click cronjob menu in application, error like this.
please help

Your hosting disable the is_file function The problem is from your hosting, because the cronjob page automatically fetches the correct curl path, so it needs the is_file function to check all paths..

But you can use this without going to the cronjog page in mpwa:

every 1 min
curl -s "http://yoursite.com/en/blast-start" >/dev/null 2>&1

every 1 min
curl -s "http://yoursite.com/en/schedule-run" >/dev/null 2>&1

every 10 min
curl -s "http://yousite.com/en/subscription-check" >/dev/null 2>&1

2 hours ago, Aidil Aryanto said:

bang barangkali tau cara fixnya

This problem is from your hosting because the mod_security function is running, you should contact your hosting to tell them to stop it for your site in order for the upload system to work.

Also make sure you did not remove this line from .htaccess:

<IfModule mod_security.c>
SecFilterEngine Off
SecFilterScanPOST Off
</IfModule>

2 hours ago, Jei Grey said:

I'm trying the expired status in the user account. in the status view is appropriate. But the device is still connected and can still send messages even though the status has expired. please check mr @Magd Almuntaser

There is a mistake you made, if you notice that the plan expiration is moving (3 minutes ago) and this thing is not supposed to appear.. When you stop someone, make sure that you made him (inactive) and not (expired) because the expired tool is only used automatically and needs the date to expire.

2 hours ago, Ipo Kane said:

Hello master @magd Almuntaser, if there are 10 users who create a campaign at the same time, will the messages be sent simultaneously at the same time (asynchronously) or in turns/queue?

Atau mungkin teman2 ada yang tahu?

at the same time but programmatically organized

43 minutes ago, Magd Almuntaser said:

There is a mistake you made, if you notice that the plan expiration is moving (3 minutes ago) and this thing is not supposed to appear.. When you stop someone, make sure that you made him (inactive) and not (expired) because the expired tool is only used automatically and needs the date to expire.

Magd, then if the date expire is filled, so the user can login, but can’t use the service? like sending message or anything else?

There is update 9.0.2

8 minutes ago, adhiete said:

Magd, then if the date expire is filled, so the user can login, but can’t use the service? like sending message or anything else?

Yes, if the user has expired, he can login but he cannot use any feature or even use the API.

2 minutes ago, Magd Almuntaser said:

Yes, if the user has expired, he can login but he cannot use any feature or even use the API.

the case I tried. Service status expired. users cannot add devices anymore. But the device stays connected and can send messages

1 hour ago, Magd Almuntaser said:

This problem is from your hosting because the mod_security function is running, you should contact your hosting to tell them to stop it for your site in order for the upload system to work.

Also make sure you did not remove this line from .htaccess:

<IfModule mod_security.c>
SecFilterEngine Off
SecFilterScanPOST Off
</IfModule>

already stop, but still same :( upload file succes but error viewing file. Error like screenshot i’ve sent.

Edited Thursday at 09:02 AM3 days by Aidil Aryanto

4 minutes ago, Jei Grey said:

the case I tried. Service status expired. users cannot add devices anymore. But the device stays connected and can send messages

If that is the case, I think the device should still be connected, but it cannot send messages, either from the application or API.

It must remain connected, so that if the user extends the subscription, the user does not need to rescan and can be used immediately.

It is a bit complicated if the user has to rescan, especially if the user is not the person who is given access to scan the QR.

1 hour ago, adhiete said:

If i look at the cronjob and database, it seems the messages will be sent on queue. Except the 10 users create and saving at the same second.
Already try on the scheduled time, three user creating campaign and saving up on the same time 14:15. User A saving is 14:10:36, User B saving is 14:11:29, and User C 14:12:44. The campaign execution ended on User A first, then User B, and last User C.

Berarti pesan dari user B akan terkirim setelah semua pesan dari campaign user A terkirim semua ya mas? Jadi pengiriman bisa delay, menunggu semua pesan dari user A terkirim dahulu.

Tapi dari jawaban Magd di atas, dikirim bersamaan. Mau mencoba tapi tidak ada nomor untuk dikirimi campaign 😄. Butuh nomor agak banyak untuk melihat progress pengirimannya.

1 minute ago, Ipo Kane said:

Berarti pesan dari user B akan terkirim setelah semua pesan dari campaign user A terkirim semua ya mas? Jadi pengiriman bisa delay, menunggu semua pesan dari user A terkirim dahulu.

Tapi dari jawaban Magd di atas, dikirim bersamaan. Mau mencoba tapi tidak ada nomor untuk dikirimi campaign 😄. Butuh nomor agak banyak untuk melihat progress pengirimannya.

Ho oh, ini tadi hasil ngetes di campaign di jam yang sama. Mau ngeliat resources yang kepake, kuat apa engga di 1G 1C VPS wkwkwk. Tapi ya aman aman aja. Soalnya kan test kirim sampai 3 campaign di jam yang sama dengan user berbeda. Per 1 campaign kirimnya ke 6 nomor berbeda. Totalnya 17 nomor soalnya ada 1 campaign yang 5 nomor. Hasil pemakaiannya tadi cuma berapa persen gitu di processornya. Minimalis lah ini, mungkin kerasa kalau 1 campaign 100 nomor kali ya. Ini resources yang kepake cuma 0,5% ram juga cuma 3% ketika campaignnya berjalan. Amazing lah.

Hasilnya ya User A tetap ke kirim duluan, sampai semua selesai baru User B, dan lanjut ke User C. dan User A, B, C, ini set di jam yang sama.
Kalau dilihat jedanya tipis dan prosesnya cepet banget.

Sesuai sih sama jawabannya Magd, semua akan bersamaan terkirim tapi terorganisir.

10 minutes ago, adhiete said:

Ho oh, ini tadi hasil ngetes di campaign di jam yang sama. Mau ngeliat resources yang kepake, kuat apa engga di 1G 1C VPS wkwkwk. Tapi ya aman aman aja. Soalnya kan test kirim sampai 3 campaign di jam yang sama dengan user berbeda. Per 1 campaign kirimnya ke 6 nomor berbeda. Totalnya 17 nomor soalnya ada 1 campaign yang 5 nomor. Hasil pemakaiannya tadi cuma berapa persen gitu di processornya. Minimalis lah ini, mungkin kerasa kalau 1 campaign 100 nomor kali ya. Ini resources yang kepake cuma 0,5% ram juga cuma 3% ketika campaignnya berjalan. Amazing lah.

Hasilnya ya User A tetap ke kirim duluan, sampai semua selesai baru User B, dan lanjut ke User C. dan User A, B, C, ini set di jam yang sama.
Kalau dilihat jedanya tipis dan prosesnya cepet banget.

Sesuai sih sama jawabannya Magd, semua akan bersamaan terkirim tapi terorganisir.

Terima kasih sudah share hasil tesnya. Sepertinya memang ringan, cuma semacam proses curl biasa untuk mengirim pesan ke server Whatsappnya. Apalagi jika proses pengirimannya ternyata berurutan, yang artinya hanya memproses 1 pesan pada waktu yang tertentu, yang terjadi secara terus-menerus.

Sebenarnya yang saya maksud bersamaan itu, misal jika ada 10 user yang membuat schedule pkl 14.30, maka pada pukul 14.30 itu pula semua pesan dari semua user mulai terkirim. Jadi pengiriman pesan di campaign B tidak menunggu semua pesan dari campaign A terkirim semua.

Atau mungkin bisa diakali dengan membuat banyak cron job ya? 20 cron job misalnya, agar prose pengiriman lebih cepat 😁

46 minutes ago, Aidil Aryanto said:

already stop, but still same :( upload file succes but error viewing file. Error like screenshot i’ve sent.

However, mod_security is still working for your site, the (406 not acceptable) message will not go away unless mod_security is stopped.

5 minutes ago, Ipo Kane said:

Terima kasih sudah share hasil tesnya. Sepertinya memang ringan, cuma semacam proses curl biasa untuk mengirim pesan ke server Whatsappnya. Apalagi jika proses pengirimannya ternyata berurutan, yang artinya hanya memproses 1 pesan pada waktu yang tertentu, yang terjadi secara terus-menerus.

Sebenarnya yang saya maksud bersamaan itu, misal jika ada 10 user yang membuat schedule pkl 14.30, maka pada pukul 14.30 itu pula semua pesan dari semua user mulai terkirim. Jadi pengiriman pesan di campaign B tidak menunggu semua pesan dari campaign A terkirim semua.

Atau mungkin bisa diakali dengan membuat banyak cron job ya? 20 cron job misalnya, agar prose pengiriman lebih cepat 😁

As I told you each campaign is separate from the other, the two campaigns will be sent together but in an organized manner..

Let's assume that campaign 1 has 10 numbers

Campaign 2 has 10 more numbers

When the two campaigns are sent, they will start together.. but in an organized manner, meaning that the first message from campaign 1 will not be sent at the same moment as the first message from campaign 2, but immediately after it.
Because if WhatsApp sees that there are two messages at the same time from the same number, it feels that there is something strange and that it is not human.

The cronjob has nothing to do even if you put 100 cronjobs.. The whole deal is from Nodejs and not from cronjob..

The cronjob only sends the request to nodejs and then Nodejs deals with the delay and sending of each message in the js files

when i install i see this error

9 minutes ago, dewanoo said:

when i install i see this error

Itu ngak biaa konek ke sql om

Android Button Message not working