AHMEDX
Guide

ZOKOU MD WhatsApp Bot: Features, Session ID and Deployment Guide

ZOKOU MD, also known as Zokou 2.0, is a third party WhatsApp Multi Device bot project by Djalega++ and Monkey D Luffy, documented in a French language README in its original GitHub repository. That repository is live today and was read in the original French for this guide: it documents the feature list, links one session website, and gives Heroku and Koyeb deployment routes. The session website was opened again for this guide and its QR route loads, while the pairing code destination it links out to returns a 404 error, and the README Heroku button in fact templates a different repository, so this guide states the present day condition of every route plainly.

By AHMED X · November 12, 2026 · Last verified November 12, 2026

About

What Is ZOKOU MD WhatsApp Bot?

What the project is, who developed it, where its code can be read today, and the state of the repository record.

ZOKOU MD, also known as Zokou 2.0, is a third party WhatsApp Multi Device bot project by Djalega++ and Monkey D Luffy. The original repository, djalega8000/Zokou-2.0, is live today, it is not a fork, and every fact in this guide is checked against it directly. Other repositories and forks using the Zokou name circulate, including a copy under the WhiteKingsVII account; that copy was not used as a source for this guide, and features from it are not merged in.

The project README is written in French, and this guide follows what it actually says rather than what English summaries of the project often claim. The package.json file names the application simply ultra, gives its version as 2.0.0 with index.js as its main file, and takes its Baileys dependency from a fork of the library held under the second developer own account rather than from the main Baileys release line. The repository record was last pushed in August 2024, so readers should treat this as a project whose public code has not moved recently.

The repository tree holds index.js as the main application, set.js as the configuration file, exemple_de_set.env as the example environment file, a commandes folder of command files, a framework folder, auth and bdd folders, media and gif resource folders, and the deployment and project files package.json, app.json, heroku.yml and a Dockerfile. The README itself is short: a feature list in two parts, a fork step, one session link, two deployment sections, a contributions section and a license section.

Features

ZOKOU MD WhatsApp Bot Features

The features below are the ones the original French README itself lists, translated faithfully. The README publishes no command list, no command syntax and no prefix, so none is published here; the four command names it credits to a contributor are framed as credits, exactly as the README gives them.

Audio and Video Downloading

The first feature the README lists: Zokou can download audio and video files from links you send it, so they can be shared easily with your contacts. The README names no list of supported websites and no formats, so this guide records the feature at exactly that level.

Telegram Sticker Export

The README documents exporting stickers from Telegram into WhatsApp conversations by sending them to Zokou. It states plainly that this feature needs an API key from API Lolhuman. The README even prints a shared key for readers who cannot get one; do not use credentials printed inside a public repository, and obtain your own key instead.

WhatsApp Group Management

The README group feature covers adding and removing members and configuring group rules and other settings, presented there as help for managing group conversations.

Text to Image Generation

The README lists a text to image feature and says the best logos were selected for it. It does not explain which external service generates the images or catalogue the available designs, so this guide records the feature as the README presents it and no further.

Jokes and Riddles

Under its fun features heading, the README lists a collection of jokes and riddles, blagues et devinettes in the original French, intended to liven up conversations.

Inspirational Quotes

The second fun feature the README lists: inspirational quotes you can receive and share for daily motivation.

Credited Command Additions

The README contributions section thanks a contributor named Fatao for adding the Fancy, GPT, DALL E and APK commands. Those four names are a credit line in the README, not a verified command list: the README gives no syntax, no arguments and no prefix for them, and this guide presents them only as the additions the project credits to him.

Session ID Authentication

The README obtains the bot session through one linked website, covered in the session section of this guide. Its present day state is mixed: the QR route on that site loads, and the pairing route it points to does not.

Deployment Files in the Tree

Beside the two documented deployment routes, the tree carries a Dockerfile, app.json and heroku.yml. Their presence is file evidence of the deploy shapes the project prepared; the README itself documents Heroku and Koyeb only.

Session ID

How to Get a ZOKOU MD Session ID

The README links exactly one session website, zkscan.onrender.com, as its Session-1 route. That site and both of its authentication pages were opened again for this guide: the site loads and identifies itself as ZOKOU-MD, its session page offers QR and pairing code choices, its QR page loads, and the pairing code destination it links out to returns a 404 error.

01

Open the Session Website From the README

The README second step for obtaining the bot is a single link, labelled Session-1, pointing at zkscan.onrender.com. Opened for this guide, the site loads and presents itself as Zokou MD by Djalega++ and Monkey D Luffy, with a Get a SESSION_ID option. Use only this developer linked address, because copied session pages are a known trap.

02

Choose Your Authentication on the Session Page

The Get a SESSION_ID route leads to a page offering two choices: Use QR Code and Use Pairing Code. The two choices do not lead to equally healthy places today, as the next steps record.

03

QR Code: The Route That Loads Today

The QR choice opens the site qrcode page, which loads as a ZOKOU-MD QR scanner page and presents the QR code for linking. On Android, open WhatsApp, tap the three dot menu, select Linked Devices, tap Link a Device and scan. On iPhone, open WhatsApp, go to Settings, select Linked Devices, tap Link a Device and scan. This is the working documented authentication route as checked for this guide.

04

Pairing Code: Its Destination Returns 404

The pairing code choice on the session page links out to a separate Koyeb address, nutty-zaneta-school900-3958f33c.koyeb.app. That address was opened for this guide and returns a 404 error, so no working pairing code service for ZOKOU MD could be confirmed. Do not enter your number into any other page claiming to pair ZOKOU MD.

05

A Second Session Site Is Mentioned but Not Linked

The README contributions section thanks another contributor, CrazyPrice, for hosting a second website for session IDs. It publishes no address for that site, so this guide cannot check it and links nothing for it. The one linked site above is the only documented route.

06

Keep the Session ID Private

Once linking completes, follow the site instructions to obtain your Session ID and place it in the bot configuration. Anyone holding usable authentication credentials may be able to access the WhatsApp session they came from, so never share the value in chats, screenshots or public forks.

Deployment

How to Deploy ZOKOU MD WhatsApp Bot

The README documents two deployment routes, Heroku and Koyeb, and they are not equal: the Koyeb link is built on this repository, while the Heroku button templates a different repository altogether, which this guide states plainly. The package file also defines a manual Node.js run that the steps below record from the real scripts.

01

Fork and Get a Session First

The README first step is to fork the repository to your own GitHub account, and its second step is the session website covered above. Both come before any deployment route, and the README asks readers to star the repository to encourage the developers.

02

Heroku: The Button Templates a Different Repository

The README deployment section for Heroku links an account page and then a deploy button. Read carefully, that button template address points at FaouzKK/zokou-french-version-whatsapp-bot, a French version repository under the second developer account, and not at djalega8000/Zokou-2.0 itself. The tree of the original repository does carry app.json and heroku.yml, but as written, the README Heroku route deploys that other repository. This guide reports the link exactly as it stands rather than presenting it as a one click deploy of this repo.

03

Koyeb: The Deploy Link for This Repository

The README Koyeb section links an account creation page and then a prefilled deploy link built on this repository, on the main branch, with the Dockerfile era settings expressed as French environment names such as NOM_OWNER, NOM_BOT, MODE_PUBLIC and NUMERO_OWNER. That link ships filled in example values, including an owner number and a complete database URL with credentials. Replace every shipped value with your own before deploying, and never run against the database the link carries.

04

Manual Installation: The Package Scripts

For a machine of your own, package.json defines the run methods directly. Its s script starts the application with node index.js, and its zokou script starts the same file under PM2 with a memory restart limit. The manual shape is: clone the repository, run npm install, review set.js and the exemple_de_set.env example, place your session and settings, then start with npm run s or npm run zokou and read the terminal output to confirm the WhatsApp connection.

05

Docker: A File, Not a Tutorial

The repository tree contains a Dockerfile, which is the file a container based environment uses to package the application. The README gives no Docker commands and no container procedure, so this guide records the file as evidence of a prepared container route and publishes no invented Docker steps.

Configuration

ZOKOU MD Configuration Settings

The setting names below were read from set.js and the shipped exemple_de_set.env file, which use French names. Only names and roles are published; the shipped example files carry filled in values, including database credentials and an example session value, that belong to the project side and must always be replaced with your own.

SESSION_ID

The session setting set.js reads from the environment, falling back to a shipped placeholder when none is given. It is the value the session website exists to produce, and your own value should always be set explicitly and kept private.

NOM_OWNER and NUMERO_OWNER

The owner identity settings: NOM_OWNER is the owner name the bot presents and NUMERO_OWNER the owner number, both read by set.js and both shipped with project example values in the example file.

NOM_BOT and LIENS_MENU

The presentation settings: NOM_BOT is the bot name and LIENS_MENU the menu image link the application displays. Both are read by set.js from the environment with shipped defaults.

MODE_PUBLIC

The operating mode setting, read by set.js as the bot mode. The example file ships it in the off position, so check the value in your own copy before assuming the bot answers everyone.

Status Behaviour Settings

LECTURE_AUTO_STATUS controls automatic status reading and TELECHARGER_AUTO_STATUS automatic status downloading, with STARTING_BOT_MESSAGE and ANTI_DELETE_MESSAGE covering the startup message and anti delete message behaviour, and WARN_COUNT the warning limit. All are read by set.js under these exact French names.

DATABASE_URL

The database connection set.js builds the application storage on. The shipped example file and even the set.js code itself carry a filled in database URL with credentials from the project side. Never use it: set your own DATABASE_URL, because anyone who reads the public files can read those credentials too.

PREFIXE

set.js reads a PREFIXE setting from the environment, so the command prefix is configurable in this project. The README documents no default prefix and no command syntax, and this guide publishes no prefix value for ZOKOU MD; follow the files inside your own copy.

Official Links

ZOKOU MD Official Links

The resources checked for this guide: the original repository and its package file, the developer linked session website and its two authentication pages with their real present day status, the dead pairing destination listed for the record, and the external API one feature depends on.

Zokou 2.0 GitHub Repository

The original djalega8000/Zokou-2.0 repository, live today and not a fork. It carries the French README, set.js, exemple_de_set.env, package.json and the tree this guide verified against.

https://github.com/djalega8000/Zokou-2.0

Zokou 2.0 package.json

The package file inside the original repository: the record this guide used for the application name, its 2.0.0 version value and the s and zokou run scripts.

https://github.com/djalega8000/Zokou-2.0/blob/main/package.json

ZOKOU MD Session Website (Live)

The zkscan.onrender.com website the README links as its Session-1 route. Checked for this guide, it loads and identifies itself as ZOKOU-MD by Djalega++ and Monkey D Luffy, with a Get a SESSION_ID option.

https://zkscan.onrender.com

ZOKOU MD Session ID Page (Live)

The getsession page of the same site, which offers the two authentication choices: Use QR Code and Use Pairing Code.

https://zkscan.onrender.com/getsession

ZOKOU MD QR Authentication Page (Live)

The qrcode page of the session site, which loads as a ZOKOU-MD QR scanner page presenting the linking code. This is the working documented authentication route as checked for this guide.

https://zkscan.onrender.com/qrcode

Pairing Code Destination (Offline)

The separate Koyeb address the session page pairing choice links out to. It returns a 404 error today, checked for this guide, and is listed for the record, not as a working pairing service.

https://nutty-zaneta-school900-3958f33c.koyeb.app/

API Lolhuman

The external API service the README names for the Telegram sticker export feature, which requires an API key from this site. Obtain your own key there rather than using any key printed inside a repository.

https://api.lolhuman.xyz/

Heroku

The hosting platform one of the two README deployment routes names. Note that the README Heroku button templates a different repository, as the deployment section of this guide records.

https://dashboard.heroku.com/

Koyeb

The hosting platform of the second README deployment route, whose prefilled deploy link is built on the original Zokou 2.0 repository.

https://app.koyeb.com/

Safety

Is ZOKOU MD WhatsApp Bot Safe?

The precautions that apply to ZOKOU MD, including the credentials sitting inside its shipped files, the broken pairing route its session site points to, and the disagreement inside its license records.

ZOKOU MD is an unofficial third party bot. Unofficial automation can bring temporary restrictions or a permanent ban on the number you connect, and no feature in any bot can promise protection from that. Use a separate number for testing rather than your main personal or business number, and avoid spam and abusive automation of any kind. Authenticate only through the session website the README itself links, and check the address before typing anything: its pairing choice currently leads to a dead page, and a vacuum like that is exactly what fake pairing websites exploit.

Check the shipped files before you run anything. The example environment file, the Koyeb deploy link in the README and set.js itself carry filled in project side values, including a complete database URL with credentials and an example session value. Those credentials are readable by anyone who opens the public repository, so never run the bot against them and never treat a shipped owner number as yours. Replace every value with your own, use your own database, obtain your own API Lolhuman key instead of the shared key the README prints, and keep your Session ID out of chats, screenshots and public forks.

On licensing, the records inside the repository disagree with each other. The README license section states that the Zokou WhatsApp bot is published under the MIT License and links the MIT text. There is, however, no LICENSE file anywhere in the repository tree, and the GitHub API detects no license for the repository, while the license field of package.json reads ISC. This guide reports all three signals exactly as they stand and names no single license for ZOKOU MD, so readers should weigh them together before reusing the code.

Alternatives

Free MD Bots You Can Deploy on AHMED X

Want more free MD bots like this? These bots on AHMED X cover the same ground: free deploy, pair-code setup, group and chat automation.

ASTRA X

ASTRA X

WhatsApp MD Bot

Advanced AI-first MD bot with dual AI engines, media downloaders and deep group management.

Geston-MD

Geston-MD

WhatsApp MD Bot

Lightning-fast Baileys multi-device bot with AI chat, group protection and replies in many languages.

CELESTIA

CELESTIA

WhatsApp MD Bot

A polished multi-device WhatsApp bot with a large command library, AI chat and safe group tools.

TOXIC-MD

TOXIC-MD

WhatsApp MD Bot

Lightning-fast WhatsApp bot built on Baileys, made for speed and everyday automation.

SUKUNA-MD

SUKUNA-MD

WhatsApp MD Bot

A modular WhatsApp MD bot with group administration, media tools, protection engines and AI voice replies.

Levanter

Levanter

WhatsApp MD Bot

Multi-device WhatsApp bot packed with group protection, AI chat and a plugin system.

View all bots in the catalog

FAQ

ZOKOU MD FAQs

Short answers to the questions readers ask most about ZOKOU MD.

ZOKOU MD, also called Zokou 2.0, is a third party WhatsApp Multi Device bot project by Djalega++ and Monkey D Luffy, documented in a French language README. Its documented features cover audio and video downloading, Telegram sticker export, group management, text to image generation, jokes, riddles and inspirational quotes.

Djalega++ and Monkey D Luffy. The README developer section names both, the package file gives its author as Djalega++, and the session website presents the bot as by Djalega++ and Monkey D Luffy.

Through the session website the README links, zkscan.onrender.com. Open it, choose Get a SESSION_ID, and use the QR Code option: the site qrcode page loads today and presents the linking code to scan with WhatsApp Linked Devices.

Its session website offers a Use Pairing Code choice, but that choice links out to a separate Koyeb address that returns a 404 error today, checked again for this guide. No working pairing code service for ZOKOU MD could be confirmed; the QR route on the same site is the working documented option.

The README publishes no command list, no syntax and no prefix, so this guide publishes none. It only credits a contributor named Fatao with adding Fancy, GPT, DALL E and APK commands, and presents those four names as that credit. The repository does contain a commandes folder of command files, but names taken from tutorials may not match the original version.

Heroku and Koyeb, plus a manual Node.js run from the package scripts. One caution: the README Heroku button templates a different repository, FaouzKK/zokou-french-version-whatsapp-bot, while its Koyeb deploy link is built on the original Zokou 2.0 repository. The package file runs the bot with npm run s under Node.js or npm run zokou under PM2.

No single license can be confirmed from the records. The README license section names the MIT License, but the repository tree contains no LICENSE file and the GitHub API detects no license, while the license field of package.json reads ISC. Readers should weigh all three signals before reusing the code.

Disclaimer

About This Guide

How this guide was prepared.

This article is based on the ZOKOU MD records that could be opened on the last verified date: the original djalega8000/Zokou-2.0 repository, read through the GitHub API and its raw files, including its French language README with the raw links behind its session and deployment buttons, its package.json, set.js, exemple_de_set.env and its full repository tree, together with the developer linked session website and its session and QR pages, and the pairing destination behind its pairing choice. On that date the original repository was live and last pushed in August 2024, the session site and its QR page loaded, the pairing destination returned a 404 error, the README Heroku button was found to template a different repository, and the license records disagreed as this guide records. A second repository copy under the WhiteKingsVII account was not used as a source. Where the records publish nothing, this guide says so instead of filling the gap.

AHMED X provides this article for educational and informational purposes only. AHMED X is not the developer or owner of ZOKOU MD and does not claim any partnership or official affiliation with Djalega++, Monkey D Luffy, or the project contributors.

AHMED X is not affiliated with, endorsed by, or sponsored by WhatsApp or Meta. WhatsApp is a trademark of its respective owner. Use unofficial WhatsApp automation at your own risk.

Keep Reading

Related WhatsApp Bot Guides

More free WhatsApp bot guides from the AHMED X blog.

Guide

MD Bot WhatsApp: Complete Beginner Guide to Features, Session ID and Deployment

An MD bot WhatsApp application is an automated WhatsApp bot that connects to an account using WhatsApp Multi Device functionality. These bots can help users automate messages, manage groups, download media, create stickers, and perform other tasks through WhatsApp commands. Many WhatsApp MD bots are available as open source JavaScript projects. Beginners can choose a project, connect their WhatsApp account using a QR code or pairing code, and run the bot on a computer, VPS, or supported cloud hosting service.

Read the guide
Guide

WhatsApp MD Bot: Types, Features and How to Choose the Best One

A WhatsApp MD bot is an automated application that connects to a WhatsApp account through Multi Device functionality. These bots are available in different categories, and each category is designed for a different purpose. Some WhatsApp MD bots focus on group management, while others provide media downloading, AI assistance, entertainment commands, or simple automatic replies.

Read the guide
Guide

MD WhatsApp Bot: Complete Guide to QR Code, Pairing Code and Session ID

Connecting an MD WhatsApp bot to your WhatsApp account is one of the most important steps when setting up a bot. Without successful authentication, the bot cannot establish its WhatsApp connection or process messages. Most WhatsApp MD bots use linked device authentication. Depending on the project, you may connect through a QR code or a pairing code and then use the generated session credentials to keep the bot connected.

Read the guide
Guide

MD Bot: Complete Beginner Guide and WhatsApp Bot Glossary

If you are new to WhatsApp automation, you may have seen terms like MD, Session ID, Pairing Code, QR Code, Prefix, Plugins, Baileys, and Node.js. These words are commonly used in MD bot tutorials, but understanding them can be difficult when you are just starting. An MD bot is an automated application that connects to a WhatsApp account and performs different tasks through commands and programmed features.

Read the guide

Deploy Your Own Free WhatsApp Bot Today

Pick a bot from the AHMED X catalog and deploy it free in minutes. No server, no coding.

Browse Free Bots