Projects

WhatsApp Ops Bot (scoped to one group)

Production WhatsAppAutomationGuardrails

WhatsApp bot locked to one NOC group: per-area monitoring reports on command, with an allowlist, cooldowns and timeouts so it never spams.

Problem

NOC coordination over chat got noisy: the same monitoring requests again and again, in different formats. A bot that answers in every group is a risk, so the automation had to be tightly scoped.

My role

Built and run it: command design, guardrails and the link to the monitoring report pipeline.

Scale

  • 1 allowed group
  • About 30 monitoring areas

What I built

  • Hard allowlist: the bot only listens and answers in one group.
  • Command router with monitoring <area>; areas come from a config file.
  • Cooldowns and timeouts against spam and loops.
  • Handlers return the PNG report from the monitoring pipeline.
  • Runs 24/7 as a service.

Architecture

  1. Chat

    • NOC WhatsApp group

  2. Bot

    • Allowlist + command router
    • Area config

  3. Report

    • Playwright renderer → PNG

  4. Source

    • Monitoring dashboard
The PNG goes back to the same group; every other chat is ignored.

Outcome

  • Monitoring requests are one-line commands with the same clean format every time.
  • The bot stays silent outside the allowed group.
  • No more manual screenshots from the dashboard.

Stack

Node.jsOpenClawWhatsAppPlaywrightAllowlist / cooldown
GitHub

Next project

ISP PPPoE Platform on MikroTik