Hi all,
I work on Turbo Notify, a service that links your own WhatsApp number to an API. We just published its Node-RED nodes as @turbo-notify/node-red-whatsapp (MIT, no dependencies).
What the nodes do
- whatsapp send: text, image, video, audio, document, sticker, location and replies, from your own number.
- whatsapp status: reads whether a message is pending, sent, delivered, read or failed.
- whatsapp events: starts a flow when something happens on your number, such as a message arriving. It polls every 30 seconds, keeps its cursor between deploys and delivers at least once.
- The API key is kept in the credentials store, so it never appears in an exported flow, and it is only sent over https.
Examples
Eighteen flows are ready to import (Import, then Examples): a door sensor alert, a daily report to a list (rate limited), a website down alert and a temperature alert that only speak when the state changes, an alert for errors in Node-RED itself, an order confirmation and an HTTP endpoint that sends a message (both refuse every call until you set a token), a menu by keyword, an after-hours reply, forwarding to a team group, a PDF, a store location, a delivery check and a CSV log. Each one runs in the package's test suite on the real core nodes.
Things you should know
- You need a Turbo Notify account with a number linked and a plan that covers the messages you send. There is no shared bot or demo number.
- It is not the Meta WhatsApp Business Platform: the number is linked like WhatsApp Web, so WhatsApp's rules apply to you. Please do not send unsolicited bulk messages; a number that spams can be restricted. The examples pace sends at one message every 5 to 10 seconds for that reason.
- Events are polled, not pushed.
README, scorecard and examples: node-red-whatsapp (node) - Node-RED
Documentation: Turbo Notify in Node-RED | Turbo Notify
Feedback is welcome, especially on the examples and on what you would want in the nodes.