Guide

AHMED X Bot Deployment Guide

AHMED X is a free WhatsApp bot deployment platform, no coding, no servers, no VPS. Pick one of our catalog bots, generate a pairing code with your WhatsApp number, and your bot is live in minutes. This guide walks you through every step, from signup to your first command.

Create your free AHMED X account

Sign up with your email and a password, it takes under a minute and it's completely free. Once you're in, you'll land on your personal dashboard where every bot you deploy, every session you link, and every plugin you like will live.

Browse the bot catalog

Open the Bots page to see every bot AHMED X supports. Each card shows what the bot can do, its plugin count, and community rankings so you can see which bots are trending right now. Tap a bot to read its full profile, command list, and required settings before you commit.

Generate a WhatsApp pairing code

Every bot needs a linked WhatsApp number to run on. Open the bot's pairing page and request a pairing code, an 8-character code that appears on screen. On your phone go to WhatsApp → Linked devices → Link a device → Link with phone number instead, then type the code. Pairing codes expire within minutes, so enter it immediately.

Copy your Session ID

After pairing succeeds, the pairing site shows your Session ID, a long string that proves your bot is authorized on that number. Copy it and keep it private: anyone with your Session ID can control the bot on your number. Never share it in groups or screenshots.

Configure your deployment

Back on AHMED X, hit Deploy on the bot you chose. Give your app a lowercase name (letters, numbers and dashes only), paste your Session ID into the SESSION_ID field, and fill any extra config vars the bot asks for, things like owner number or command prefix. Every var is explained right next to its input.

Deploy and watch the live logs

Hit Deploy and the build starts instantly. You'll see live logs streaming in the deploy view, dependency install, startup messages, and finally the 'bot online' line. Most builds finish in two to five minutes. If anything fails, the logs tell you exactly which step broke.

Test your bot with a command

Once the status flips to Running, message your linked WhatsApp number with .ping, the bot should reply within seconds. Try .menu to see its full command list. If it replies, congratulations: your WhatsApp bot is officially live, hosted entirely by AHMED X.

Manage bots from your dashboard

Done

Your dashboard's My bots tab is mission control: restart a crashed bot, stop one you're not using, update config vars, or delete a deployment entirely. Stopped bots show an amber countdown, restart within 24 hours or they're auto-deleted to keep the platform fast for everyone.

Common questions

Yes. Deploying bots on AHMED X costs nothing, no trials, no credit card, no hidden tiers. The platform is free by design; we keep it sustainable by auto-deleting bots that stay stopped or broken for 24 hours.

No. AHMED X hosts everything. You pick a bot from the catalog, paste your Session ID, and hit deploy, the build, hosting, and uptime are all handled for you.

Not at all. Deployment is a form: app name, Session ID, and a few settings the bot explains inline. If you can fill a signup form, you can deploy a bot.

Usually two to five minutes. You watch live logs while it builds, and the bot card flips to Running the moment it's online. Pairing your WhatsApp number adds another minute or two.

The Session ID is the credential that links your bot deployment to your WhatsApp number. You get it from the bot's pairing page after linking via an 8-character pairing code. Without it, the bot has no WhatsApp account to run on.

Technically yes, but we strongly recommend a spare number. WhatsApp may restrict numbers that run automation, and a ban would lock you out of your personal chats too.

Open My bots and press Restart on the bot card, most crashes clear with a restart. If it keeps crashing, the session is likely invalid: re-pair to get a fresh Session ID, update the config vars, and restart.

Yes. stopped bots are auto-deleted after 24 hours. The bot card shows the countdown. Restart any time before it ends to keep the deployment.

Yes. Open the bot from My bots, edit its config vars (like SESSION_ID, owner number, or prefix), save, and restart. Changes apply on the next start.

Every catalog bot ships with a plugin set listed on its Plugins tab, commands like .ping, .menu, and downloaders. Browse plugins per bot, copy any plugin's details, and like the ones you use. There's no install step; plugins come with the bot you deploy.

Troubleshooting

Codes expire after a few minutes. Generate a fresh code on the pairing site and enter it immediately on your phone: WhatsApp → Linked devices → Link a device → Link with phone number instead. Double-check you're linking the intended number, pairing the wrong one is the most common mistake.

WhatsApp sessions die if the linked phone stays offline too long or the number gets flagged. Generate a new Session ID on the pairing site, paste it into SESSION_ID in your bot's config vars on AHMED X, and hit Restart.

Press Restart on the bot card in My bots. If it crashes again within a minute, the session is almost certainly invalid, re-pair for a fresh Session ID, update the config vars, and restart. If it still crashes, check the deploy logs for a plugin error.

Check three things in order: 1) the bot card says Running, not Stopped or Crashed; 2) you're messaging the exact number you paired; 3) send .ping and wait up to a minute, first reply after a restart can be slow. Still silent? Restart the bot.

Yes. stopped bots are deleted automatically after 24 hours, and the countdown shows on the bot card. Restart any time before it hits zero to keep everything. Once deleted, you'd need to deploy fresh.

Refresh and request a new code. Pairing needs a stable connection on both your browser and your phone, switch to solid Wi-Fi on both if it stalls. Also confirm WhatsApp on your phone is updated; very old versions break the link-with-number flow.

Open the deploy logs and scroll to the red lines at the end. The usual suspects: SESSION_ID missing or pasted with a trailing space, app name with capitals or spaces, or a required var left empty. Fix it and redeploy, failed builds don't count against you.

WhatsApp sometimes bans numbers running bots, this is why we recommend a spare number. AHMED X can't unban numbers; you'd appeal inside WhatsApp itself. To avoid it: don't spam groups, keep broadcast lists small, and don't run two bots on one number.

Tips

App names must be lowercase letters, numbers and dashes, no spaces or capitals.
Use a spare WhatsApp number for bots. WhatsApp sometimes bans numbers running automation, so keep your personal number separate.
Pairing codes expire in minutes. Have your phone ready on the Linked devices screen before you generate one.
After any session change, update SESSION_ID in config vars and restart, the bot won't pick it up on its own.
Check the bot's plugin page before deploying. Knowing which plugins are built in saves you from installing extras later.
If a build fails, read the last 20 lines of the log. Nine times out of ten it's a missing or mistyped config var.
Restart a stopped bot before the 24-hour countdown ends, after that it's deleted permanently.
Test with .ping first after every fresh deploy. If .ping replies, the session and deployment are both healthy.
Keep your Session ID out of screenshots and group chats. Treat it like a password.
One number, one bot. Linking the same WhatsApp number to two deployments causes session conflicts.

Ready to deploy?

Your free WhatsApp bot could be replying to .ping in the next five minutes.

Open your dashboard