// the find
wppconnect-team/wppconnect
WPPConnect is an open source project developed by the JavaScript community with the aim of exporting functions from WhatsApp Web to the node, which can be used to support the creation of any interaction, such as customer service, media sending, intelligence recognition based on phrases artificial and many other things, use your imagination
WPPConnect drives a real WhatsApp Web session via Puppeteer to expose sending, receiving, groups, labels, catalogs, and more to Node. It's aimed at people building WhatsApp bots or customer-service automation who don't have (or don't want) access to Meta's official Business API.
The layer split (group, labels, catalog, business, newsletter, status, etc.) covers far more of WhatsApp's actual feature surface than most competing libraries, and multi-session support is a first-class concept rather than something bolted on later. Token store is a pluggable abstraction (file/memory) so session persistence across restarts is already solved. CI is real: build, lint, CodeQL and commitlint all gate PRs, and releases go through release-it instead of manual tags.
This is Puppeteer scraping the WhatsApp Web DOM, not a stable API — WhatsApp ships UI/internal changes that break it, and the README's own 'Update checking' section is effectively an admission that staying on the latest version is mandatory, not optional. Automating WhatsApp outside the official Business API carries real risk of numbers getting banned, and that operational risk is never mentioned anywhere in the docs. The maintainer states outright in the README that more maintainers are needed because they can't keep up with updates alone — a bus-factor problem the project is open about but hasn't solved. The injected browser-side code in src/lib/wapi is plain untyped JS sitting inside an otherwise TypeScript codebase, so the part that actually talks to WhatsApp has no type safety.