Notion Database Item to WhatsApp Alert
Looks up the related Notion page for every new database entry and pushes its details to a WhatsApp number so nothing sits unnoticed in the workspace.
Use this templateWhy use it
Your team lives in Notion, but nobody lives inside Notion all day. A new request lands in the intake database, a bug gets filed, a client fills in the form that writes to your tracker — and it just sits there until someone happens to open the page and scroll. Notion's own notifications are easy to mute and easier to miss, so the first time you hear about an urgent item is when the person who submitted it follows up asking why nothing happened. Response times slip, small requests turn into complaints, and you end up refreshing a database view out of anxiety instead of trusting that you'll be told.
How it works
- 1Notion watches the database you choose and fires the moment a new item appears in it, whether it was typed in by a teammate, added by a form, or created by another tool.
- 2Notion is queried again to fetch that specific page, so you get the full record — the properties, the fields filled in on creation, the details that the trigger alone doesn't carry.
- 3WhatsApp delivers a message to the number you nominate, sent through WhatsScale from your existing WhatsApp line, carrying the item's details so the person on call can read it and act without opening the workspace.
What it connects
- Notion
- WhatsScale
Questions
Can I control what the WhatsApp message actually says?
Yes. The message text is written by you and can pull in any property the lookup returned — title, status, owner, priority, a link back to the page — so the alert reads the way your team needs it to.
Why does it look up the page after the trigger already fired?
The trigger tells you an item was created; the lookup returns the full record for that item. Fetching the page means your alert can include the actual field values rather than just an ID and a timestamp.
Does this work for edits to existing items, or only brand new ones?
Only new items. The trigger fires on creation in the chosen database, so editing a property on a row that already exists will not send a message. Use it for intake, requests, bug reports and similar first-touch events.
Can the alert go to more than one person?
One number is configured per send step. To reach a team, point it at a WhatsApp group you control, or duplicate the send step with a second recipient number in it.
What happens if the database gets a burst of new rows at once?
Each new item is handled separately, so a batch of ten entries produces ten messages. If your database receives high volume, point the automation at a filtered view or a dedicated intake database rather than your busiest tracker.
Do I need a WhatsApp Business API approval before this works?
No. WhatsScale connects the WhatsApp number you already use, so there is no application process or waiting period before the first alert can go out.