Automate actions
Official Cloud API. Opt-in recipients. Template or 24-hour session.
WhatsApp is one workflow channel. Recipients must opt in. Aevico is not a WhatsApp broadcast or marketing suite.
Official Cloud API
Sends use the official WhatsApp Business Platform (Cloud API). Comply with Meta policies, consent, template rules, and messaging limits.
Example: approved template
Use a Meta-approved template for most sends. Session text is only for the 24-hour customer-care window.
| Field | Value |
|---|---|
| THEN | Send WhatsApp |
| Template name | item_alert |
| Template language | en |
| Body parameters | {title} then {url} |
| Session text | Leave empty unless you are inside the 24-hour window and skip the template. |
Fields
| Field | Notes |
|---|---|
| Credential | Meta Cloud API token on Integrations → WhatsApp. |
| From phone number id | Meta phone number id (often stored on the credential endpoint). |
| Recipients | Opted-in phones on Automate → WhatsApp. No send without opt-in. |
| Template | Approved name + language in Meta Business Manager (recipe: item_alert / en). Body params: one per line, in template order. |
| Session text | Only inside Meta’s 24-hour customer-care window if you skip a template. |
Workflows are not a broadcast product. There is no audience blast, campaign builder, or promotion engine on this channel.
32 articles on this site. Engineering notes on GitHub.
