A browser-based WhatsApp management interface built on top of Evolution API v2. No installation, no Node.js, no build step — just open index.html.

Current version: v1.5.0

• A running Evolution API v2 instance (self-hosted)
• A connected WhatsApp instance on that server
• A modern browser (Chrome / Edge / Firefox)

1. Download or clone this repo
2. Open index.html directly in your browser
3. Click the Settings gear button in the top-right
4. Fill in:
   • Business / App Name — display name shown in the header (e.g. your company name)
   • Server URL — your Evolution API base URL (e.g. https://your-server.com)
   • Instance Name — the WhatsApp instance name configured in your Evolution API
   • API Key — your Evolution API key
5. Click Save — credentials are stored locally in your browser (never sent anywhere else)

A full WhatsApp-style chat inbox — browse all conversations, send and receive messages in real time.

• Browse & Send — fetch all groups, select one or more, broadcast a message
• Create Group — create a new group with participants
• Manage Group — update subject, description, picture, participants, settings, invite links, ephemeral timer

• Send to multiple recipients or groups with a randomized delay between messages (configurable min/max seconds) to simulate human sending behavior

Schedule any Compose or Group Broadcast job to send automatically at a future time. The browser tab must remain open — it does not need to be the active tab.

• Jobs are stored in IndexedDB (survives page refresh, handles large payloads)
• Scheduler polls every 30 seconds via a Web Worker — fires reliably even when the tab is in the background; jobs execute in order with the configured random delay between messages

• Validates phone numbers using libphonenumber-js
• Auto-normalizes local numbers to E.164 format (e.g. 0501234567 → 972501234567 for IL)
• Configure default country in Settings for local number parsing

When hosting on a web server, you can pre-configure all settings centrally using a config.json file placed next to index.html. Users won't need to touch Settings — everything is loaded automatically.

Copy config.example.json → config.json and fill in your values:

{
  "appName":  "My Business",
  "base":     "https://your-evolution-api-server.com",
  "instance": "MyInstance",
  "apikey":   "your-api-key-here",
  "country":  "IL",
  "delayMin": 1,
  "delayMax": 5
}

Any field can be omitted — omitted fields fall back to the user's local browser settings.

Note: config.json is listed in .gitignore so your credentials are never committed to the repo.

• Credentials are stored in your browser's localStorage (local use) or in config.json on your server (hosted use)
• Nothing is hardcoded in the source — the repo contains zero credentials
• Credentials never leave your browser except in direct API calls to your own Evolution API server

See CHANGELOG.md for full version history.

MIT — free to use and modify.