New

Whatsback Web: Automate Whatsapp With Power & Responsibility

Hello Punk! I am darkterminal a Software Freestyle Engineer. Let’s cut to the chase: WhatsApp automation is a double-edged sword. We all crave tools to streamline messaging, but dancing with unofficial APIs is risky business. Today, I’m pulling back the curtain on Whatsback Web—a project born from late-night coding sessions and a stubborn refusal to accept "impossible." But first: this isn’t a fairy tale. Use it wisely, or face the wrath of WhatsApp’s banhammer.

Why I Built Whatsback Web?

You Can Dive Deeper in My Previous Blog. This project has been my playground ever since whatsapp-web.js first hit the scene. It’s been a wild, fun ride—like a high-stakes game of cat and mouse. Sure, I’ve sacrificed a lot of phone numbers along the way (RIP to those brave souls). But here’s the thing: I’ve learned, observed, adapted, and most importantly—I’ve survived.

Why I Built Whatsback Web—And Why It’s Different From Other Tools

Imam Ali Mustofa ・ Feb 21

#webdev #automation #whatsapp #opensource

This isn’t just a project; it’s a testament to stubbornness and curiosity. Every ban, every roadblock, every “this shouldn’t work” moment has been a lesson. And now, I’m here to share the spoils of that battle with you.

It’s gonna be a bumpy ride—but hey, that’s where the fun is.
darkterminal - The guy who refuses to quit.

Who Likes Spam?!

Let me be clear: I hate spam. It’s annoying, disruptive, and downright infuriating. No wonder WhatsApp comes down hard with those permanent bans. Imagine this: a brand-new number with zero interaction history suddenly blasting out a flood of messages and hammering the server with requests. Damn, that’s just unfair.

Spam isn’t just a nuisance—it’s a violation of trust. It clogs up the system, ruins the experience for everyone. That’s why I’ve built this project with restraint in mind. It’s not about spamming; it’s about smart, responsible automation.

So, if you’re thinking of using this tool to flood people’s chats, think again. Play nice, or face the consequences. WhatsApp doesn’t mess around, and neither should you.

Using WhatsApp Web

This project is built on top of whatsapp-web.js—a library that gives you superpowers to interact with WhatsApp Web programmatically. No heads, no hassle. But don’t expect a ton of crazy features here. Why? Because I’ve already gone crazy enough building this thing.

The whole point of Whatsback Web is to give you a useful tool to save time in your business. It’s about efficiency, not overcomplication. With its REST API, you can forward messages, send automated texts, and integrate it seamlessly into your website or app.

await fetch(`${WHATSBACK_URL}/api/message/send-message`, { 
  method: "post", 
  headers: { 
    "Content-Type": "application/json" 
  }, 
  body: JSON.stringify({ 
    number, 
    message: job.message, 
  }), 
});

Getting Started

There is 2 way to install and use Whatsback Web

Docker (The Easy Way)

When using docker installation you've 2 options, using Docker CLI or Docker Compose.

Docker CLI

Pull the image:

   docker pull ghcr.io/darkterminal/whatsback-web:latest

Create Network

  docker network create whatsback-net

Create Volume

  docker volume create whatsback-db

Run Whatsback Application Container

  docker run -d \ 
    --name whatsback-app-provider \ 
    --network whatsback-net \ 
    -p 8169:5001 \ 
    -e NODE_ENV=production \ 
    -e APP_PORT=5001 \ 
    -e DB_PATH=/data/database.sqlite \ 
    -v whatsback-db:/data \ 
    ghcr.io/darkterminal/whatsback-web:latest

Run Whatsback Cronjob Container

  docker run -d \ 
    --name whatsback-app-cronjob \ 
    --network whatsback-net \ 
    -e NODE_ENV=production \ 
    -e APP_HOST=whatsback-app-provider \ 
    -e DB_PATH=/data/database.sqlite \ 
    -v whatsback-db:/data \ 
    ghcr.io/darkterminal/whatsback-web:latest \ 
    sh -c "./wait-for whatsback-app-provider:5001 -t 120 -- node cronjob.js"

Docker Compose

# docker-compose.yml or compose.yml 
services: 
  app: 
    image: ghcr.io/darkterminal/whatsback-web:latest 
    container_name: whatsback-app-provider 
    ports: 
      - "${UI_PORT:-8169}:5001" 
    environment: 
      - NODE_ENV=production 
      - APP_PORT=${APP_PORT:-5001} 
      - DB_PATH=/data/database.sqlite 
    volumes: 
      - db-data:/data 
    networks: 
      - app_net 
    healthcheck: 
      test: ["CMD-SHELL", "curl -f http://localhost:$$APP_PORT/health || exit 1"] 
      interval: 15s 
      timeout: 10s 
      retries: 5 
 
  cronjob: 
    image: ghcr.io/darkterminal/whatsback-web:latest 
    container_name: whatsback-app-cronjob 
    environment: 
      - NODE_ENV=production 
      - APP_HOST=app 
      - DB_PATH=/data/database.sqlite 
    volumes: 
      - db-data:/data 
    command: sh -c "./wait-for app:5001 -t 120 -- node cronjob.js" 
    networks: 
      - app_net 
    depends_on: 
      app: 
        condition: service_healthy 
 
networks: 
  app_net: 
    driver: bridge 
 
volumes: 
  db-data:

Source Installation

git clone https://github.com/darkterminal/whatsback-web.git   
cd whatsback-web   
npm install   
NODE_ENV=production node server.js

???? The Elephant in the Room: Security & Risks

Let’s be blunt:

WhatsApp hates bots (Me too). Using this could get your account banned.
We’ve added armor (Helmet, rate-limiting), but no guarantees.
This project isn’t affiliated with WhatsApp. Use at your own risk.

☕ Support the Madness

Building tools like this burns caffeine and sanity. If Whatsback Web saves you time:

GitHub Sponsors - International Supporter
Saweria - Indonesian Supporter

Checkout The Whatsback Web - GitHub Repository

???? Final Warning

This isn’t a toy. It’s a proof-of-concept for developers who understand the risks. If you’re looking for a “safe” solution, walk away.

???? Tips to Survive the WhatsApp Jungle

Let’s keep it real: using Whatsback Web isn’t a free pass to go wild. WhatsApp’s algorithms are watching, and they don’t play nice. Here’s how to stay under the radar and keep your account alive:

Age Matters:

Make sure the number you’re using is at least 2 weeks old (my personal sweet spot is 1 month). Fresh numbers scream “bot” and get slapped with bans faster than you can say “Oops.”
Keep It Active:

Use a number that’s actively used for daily interactions. Dormant numbers are red flags. WhatsApp loves activity—so give it what it wants.
API Etiquette:

Use the REST API wisely. Don’t bombard the server with endless requests. Space them out, be patient, and don’t whine when things don’t go your way.
No Spam, Ever:

This can’t be stressed enough. Avoid spam like the plague. It’s not just annoying—it’s a one-way ticket to Bannedville.

Remember:

This isn’t about gaming the system—it’s about working smarter. Play by the rules, and Whatsback Web will be your best friend. Break them, and well… good luck explaining to your boss why your WhatsApp account got nuked.

Stay smart,

darkterminal

The guy who’s been there, done that, and lived to tell the tale.

Disclaimer: Follow these tips, or prepare to face the consequences. Your call.

Back to Listing

credit: