jameswniu

Agentic Whatsapp Actions API Daemon — Development skill for Claude Code

Development community

WhatsApp's official API is Business-only and never touches your personal chats or groups.

How to install Agentic Whatsapp Actions API Daemon

This entry records only its repository, not the path inside it, so there is no exact command to give. Open jameswniu/agentic-whatsapp-actions-api-daemon and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Agentic Whatsapp Actions API Daemon does

WhatsApp's official API is Business-only and never touches your personal chats or groups. This wraps the WhatsApp Web protocol in a local HTTP API any client can drive: agents (OpenClaw, Claude Code), production AI, cron, curl. Deterministic enough to trust with a real account: dry-run default, gated mutations, queryable action IDs.

Alternatives in Development

Om Tidy — Self-maintenance pass — acts on every hygiene flag: archives completed work, groups loose clusters, splits ove 4.6k ★
Bypass 403 — Probe a 403/401 endpoint with the most-paid bypass tricks (header injection, path encoding, method swap, WAF f 4.5k ★
Clawgod — This is NOT a third-party Claude Code client 837 ★

README

agentic-whatsapp-actions-api-daemon

**A local HTTP API that makes a personal WhatsApp account scriptable, with the brakes built in.**

WhatsApp's official Cloud API is a business product. It requires a WhatsApp Business Account and a registered number, it is gated behind business verification, and it has no access to a personal account's chats, contacts or groups. If you want an agent, a cron job or a shell script to act on *your own* WhatsApp, the official API is not a worse option. It is not an option.

The protocol that can do it is the WhatsApp Web multi-device protocol, which [whatsmeow](https://github.com/tulir/whatsmeow) speaks by pairing as a linked device, the same way WhatsApp Web on a laptop does. But a raw protocol library hands a caller unguarded control of a real account, which is exactly the wrong thing to give an autonomous process.

This is whatsmeow with an envelope around it.

Read this before you run it

Linking any unofficial client to a personal account **violates WhatsApp's Terms of Service**. Meta says so directly in [About unofficial apps](https://faq.whatsapp.com/1217634902127718) and [Unauthorized use of automated or bulk messaging](https://faq.whatsapp.com/5957850900902049).

The ban risk is documented, not hypothetical. whatsmeow's own issue tracker carries [#807](https://github.com/tulir/whatsmeow/issues/807) and [#810](https://github.com/tulir/whatsmeow/issues/810), which report account warnings and bans including at low volume. Risk scales with automation volume, which is precisely what a daemon like this enables.

Nothing here reduces that risk, and no gate in this repo changes the ToS position. The gates exist to stop *your own* automation from doing something irreversible. Run it on an account you can afford to lose.

Why a daemon and not a library call

whatsmeow holds a paired session backed by a SQLite store. Pairing is interactive and the session must persist, so it cannot be spun up per command. Something has to stay