· 4 min · TextMeFlow Team

Send WhatsApp Messages from Notion — Automatically on a New Row

More and more small teams keep their leads, bookings or tasks in Notion instead of a CRM. That works fine for overview, but a new row in a Notion database won't send itself a WhatsApp message. This article shows how to set that up without code, using Notion, Make.com and the TextMeFlow API.

Why Notion as a trigger

Notion databases are often used as a lightweight CRM: a sales page with leads, a bookings overview, an intake form that writes to a database via Notion Forms or an embedded form. Every new or changed row is a natural moment to send someone a message.

Typical uses:

  • A new row in "Leads" with status "new" → a welcome message with a follow-up question.
  • A booking gets the status "confirmed" → a confirmation message with the date and location.
  • A task gets an owner and a deadline assigned → a reminder message to the customer or a colleague.

What you need

  • A Notion workspace with the database you want to use as a trigger.
  • A free TextMeFlow account with a linked WhatsApp number (QR scan, no Meta Business verification needed — see /en/docs/getting-started).
  • A Make.com account (the free plan is enough to test this).

Step 1: build the scenario in Make.com

  1. Create a new scenario and choose Notion → Watch Database Items as the trigger. Connect your Notion workspace (via an internal integration token, which you can create in Notion under Settings → Connections) and select the database.
  2. Add a Filter right after the trigger, for example on the "Status" column equal to "New" or "Confirmed" — that way you only react to rows that are ready for a message, not to every edit.
  3. Add a second module: HTTP → Make a request.
  4. Configure the HTTP module:
    • Method: POST
    • URL: your TextMeFlow send endpoint (found in your dashboard under API settings)
    • Headers: Content-Type: application/json and your API key as Authorization: Bearer <your-key>
    • Body (JSON), with fields mapped from the Notion properties:
{
  "to": "{{1.properties.Telefoonnummer.phone_number}}",
  "message": "Hi {{1.properties.Naam.title}}, your appointment on {{1.properties.Datum.date.start}} is confirmed!"
}
  1. Notion properties come with a type-specific structure (title, phone_number, date, select, ...) — Make shows the exact field names automatically once you click the trigger output, so test the module first with Run once before you finalize the mapping.

Step 2: prevent duplicate sends

"Watch Database Items" triggers on every change to a row that meets your filter — including a second time if someone later edits something else while the status stays the same. Solve this with a separate checkbox column "WhatsApp sent": filter the trigger on rows where that checkbox is still unchecked, and add an Update a Database Item module after the HTTP module that ticks the checkbox. That way you send each row exactly once, no matter how often Make checks the scenario.

Step 3: format phone numbers correctly

In Notion, preferably use a property of type "Phone" instead of plain text — that already enforces a more consistent format. Make sure the number is written internationally (for example 32470123456, without + or 00), otherwise the message won't arrive anywhere. A simple fix: add a Text parser step in Make that automatically converts a local number (0470...) to the international format before you send it to the API.

Personalize without spam risk

Because every message is personalized with a name, date or status field from Notion, it doesn't look like a bulk broadcast — exactly what protects your number from being blocked. TextMeFlow also automatically applies rate limiting, a risk score and respect for quiet hours to every outgoing message, regardless of which tool you send through. Want to understand in more depth how that works? Read /en/docs/anti-spam.

Alternative: n8n or Zapier

Prefer working with n8n (self-hosted, free) or Zapier? The principle is identical: a Notion trigger followed by an HTTP node to the same endpoint. We described that setup with all three tools in detail in Send WhatsApp Messages from n8n, Make.com or Zapier.

Know the limits

The free TextMeFlow plan gives you 50 messages per month, forever — enough to test this scenario. For production volumes (daily leads, bookings or tasks) you switch to a paid plan with higher quotas and, if needed, multiple linked devices from the Business plan.

Notion wasn't built as a CRM, but for small teams that already track everything in Notion, this is the fastest way to go from a manual copy-paste process to automatic WhatsApp communication — without needing a developer.

Ready to set it up yourself? Create a free account and send your first automated message within ten minutes.

Want to send WhatsApp messages via API yourself?

Free forever up to 50 messages/month. Scan a QR and send your first message within 5 minutes.

Free forever