WhatsApp templates
MarkdownCreate, edit, sync and test WhatsApp message templates.
template_send_test
Section titled “template_send_test”Send a test WhatsApp template · Changes data · can overwrite or remove · Listed to the agent from the start
Sends a real test message with an APPROVED template to a WhatsApp number. It consumes credits like any outbound message: get the user’s OK first. to_number must be international E.164, +[country code][number], no spaces or dashes (for example +14155551234); if the user gives a local number, ask for the country. If the template has N {{n}} variables, params must hold exactly N values in order; otherwise omit params.
| Argument | Type | Required | Description |
|---|---|---|---|
element_name |
string | Yes | |
to_number |
string | Yes | |
descripcion |
string | No | One short sentence: what this call changes and why (10-200 chars, no personal data). |
params |
array | No |
template_create
Section titled “template_create”Create a WhatsApp template · Changes data · can overwrite or remove · Reached with dakso_explore
Creates a WhatsApp template and submits it to Meta for approval (UTILITY is approved in minutes; MARKETING can take 24-48 h and needs an opt-out footer). element_name: lowercase_with_underscores, 3-64 chars. Header and footer up to 60 chars, body up to 1024. If body or header use {{1}}, {{2}}…, pass example_values with exactly that many realistic values (Meta rejects ‘test’ or ‘123’). buttons: up to 3 of {type: QUICK_REPLY | URL | PHONE_NUMBER, text, url?, phone_number?}. Confirm the content with the user first.
| Argument | Type | Required | Description |
|---|---|---|---|
category |
string | Yes | |
content |
string | Yes | |
element_name |
string | Yes | |
buttons |
array | No | |
descripcion |
string | No | One short sentence: what this call changes and why (10-200 chars, no personal data). |
example_values |
array | No | |
footer |
string | No | Default: "". |
header |
string | No | Default: "". |
language_code |
string | No | Default: "es". |
template_edit
Section titled “template_edit”Edit a WhatsApp template · Changes data · can overwrite or remove · Reached with dakso_explore
Edits an existing template and resubmits it to Meta (about 1 edit per day and 10 per month per template; the current approved version keeps being sent until Meta approves the new one). Only APPROVED, REJECTED or PAUSED can be edited; FAILED never existed in Meta (delete and recreate). Name, category and language cannot change. Omitted fields are kept; pass “” to remove header or footer and [] to remove buttons. Pass realistic example_values if the new content has variables.
| Argument | Type | Required | Description |
|---|---|---|---|
element_name |
string | Yes | |
buttons |
array | No | |
content |
string | No | Default: "". |
descripcion |
string | No | One short sentence: what this call changes and why (10-200 chars, no personal data). |
example_values |
array | No | |
footer |
string | No | |
header |
string | No |
template_get
Section titled “template_get”Get a WhatsApp template · Read only · Reached with dakso_explore
Returns the full detail of one template by element_name: body, header, footer, buttons, example, status and rejection reason, plus computed _meta: variableCount (number of {{n}} variables), editable, sendable (only APPROVED) and statusNote explaining the status and what to do next.
| Argument | Type | Required | Description |
|---|---|---|---|
element_name |
string | Yes |
template_list
Section titled “template_list”List WhatsApp templates · Read only · Reached with dakso_explore
Lists the organization’s WhatsApp templates: name, category, language, status (APPROVED, PENDING, REJECTED, FAILED or PAUSED) and the rejection reason if any. Optional filters status and category. Use it first to see which templates exist and in what state before creating, editing or sending one.
| Argument | Type | Required | Description |
|---|---|---|---|
category |
string | No | Default: "". |
status |
string | No | Default: "". |
template_sync
Section titled “template_sync”Sync WhatsApp templates with Meta · Changes data · can overwrite or remove · Reached with dakso_explore
Syncs the local copy of the templates with Meta: refreshes status (for example PENDING to APPROVED), rejection reasons and components. Use it when the user asks about a template just created or edited, or when the data looks stale.
| Argument | Type | Required | Description |
|---|---|---|---|
descripcion |
string | No | One short sentence: what this call changes and why (10-200 chars, no personal data). |