The Meta Cloud API integration — automated sends with no one clicking a wa.me link, triggered by welcome messages, inactivity, pending invites, and future campaigns. Separate from the manual WhatsApp Outreach tool.
Send to any number you enter, using an approved template — the same path a real trigger will use, so a successful test here means the pipeline actually works. Logged under cms_test_send below, does not touch any per-device "already sent" state.
Each trigger is a Campaign doc — flip enabled from the Campaigns page once you're ready to go live.
| Key | Name | Tier | Enabled | What it does |
|---|
Every template ends with the deep link (generated per-template, not stored here), then a blank line, then these static lines, in order. Each line is a URL or "Label: URL", e.g. "Android: https://play.google.com/...". Change them here once, then click "Apply to all templates" to recompose every template's message body instead of editing each one by hand. Meta still needs each changed template re-submitted and re-approved afterward — this only keeps our own record in sync.
A template can only send once Meta has approved it under this exact name. "Preview" shows the message text with sample values filled in — submit that exact English wording to Meta Business Manager (as positional {{1}}, {{2}}... params), then flip the status here once approved. A test send and every real trigger both refuse to fire until this says "approved".
| Key | Meta template name | Category | Message | Status |
|---|
| Phone | Trigger | Message sent | Lang | Status | Failure reason | Sent |
|---|
Numbers that replied STOP, or were opted out manually. Checked before every automated send, including test sends.
| Phone | Source | Opted out |
|---|