AHMEDX
Guide

SULA MD WhatsApp Bot: Features, Pairing Code and Deployment Guide

SULA MD is a third party WhatsApp Multi Device bot project by Sulaksha Madara, and two different things share its name. The first is the GitHub project: the repository that survives today under the developer account holds the application files, sula.js, settings.js, package.json, app.json and an Apache License, but no README at all. The second is the newer SULA OFC web platform at sulaofc.store, which offers cloud bot deployment through pair code connection and advertises its own feature set. The README that documented pairing and deployment buttons for the GitHub project lived on a second repository address, SULA-MD-NEW/SULA-MD, which returns a 404 error today. This guide keeps the repository and the platform separate from the first line to the last, exactly because mixing them produces wrong instructions.

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

About

What Is SULA MD WhatsApp Bot?

What the project is, who develops it, which repository survives today, and what happened to the repository its documentation lived on.

SULA MD is a WhatsApp Multi Device bot created by Sulaksha Madara. The repository that can be opened today is sulaksha-madara/SULA-MD. Its package file names the project SULA-MD at version 4.0.0, describes it as a WhatsApp bot created using Node.js, and gives sula.js as the main file. Its app.json describes the app as SULA-MD Multidevice Whatsapp Bot. The package file lists its Baileys dependency as the WhiskeySockets Baileys package taken from a GitHub fork named Malvin-Baileys.

Two repository identities appear in the project record, and this guide checked both. The developer account repository, sulaksha-madara/SULA-MD, is live, but its tree contains only five files: sula.js, settings.js, package.json, app.json and LICENSE. There is no README in it. The documentation that write ups of this project quote, including a Get Session ID via Pair Code section and the deployment buttons, lived on the second address, SULA-MD-NEW/SULA-MD, which is also where the README sources list gives the project README and where the Heroku template link pointed. That address returns a 404 error today, and the SULA-MD-NEW account shows no public repositories. Where this guide describes that documentation, it says so, and it rests every load bearing claim on files that can still be opened.

The SULA OFC platform is a separate and newer thing. At sulaofc.store the developer offers a web platform whose bots page invites users to deploy the SULA MD WhatsApp bot in the cloud, connecting a number by pair code or QR scan with no application installation or server setup. Features advertised there belong to that platform service. They are not documentation of what the self hosted GitHub application does, and this guide never merges the two.

Features

SULA MD WhatsApp Bot Features

Two lists, kept apart on purpose. The first cards rest on files in the surviving repository. The last cards describe what the SULA OFC platform advertises on its own pages, framed as platform advertising and not as repository documentation.

Multi Device WhatsApp Bot

The identity the surviving files establish: app.json calls the app a Multidevice Whatsapp Bot, the package file describes a WhatsApp bot created using Node.js, and its Baileys dependency is the library that provides the linked device connection.

Session ID Pairing

The self hosted application is built around a SESSION_ID. app.json lists SESSION_ID as its one required setting, with the description Put the session-id here, and settings.js reads the session from the SESSION_ID environment value. The documentation on the closed repository carried a section titled Get Session ID via Pair Code for obtaining it.

Anti Delete and Protection Toggles

settings.js in the surviving repository defines the protection set: ANTI_DELETE ships switched on in the file, alongside ANTI_LINK, ANTI_CALL and ANTI_BOT toggles. A DELETEMSGSENDTO setting names the number that receives recovered deleted messages.

Status Automation

The same settings file defines AUTO_READ_STATUS and AUTO_REACT_STATUS, both shipped switched on, covering automatic status viewing and automatic status reactions in the self hosted application.

Automation and AI Toggles

settings.js also defines AUTO_REPLY, AUTO_VOICE, AUTO_STICKER and the AI switches AI_REPLAY and AI_CHAT. In the shipped file every one of them is set off by default, so they are capabilities the settings expose, not behaviour the bot performs until an owner enables them.

Platform: Cloud Bot Deployment

On the SULA OFC platform, the advertised offer is a free cloud bot: connect your WhatsApp in seconds via pair code or QR scan, with zero application installation or server setup needed, in the platform own wording. That is a hosted service, separate from the GitHub application above.

Platform: AI and Media Tools

The platform bots page advertises an Advanced AI Assistant Suite, movie, music and social media downloaders, group administration tools, deleted message recovery and a view once media saver. The developer website descriptions also name GPT and Gemini integrations. All of it is platform advertising for the hosted service, not repository documentation.

Platform: Settings Panel

The platform offers a customizable settings panel, described on its bots page as covering auto reply keywords, logos, voice responses and prefix rules. The platform settings documentation names two commands, .setting and .password, for requesting the settings password. Those commands belong to the platform service; no command list exists for the GitHub application.

Pairing

How to Get a SULA MD Session ID

There are two connection stories and they end in different places. The platform route, verified live on sulaofc.store/bots for this guide, connects a number to the hosted service. The self hosted application instead consumes a SESSION_ID value, and its documented pairing section lived on the repository that no longer opens.

01

Platform Route: Open the SULA OFC Bots Page

Visit sulaofc.store/bots and find the Deploy SULA MD WhatsApp Bot panel. The page presents the service as a live free cloud bot and asks the user to confirm the number is a secondary WhatsApp number before connecting.

02

Platform Route: Enter Your Number

Enter your WhatsApp number with its country code, without the plus sign or spaces, following the page shortcuts and instructions. Check the number carefully, because the code that follows is issued for the number entered.

03

Platform Route: Generate the Pair Code

The platform generates an eight letter pair code and states that the generated code is active for 60 seconds. That figure comes from the platform page itself, checked for this guide; it describes the platform service, not the self hosted application.

04

Platform Route: Enter the Code in Linked Devices

On Android, open WhatsApp, tap the three dot menu, select Linked Devices, tap Link a Device and choose Link with phone number instead. On iPhone, open WhatsApp, go to Settings, select Linked Devices, tap Link a Device and choose the phone number option. Enter the code before it expires, and the platform connects the bot on its own hosting.

05

Self Hosted Route: The SESSION_ID the App Requires

For the GitHub application, authentication ends in a SESSION_ID value: app.json requires it at deploy time and settings.js reads it when the app starts. The Get Session ID via Pair Code section that documented obtaining one was part of the README on the repository address that returns a 404 error today, so no live official pairing page for the self hosted version could be confirmed for this guide.

06

Do Not Assume the Two Routes Match

A number connected on the SULA OFC platform is connected to that hosted service. It should not be assumed to produce the SESSION_ID format the self hosted application expects, and a Session ID from any other source should not be typed into the platform. Keep each route inside its own system.

07

Keep Credentials Private

A Session ID and a settings password are both working credentials. Never share either in chats, screenshots or public forks, and only enter your number on pages you can trace back to the developer, starting from the repository or the platform address the project itself publishes.

Deployment

How to Deploy SULA MD WhatsApp Bot

The surviving repository proves the Heroku file shape and the manual run method directly. The Render and TalkDrove routes were documented on the closed repository README, and the TalkDrove page did not load when checked, so those routes are recorded as documentation rather than working procedures.

01

Heroku: The app.json Shape in the Surviving Repo

The repository contains app.json, the file a Heroku style deployment reads. It names the Node.js buildpack, sets the heroku-24 stack, and lists SESSION_ID as required with BUTTON, AUTO_REACT, DELETEMSGSENDTO and ALLWAYS_OFFLINE as optional settings. That file is present day evidence of the Heroku route shape.

02

Heroku: The README Button Points at a Closed Repo

The one click template route described for this project pointed its template address at SULA-MD-NEW/SULA-MD. That repository returns a 404 error today, so the button route cannot be followed as written, whatever the app.json in the surviving repository proves about the intended shape.

03

Render: Documented on the Closed Repository

The project documentation on the closed repository included a Render deployment link. The surviving repository contains no Render specific configuration file, so this guide records the route as documented there and claims no current working Render procedure for SULA MD.

04

TalkDrove: The Documented Page Did Not Load

The same documentation listed a TalkDrove deployment page at host.talkdrove.com/share-bot/79. That address did not load when checked for this guide, so the route is recorded as documented but presently unreachable.

05

Manual Run: Clone the Surviving Repository

Clone sulaksha-madara/SULA-MD, the repository that can still be opened, and install the dependencies from its package file with npm install. Review settings.js before starting, because that file holds the session, prefix and behaviour settings the application reads.

06

Manual Run: PM2 Scripts From package.json

The package file defines the run method directly: its start script launches sula.js under PM2 with the process name SulaMd and attaches to it, and stop and restart scripts for the same PM2 process sit beside it. Those scripts were verified in the real package.json for this guide.

07

Platform Route: The SULA OFC Cloud Service

Separately from every route above, the SULA OFC platform offers its own hosted deployment through its website, where the bot runs on the platform after the pair code connection described in the pairing section. It needs no repository, no server and no SESSION_ID handling by the user, because it is a managed service rather than the self hosted application.

Configuration

SULA MD Configuration Settings

The settings app.json and settings.js in the surviving repository actually define. Replace every shipped example value with your own before any run.

SESSION_ID

The one required setting. app.json demands it at deploy time, and settings.js reads it from the environment, falling back to a value shipped inside the file itself when no environment value is set. That shipped value belongs to the project side: always set your own.

PREFIX

settings.js defines PREFIX with a full stop as its shipped default, so the self hosted application is configured around a dot prefix unless the owner changes it in the environment or in a config.env file, which settings.js also supports.

MODE

settings.js defines the operating mode setting, with its shipped default written in the file as privet. The app.json optional settings sit beside it, including ALLWAYS_OFFLINE for an always offline presence.

Protection Settings

ANTI_DELETE ships switched on in settings.js, with DELETEMSGSENDTO naming where recovered deleted messages are sent. ANTI_LINK, ANTI_CALL and ANTI_BOT complete the protection set the file defines.

Automation Settings

The file defines AUTO_READ_STATUS and AUTO_REACT_STATUS switched on, AUTO_REACT for chat reactions, and AUTO_REPLY, AUTO_VOICE, AUTO_STICKER, AI_REPLAY and AI_CHAT switched off, each changeable through the environment.

Project Files

The complete surviving tree is five files: sula.js as the application, settings.js for configuration, package.json for dependencies and the PM2 scripts, app.json for Heroku style deployment, and LICENSE. Anything beyond those five files in a downloaded copy came from somewhere else.

Official Links

SULA MD Official Links

The resources checked for this guide: the surviving repository, the live platform pages, and the documented addresses that no longer load, listed for the record with their check results stated honestly.

SULA MD GitHub Repository

The sulaksha-madara/SULA-MD repository: live, carrying sula.js, settings.js, package.json, app.json and the LICENSE file this guide verified against. It contains no README.

https://github.com/sulaksha-madara/SULA-MD

SULA OFC Platform

The developer platform website at sulaofc.store, which presents the SULA MD cloud service and links its bots and settings pages. It loads today.

https://sulaofc.store

SULA MD Bot Deployment Page

The platform bots page at sulaofc.store/bots, read for this guide: it offers the pair code or QR connection, states the eight letter code and its 60 second activity window, and lists the platform advertised features.

https://sulaofc.store/bots

SULA MD Settings Panel

The platform settings page at sulaofc.store/bot-settings. The address responds today; its content is delivered by the platform app, and the settings it documents belong to the hosted service rather than the GitHub application.

https://sulaofc.store/bot-settings

Documentation Repository (Offline)

The SULA-MD-NEW/SULA-MD address that held the project README and the target of its Heroku template link. It returns a 404 error today, and is listed for the record, not as a working source.

https://github.com/SULA-MD-NEW/SULA-MD

Additional Website (Did Not Load)

The sula-md.site address circulated as an additional SULA MD website. It did not load when checked for this guide, closing without a response, and is listed for the record.

https://sula-md.site

TalkDrove Deployment Page (Did Not Load)

The TalkDrove share page the project documentation listed for SULA MD deployment. It did not load when checked for this guide, and is listed for the record, not as a working route.

https://host.talkdrove.com/share-bot/79

Baileys Library

The current home of the Baileys library under the WhiskeySockets name. The package file of SULA MD lists its Baileys dependency under the WhiskeySockets package name, sourced from a GitHub fork.

https://github.com/WhiskeySockets/Baileys

Safety

Is SULA MD WhatsApp Bot Safe?

The precautions that apply to SULA MD, including the shipped credentials inside its own settings file, the platform advertising that must not be read as protection, and its licence position.

SULA 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. The SULA OFC platform advertises an Anti-Ban Shield among its marketing names; that is an advertised label for a hosted service, and it does not change the underlying risk. Use a separate number for testing rather than your main personal or business number, as the platform itself advises, and avoid spam and abusive automation of any kind.

Check the shipped settings file before running the self hosted application. settings.js in the public repository carries built in default values, including a prefilled session value and a database connection string, and those values belong to the project side. Replace the session value with your own Session ID, remove or replace any shipped credential you find, and never run a copy that still holds them. The same care applies to the platform settings password: it unlocks your bot configuration, so keep it as private as the Session ID itself.

On licensing, the surviving record is consistent, and this guide can name it: the repository contains a LICENSE file carrying the full Apache License 2.0 text, and the GitHub API independently detects Apache-2.0 for the repository. That licence position applies to the code in the surviving repository. It says nothing about the SULA OFC hosted platform, which is a service with its own terms rather than a copy of the repository.

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

SULA MD FAQs

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

SULA MD is a third party WhatsApp Multi Device bot project by Sulaksha Madara. The name covers a self hosted GitHub application, whose surviving repository holds sula.js, settings.js, package.json, app.json and an Apache License, and the newer SULA OFC cloud platform, which hosts the bot as a service. The two are related by name and developer, and their features are not interchangeable.

The repository that opens today is sulaksha-madara/SULA-MD, and it contains no README. The documentation most write ups quote lived on SULA-MD-NEW/SULA-MD, which returns a 404 error today, so claims sourced from that README are presented in this guide as documentation from a closed repository, and every verifiable claim rests on the surviving files.

For the self hosted application, the SESSION_ID value that app.json requires and settings.js reads is the credential, and the closed repository documentation carried a Get Session ID via Pair Code section for obtaining one; no live official pairing page for the self hosted version could be confirmed. On the SULA OFC platform, connection works differently: its bots page issues an eight letter pair code, stated there to stay active for 60 seconds, and hosts the bot itself.

Yes, in both stories, with different meanings. The platform connects numbers by pairing code as its main flow. The self hosted application consumes a Session ID that its documentation obtained through a pair code process. Do not assume a platform connection produces the Session ID format the self hosted application expects.

For the self hosted application, the surviving app.json proves the Heroku shape, while Render and TalkDrove routes were documented on the closed repository and the TalkDrove page did not load when checked. The package file also defines a manual PM2 run. Separately, the SULA OFC platform offers its own cloud hosting as a service.

Sulaksha Madara. The surviving repository sits under his GitHub account, its package file carries the project in his name, and the SULA OFC platform is presented as his developer platform.

Apache License 2.0. The surviving repository contains a LICENSE file with the full Apache License 2.0 text, and the GitHub API independently detects Apache-2.0 for that repository, so the two records agree.

Disclaimer

About This Guide

How this guide was prepared.

This article is based on the SULA MD records that could be opened on the last verified date: the sulaksha-madara/SULA-MD repository read through the GitHub API and its raw files, including its package.json, app.json, settings.js, LICENSE file and its full five file tree, together with a live read of the SULA OFC bots page, whose pair code flow and advertised features are quoted as platform content. On that date the SULA-MD-NEW/SULA-MD repository returned a 404 error, the additional sula-md.site address and the documented TalkDrove page did not load, and the platform settings page responded without readable text, so the settings commands this guide names rest on the platform documentation as reported in the project record and are framed as platform documented only. 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 SULA MD and does not claim any partnership or official affiliation with Sulaksha Madara 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

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

SUPUN MD is a third party WhatsApp Multi Device bot project by Mr. Supun Fernando, a developer from Sri Lanka who also works under the name Dark Shadow Modz. The first fact a reader needs is where the project can still be read: the original repository, mrsupunfernando12/SUPUN-MD, returns a 404 error today, and the developer GitHub account behind it returns a 404 error as well. The record survives in partial copies, one on GitLab under the Nadu-12 account and one on GitHub under the iam-dsmodz account, and in three developer pages that still load. The pages load, but every pairing service behind them returns a 404 error today, so this guide links no working session service for SUPUN MD. A security report covered in the safety section gives readers a second reason to check every dependency carefully before running anything connected to this project name.

Read the guide
Guide

VAJIRA MD WhatsApp Bot: Features, Pairing Code and Deployment Guide

VAJIRA MD is a third party WhatsApp Multi Device bot project by Vajira Rathnayaka, a developer from Sri Lanka who also works under the name Vajira T.D.D. The first fact a reader needs is the state of the record: every repository under the developer own accounts returns an access blocked notice from GitHub today, and the repository copy that carried the V9 README has been deleted outright. What survives is an older V7 README preserved in a public copy, a partial set of the project deployment files preserved in another, and a live Railway template that still names the developer and still requires a Session ID, while pointing at a repository nobody can open. This guide is checked against those surviving records, presents the V9 material only where a surviving file corroborates it, and says plainly where the documentation can no longer be rechecked at all.

Read the guide
Guide

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

VENOM MD is a third party WhatsApp Multi Device bot project published by Bryan Tech, and unlike many projects in this series its original GitHub repository, Bryanlover1/VENOM-MD, still opens today, so this guide is checked against the repository itself: its README read in raw form, its full file tree, its package file, its example environment file, its settings file, its Heroku configuration and its LICENSE file. Two findings shape everything about using this bot. The README itself states, in its own capital letters, that its pairing code route temporarily uses the Naruto MD pairing service, and both authentication services it links return a 404 error today. And the repository package file does not match the project it sits in: it names the package MADARA-MD and points at a main file the repository root does not contain. Both facts are recorded plainly in the sections below.

Read the guide
Guide

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

WASI MD is a third party WhatsApp Multi Device bot project by Itxxwasi, also presented as Mr Wasi, and the identifiable current project is WASI MD V7 in his own GitHub repository. The original repository is live and was read in full for this guide: its README documents the feature categories and command tables, its .env.example and config.js carry the settings, and its troubleshooting section describes QR authentication with a delete the session folder and rescan flow. The project publishes no pairing website for V7, and the developer separate session generator repository today links to a website that shows unrelated proxy content, so this guide links no WASI MD pairing page as a working service.

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