WhatsApp Business Platform (Meta Cloud API)

Technical Preview

Overview

A client-mode connector for a curated messaging slice of the WhatsApp Cloud API on Meta Graph v21.0:

Catalog connector event	Entity / path	Notes
POST messages (template)	`POST /{phone_number_id}/messages`	`type=template` + body params (alarms)
POST messages (text)	`POST /{phone_number_id}/messages`	`type=text` within 24h window
GET phone number	`GET /{phone_number_id}`	Bearer credential check
GET message_templates	`GET /{whatsapp_business_account_id}/message_templates`	List WABA templates
Inbound webhook (secondary)	Meta Cloud API webhooks	Client-mode package; webhook → MQTT out of scope

Default BASE_ADDRESS is https://graph.facebook.com/v21.0. Topics use messaging/whatsapp-business-platform/<object>/<verb>.

All events send Authorization: Bearer {access_token} (system user / permanent token). Prefer Hub secrets (WHATSAPP_ACCESS_TOKEN / WHATSAPP_TOKEN). Use the WhatsApp Business phone number ID in the path — not the customer MSISDN. Graph returns OAuthException 190 on bad tokens.

Basic Syntax

# Coreflux REST_API template — WhatsApp Cloud API Graph v21.0
# Auth: Bearer {value.json.access_token}
# BASE_ADDRESS: https://graph.facebook.com/v21.0

DEFINE CONNECTOR WhatsAppBusinessPlatformRestApi WITH TYPE REST_API
    ADD REST_API_CONFIG
        WITH BASE_ADDRESS "https://graph.facebook.com/v21.0"
        WITH ENABLE_CLIENT "true"
        WITH USE_SSL "true"
        WITH REQUEST_TIMEOUT '60'
        WITH DEFAULT_CONTENT_TYPE "application/json"
    ADD EVENT Getphonenumber
        WITH SOURCE_TOPIC "messaging/whatsapp-business-platform/phone/get"
        WITH DESTINATION_TOPIC "messaging/whatsapp-business-platform/phone/get/response"
        WITH METHOD "GET"
        WITH ENDPOINT "/{value.json.phone_number_id}"
        WITH HEADERS
            ADD "Accept" "application/json"
            ADD "Authorization" "Bearer {value.json.access_token}"
    ADD EVENT Sendtextmessage
        WITH SOURCE_TOPIC "messaging/whatsapp-business-platform/message/send-text"
        WITH DESTINATION_TOPIC "messaging/whatsapp-business-platform/message/send-text/response"
        WITH METHOD "POST"
        WITH ENDPOINT "/{value.json.phone_number_id}/messages"
        WITH HEADERS
            ADD "Accept" "application/json"
            ADD "Content-Type" "application/json"
            ADD "Authorization" "Bearer {value.json.access_token}"
        WITH BODY "{payload}"
    ADD EVENT Sendtemplatemessage
        WITH SOURCE_TOPIC "messaging/whatsapp-business-platform/message/send-template"
        WITH DESTINATION_TOPIC "messaging/whatsapp-business-platform/message/send-template/response"
        WITH METHOD "POST"
        WITH ENDPOINT "/{value.json.phone_number_id}/messages"
        WITH HEADERS
            ADD "Accept" "application/json"
            ADD "Content-Type" "application/json"
            ADD "Authorization" "Bearer {value.json.access_token}"
        WITH BODY "{payload}"
    ADD EVENT Listmessagetemplates
        WITH SOURCE_TOPIC "messaging/whatsapp-business-platform/template/list"
        WITH DESTINATION_TOPIC "messaging/whatsapp-business-platform/template/list/response"
        WITH METHOD "GET"
        WITH ENDPOINT "/{value.json.whatsapp_business_account_id}/message_templates"
        WITH HEADERS
            ADD "Accept" "application/json"
            ADD "Authorization" "Bearer {value.json.access_token}"

Auth and secrets

Create a Meta app with WhatsApp product / Cloud API access and a system user (or permanent) token with whatsapp_business_messaging (and related) permissions.
Store the token as Hub secret WHATSAPP_ACCESS_TOKEN (alias WHATSAPP_TOKEN).
Note your WhatsApp Business phone_number_id and WABA id from Meta Business Suite / WhatsApp Manager.
Publish MQTT JSON that includes access_token (or inject via Hub) plus path ids.

Never commit real tokens.

Example payloads

Phone number

{
  "access_token": "YOUR_WHATSAPP_ACCESS_TOKEN",
  "phone_number_id": "YOUR_PHONE_NUMBER_ID"
}

Text message

{
  "access_token": "YOUR_WHATSAPP_ACCESS_TOKEN",
  "phone_number_id": "YOUR_PHONE_NUMBER_ID",
  "messaging_product": "whatsapp",
  "to": "15551234567",
  "type": "text",
  "text": { "body": "Coreflux alarm: Zone A vibration" }
}

Template (alarm params)

{
  "access_token": "YOUR_WHATSAPP_ACCESS_TOKEN",
  "phone_number_id": "YOUR_PHONE_NUMBER_ID",
  "messaging_product": "whatsapp",
  "to": "15551234567",
  "type": "template",
  "template": {
    "name": "coreflux_alarm",
    "language": { "code": "en_US" },
    "components": [
      {
        "type": "body",
        "parameters": [
          { "type": "text", "text": "Zone A" },
          { "type": "text", "text": "vibration high" }
        ]
      }
    ]
  }
}

Install

The template ships with the broker. List it with -listTemplates or fetch it from the Hub catalog.
Deploy WhatsAppBusinessPlatformRestApi.lot only (not hub-metadata.lot).
Smoke with GET /{phone_number_id} → 200 before sending production templates.

References

Cloud API overview
Messages reference
Text messages
Meta Postman: WhatsApp Business Platform collection
Coreflux: REST API Connectors

Last modified on October 26, 2026

⌘I

Quick Start

Coreflux MQTT Broker

LoT Language

Coreflux HUB

VS Code - LoT Notebooks

Coreflux Portal

Using AI with Coreflux

Product Updates

WhatsApp Business Platform (Meta Cloud API)

Overview

Basic Syntax

Auth and secrets

Example payloads

Install

References

​Overview

​Basic Syntax

​Auth and secrets

​Example payloads

​Install

​References

Overview

Basic Syntax

Auth and secrets

Example payloads

Install

References