builderbot
A Node library for building WhatsApp chatbots as scripted conversation flows. Its README describes it as agnostic to the WhatsApp provider, so the provider is a choice you make and not one it makes for you.
What you need
a WhatsApp number you can connect, Node >=18 and npm, and your own code -- this is a library you build a bot with, plus whichever WhatsApp provider you choose to sit behind it
Gathered from the project’s own documentation on 2026-09-13. We have not verified that this list is complete.
Terms that apply
This library binds to no WhatsApp provider of its own: whether the clause below applies depends on which provider you put behind it — Meta’s official Business Platform, or something that drives a consumer account. WhatsApp’s Terms of Service, which we read on 2026-09-13, say a user must not use the service in ways that “involve sending illegal or impermissible communications such as bulk messaging, auto-messaging, auto-dialing, and the like” or that “involve any non-personal use of our Services unless otherwise authorized by us”, at https://www.whatsapp.com/legal/terms-of-service as we read it on 2026-09-13. We are not your lawyer and this is not advice about your particular use; read the terms yourself.
Receipts
What we saw ourselves, with the date we saw it.
How we checked
On 2026-09-13 we read this project’s repository metadata, its file tree and its manifest files through the GitHub API, and followed the outbound link far enough to confirm the address resolves — not that what is behind it is what this page says. That is a records check, not an assessment of the software. What we ran ourselves is linked under Receipts above; each linked receipt page names the method, the toolchain and the result. We installed or resolved its dependencies and nothing more. We did not run the software itself.
What the words mean here. Last commit is the date of the newest commit on the default branch, not the date of the repository’s last push to any branch. A licence name is GitHub’s own detection, not our reading of the licence file. A version floor is what the named manifest file declares, quoted from that file. A gap in months is printed whenever it is 12 complete months or more. A licence is not a price. It says what you may do with the source; it says nothing about whether the author sells a hosted tier, a paid image or support. Where this page states a cost, that is something we read and dated. Where it states none, we did not look. Where a receipt is linked above, the file it names may not be the file named for the version floor: the floor is read from whichever manifest declares it, while the receipt names whichever manifest the installer was pointed at. They answer different questions.
We do not republish this project’s own material — its README, code, configuration or assets. The link is where those live. What is on this page is ours: what we found, what we ran, and the date we looked.