Downloaders • Group tools • AI • Media & fun commands — all wrapped in a clean, snowflake-themed menu, with every reply carrying the official ES TEAMS channel badge.
Type .menu to see everything it can do.
All variables below are optional — the bot boots fine with none of them set (QR login, session resets on every restart). Set them in your host's environment variables panel (Render → Environment), or in a local .env file if running on your own machine.
┌──(es-teams-v1)──[ ENVIRONMENT ]
│
├─ PHONE_NUMBER = 2349037524605
├─ SELF_URL = https://your-app.onrender.com
├─ SESSION_PATH = /opt/render/project/data/ES_TEAMS-SESSION
├─ MONGODB_URI = mongodb+srv://user:pass@cluster.mongodb.net/dbname
├─ RENDER_DEPLOY_HOOK_URL = https://api.render.com/deploy/srv-xxxxx?key=yyyy
├─ UPDATE_REPO = paskito002/ES_TEAMS-V1
└─ UPDATE_BRANCH = main| Variable | Required | What it does |
|---|---|---|
PHONE_NUMBER |
❌ | Your WhatsApp number, digits only with country code, no + (e.g. 2349037524605). Set it to log in via pairing code. Leave blank to log in by scanning a QR code instead. |
SELF_URL |
❌ | This deployed service's own public URL. When set, the bot pings itself every 5 minutes so free-tier hosts don't spin the service down from inactivity. |
SESSION_PATH |
❌ | Folder to store the WhatsApp session in. Only needed if you attached a persistent disk — set this to that disk's exact mount path so your login survives restarts. |
MONGODB_URI |
❌ | Alternative to SESSION_PATH — stores the session in MongoDB instead of a disk. This is the one that actually survives a Render redeploy (a redeploy is a brand new container — local disk and process memory are both wiped either way). Use one or the other, not both. |
RENDER_DEPLOY_HOOK_URL |
❌ | Only relevant on Render. Lets the bot owner trigger a real redeploy from inside WhatsApp by typing .restart. Get it from your Render service → Settings → Deploy Hook. |
UPDATE_REPO / UPDATE_BRANCH |
❌ | Which GitHub repo/branch the bot checks against to know if it's out of date. Defaults to this repo's main. Only override if you maintain your own fork and want the bot to compare against that instead. |
💡 Leaving
SESSION_PATHandMONGODB_URIblank is fine — the bot just won't remember its login across restarts, so you'll need to re-pair each time it redeploys.
Two separate things put a bot to sleep, and they need different fixes.
1. The host spins the service down. On Render's free tier a web service sleeps after ~15 minutes with no inbound traffic. The bot self-pings every 4 minutes to prevent this — but a self-ping cannot wake an instance that has already gone to sleep, because the sleeping process is the thing doing the pinging. The moment it sleeps for any reason (a deploy, a host restart, a brief network gap), nothing brings it back until someone opens the URL.
The reliable fix is an external pinger:
- Set
SELF_URLto your service's public URL. Check the logs — if you see<-- LOCALHOST ONLYnext to the ping line, it is not set correctly and is doing nothing useful. - Create a free monitor at UptimeRobot or [cron-job.org] pointed at that same URL, on a 5-minute interval.
That external hit both keeps the service awake and wakes it if it ever does sleep. The only way to remove the problem entirely rather than work around it is a paid instance, which never sleeps.
2. The WhatsApp session gets dropped. If the session isn't stored somewhere permanent, every restart loses the login and demands a new pairing code. Set MONGODB_URI — it is the only option here that survives a redeploy, because a redeploy replaces the whole container (local disk included). The bot also now retries transient bad-session errors several times before giving up and asking to re-pair, so a brief server-side hiccup no longer costs you the login.
By default, Render redeploys your service automatically the moment this repo changes, which drops your WhatsApp connection without warning. If you'd rather control when that happens:
- Set
RENDER_DEPLOY_HOOK_URL(see table above). - In your Render service → Settings → Build & Deploy, turn Auto-Deploy off.
- When new code lands, the bot checks GitHub periodically (every few hours, and once on connect) and, if it's running an older commit than
UPDATE_REPO/UPDATE_BRANCH, DMs the bot owner: "Your ES TEAMS V1 is out of date. Type .restart to get the latest version and relink." - Typing
.restart(owner only) hits the deploy hook and triggers a real Render redeploy on your own schedule.
This detection only runs on Render (it reads Render's own RENDER_GIT_COMMIT variable), so it's silently inactive on any other host.
- ES TEAMS V1 is not made by WhatsApp Inc. Misusing the bot may get your WhatsApp account banned — use it at your own risk.
- ES TEAMS V1 is not openly licensed for free redistribution or resale — please don't clone or rebrand it without permission from ES TEAMS TECH.
