Send WhatsApp messages automatically from your IoT devices when sensor data meets a condition you define — a temperature breach, a device going offline, a geofence exit. WhatsApp reaches your team and customers on a channel they already check, with no app install required and the option of two-way replies.
To send WhatsApp alerts from Ubidots, create an event with a trigger condition (value-based, inactivity, geofence, or context-based) and add a Send WhatsApp action that fires when the condition is met. The message can include dynamic placeholders like device name, current value, and timestamp.
DISCLAIMER: WhatsApp enforces strict messaging policies, and infringement can lead to your number getting banned. Read Events: Preventing your WhatsApp Number from Getting Banned before going to production.
When to use WhatsApp for IoT alerts
Field technicians and operators who already check WhatsApp dozens of times a day — alerts are seen faster than email.
Customer-facing notifications in LATAM, EMEA, and Southeast Asia, where WhatsApp is the default messaging app.
Two-way confirmations — recipients can reply to acknowledge an alert or send STOP to opt out.
Rich-content alerts — unlike SMS (capped at 140 characters), WhatsApp supports longer messages and is friendlier to dynamic data like device IDs and timestamps.
No-app-install workflows where SMS pricing is too high or push notifications aren't an option.
Requirements
An Ubidots account on the Industrial plan or higher.
For testing: Ubidots' shared sandbox WhatsApp number (recipients must message it once before they can receive alerts).
For production: a dedicated WhatsApp channel, provisioned by the Ubidots team. One-time setup cost: $30. Read the anti-ban guide before submitting a number for provisioning.
1. Create a new event
Go to the Data → Events section and click the + button at the top right. Choose the event type that matches your need: conditional, global, or scheduled.
Configure the trigger logic with AND/OR conditions. The trigger types are documented separately: value-based, inactivity, geofence, and context-based.
2. Configure the WhatsApp action
Once the trigger logic is set, click + add action and select Send WhatsApp.
Recipients — add one or more phone numbers, each with country code. Recipients must have messaged your sandbox or dedicated number at least once.
Active-trigger message — the body sent when the event fires. Use the tag icon at the top-right of the message field to insert dynamic placeholders: device name, variable name, current value, timestamp, and more.
Back-to-normal message (optional) — sent when the trigger condition stops being met. See Back-to-Normal Events.
Timestamp format — by default, timestamps render as
YYYY-MM-DD HH:mm:ss TZ. If you'd rather receive UNIX epoch milliseconds, double-click the timestamp tag in the message and delete everything after the pipe (|) symbol.Repeat action (optional) — fire the same WhatsApp message multiple times while the event stays active (max 50 repetitions).
Click Save.
3. Settings tab
Name the event, optionally add a description, apply tags for end-user visibility control, set a cooldown period (in seconds) to mute repeated firings, and define one or more active windows during which the event is allowed to run. Click Save.
Best practices (avoid getting your number banned)
WhatsApp's anti-spam algorithms are aggressive. The full guide is here; the short version:
Warm up new numbers — don't go from zero to broadcast. Send and receive real messages with real users for a few days first.
Have recipients message you first — a "Contact us on WhatsApp" link on your dashboard is the cleanest way.
Add a STOP option — "Reply STOP to unsubscribe" at the end of your messages reduces spam complaints, the #1 reason for bans.
Personalize — include
#{username}or device name so messages don't look templated.Don't blast at fixed intervals — vary timing.
Aim for ≥30% reply rate — invite recipients to acknowledge alerts.
Pricing & limits
Rate limit: 2 messages per minute per number, applied automatically. Excess messages are discarded.
Recipients per action: up to 5 numbers per action. Add multiple actions to fan out further.
Per-message billing: $10 per 1,000 messages.
Dedicated number provisioning: one-time $30 setup fee.
Plan availability: Industrial plan or higher.
Frequently asked questions
Why didn't my WhatsApp message arrive?
Common causes: (1) the recipient never messaged your sandbox or dedicated number, so they're outside the 24-hour conversation window; (2) the event is outside its active window; (3) the action is muted by the cooldown period; (4) the rate limit (2 msg/min) was hit and the message was discarded; (5) your number was banned — check WhatsApp's status and the anti-ban guide.
Can I send to numbers that haven't messaged me first?
Not reliably. WhatsApp strongly favors conversations the recipient initiated. The cleanest pattern is to publish a "Contact us on WhatsApp" link in your app or onboarding email and have end users tap it once.
Can I include sensor values, device names, and timestamps in the message?
Yes — use the tag icon at the top-right of the message field to insert dynamic placeholders. Timestamps default to human-readable format; switch to UNIX epoch milliseconds by deleting the |-suffix as described in step 4 above.
How is cooldown different from active windows?
Cooldown mutes the action for N seconds after it fires, so a flapping sensor doesn't spam the recipient. Active windows define the time-of-day or day-of-week intervals during which the event is allowed to run at all. They compose: an event must be inside an active window AND past its cooldown to fire.
What's the difference between WhatsApp and SMS for IoT alerts?
WhatsApp supports longer messages, two-way replies, and richer content, but requires recipient opt-in and a provisioned channel. SMS reaches any phone with no opt-in, but is capped at 140 characters and billed per country prefix. Use WhatsApp for customer or operator alerts in markets where WhatsApp dominates; use SMS for legacy or low-data-coverage scenarios. See the SMS section of the Voice Call article.
Related articles
Events: Voice Call Notifications (also covers SMS)