WhatsApp Business API for new lead manager notification
The scenario sends the sales manager a personalised WhatsApp template when a new lead is captured.
Use case overview
The scenario sends the sales manager a personalised WhatsApp template when a new lead is captured. The message includes the lead name, contact details, and source label. A static URL button opens the lead record in CRM.
Template example
🔔 New lead: {{1}}
Contact: {{2}}
Source: {{3}}
Contact the client as soon as possible while interest is high.
- {{1}}lead name or short label (e.g. Alexey K., B2B request)
- {{2}}lead contact (phone, email, or combined contact line)
- {{3}}lead source (e.g. website form, Instagram ad, partner referral)
- “Open in CRM”button — fixed in the Meta template

When to use it
Reach for this scenario when a new lead lands in CRM or a web form and the assigned sales manager needs to know immediately — not after checking email or refreshing a dashboard. It fits inside sales teams routing form leads to reps, agencies forwarding ad or landing-page leads to the duty manager, and small teams replacing slow email alerts with a mobile-friendly CRM deep link.
Workflow
- Capture event
CRM or the lead capture integration emits a new-lead event.
phone:"+…" - Resolves the manager phone
The system resolves the manager phone number and lead summary fields.
phone:"+…" - Build & send
An internal notification template is built with three body variables and a static URL button.
POST/sendTemplate - Delivered
The manager receives the WhatsApp alert on their phone.
delivered - Status tracked
Delivery result is logged; the manager opens CRM via the button to follow up.
status:"read"

Technical implementation
Prerequisites
- 1MSG API Key · How to get API Key
- WhatsApp Business account · How to Connect WABA
- WhatsApp Template · How to Approve WABA Template
- Customer opt-in · How to Manage Customers Consent
Code examples
#!/usr/bin/env bash
set -euo pipefail
# === Configuration (replace "___" placeholders) ===
API_BASE_URL="https://api.1msg.io" # production 1MSG API base URL
CHANNEL_ID="___" # channel ID from 1MSG dashboard
API_TOKEN="___" # channel JWT token (Bearer)
TEMPLATE_NAME="___" # approved template name
TEMPLATE_NAMESPACE="___" # template namespace (required — send fails without it)
TEMPLATE_LANGUAGE="___" # template language code, e.g. "en"
# === Test data ===
MANAGER_PHONE="___" # manager phone in international format
TEST_LEADNAME="___" # {{1}} lead name
TEST_LEADCONTACT="___" # {{2}} lead contact
TEST_LEADSOURCE="___" # {{3}} lead source
PHONE_NORM="$(printf '%s' "$MANAGER_PHONE" | tr -cd '0-9')"
for pair in "CHANNEL_ID=$CHANNEL_ID" "API_TOKEN=$API_TOKEN" \
"TEMPLATE_NAME=$TEMPLATE_NAME" "TEMPLATE_NAMESPACE=$TEMPLATE_NAMESPACE" \
"TEMPLATE_LANGUAGE=$TEMPLATE_LANGUAGE" "MANAGER_PHONE=$MANAGER_PHONE" \
"TEST_LEADNAME=$TEST_LEADNAME" \
"TEST_LEADCONTACT=$TEST_LEADCONTACT" \
"TEST_LEADSOURCE=$TEST_LEADSOURCE"; do
val="${pair#*=}"
if [ -z "$val" ] || [ "$val" = "___" ]; then
echo "Missing configuration value: ${pair%%=*}" >&2
exit 1
fi
done
if [ -z "$PHONE_NORM" ]; then
echo "Error: phone number has no digits after normalization" >&2
exit 1
fi
URL="${API_BASE_URL%/}/${CHANNEL_ID}/sendTemplate"
# params carries body ONLY. Button text is fixed in the Meta template — no button param.
# {{1}} lead name → ${TEST_LEADNAME}
# {{2}} lead contact → ${TEST_LEADCONTACT}
# {{3}} lead source → ${TEST_LEADSOURCE}
read -r -d '' PAYLOAD <<JSON || true
{
"phone": "${PHONE_NORM}",
"template": "${TEMPLATE_NAME}",
"namespace": "${TEMPLATE_NAMESPACE}",
"language": { "policy": "deterministic", "code": "${TEMPLATE_LANGUAGE}" },
"params": [
{
"type": "body",
"parameters": [
{ "type": "text", "text": "${TEST_LEADNAME}" },
{ "type": "text", "text": "${TEST_LEADCONTACT}" },
{ "type": "text", "text": "${TEST_LEADSOURCE}" }
]
}
]
}
JSON
RESPONSE="$(curl -s -w '\n%{http_code}' -X POST "$URL" \
-H "Content-Type: application/json" \
-H "Authorization: Bearer ${API_TOKEN}" \
-d "$PAYLOAD")"
HTTP_CODE="$(printf '%s' "$RESPONSE" | tail -n1)"
BODY="$(printf '%s' "$RESPONSE" | sed '$d')"
case "$BODY" in
*'"sent":true'*) ok=1 ;;
*) ok=0 ;;
esac
if [ "$HTTP_CODE" -ge 200 ] && [ "$HTTP_CODE" -lt 300 ] && [ "$ok" -eq 1 ]; then
echo "Message sent to manager."
echo "API response: $BODY"
else
echo "Send failed. HTTP status: $HTTP_CODE" >&2
echo "$BODY" >&2
exit 1
fi
Response and delivery status
HTTP 2xx and JSON "sent": true mean 1MSG accepted the message for sending — not that it already reached the customer's phone. Save the id field (looks like wamid.…) to correlate delivery callbacks.
{
"sent": true,
"id": "wamid.HBgLMzgwNjM5...",
"message": "Message accepted for delivery"
}sentAccepted for sending — not yet on the customer's phone
idStore it; delivery callbacks and
hookInfoare keyed on this
Delivery itself arrives later, as a separate callback. Register a webhook (POST …/webhook) and 1MSG POSTs status updates to your HTTPS endpoint in a top-level hooks[] payload.
{
"hooks": [
{
"id": "gBGGeSaGViBfAgnlzOSHEwK9O6F",
"type": "message",
"status": "sent",
"timestamp": "1654864094",
"recipient_id": "556123122026"
}
]
}statussent,delivered,read— or a failure status when applicableidCorrelates the callback with the
idreturned by the send calltimestampUnix seconds, as a string
If you would rather not receive callbacks, poll GET {base}/{channel}/hookInfo?messageId=<id> instead. In practice delivery often completes within seconds — but the API contract does not guarantee it, so never block a flow waiting on it.
Common errors
| Status | Response | Cause |
|---|---|---|
| 200 | Message was not sent: template is not defined | namespace, template or language missing from the request body. |
| 200 | template name (…) does not exist in <language> | The template is approved in a different language than the one requested. |
| 200 | Message was not sent: provide chatId, phone, bsuid, or username | No recipient the channel could resolve. |
| 403 | access denied | The token is wrong, or belongs to a different channel than the URL. |
| 429 | too many requests. please try later | The channel is over its send rate. |

