# Send Template

The *Send Template* action node enables you to send pre-approved [WhatsApp message templates](https://guides.clickatell.com/flow/channel-capabilities/use-whatsapp-with-chat-flow/send-whatsapp-message-templates) to your customers from within Chat Flow.

You can use this node in any of your workflows, but it is typically used in [Dynamic API flows](https://guides.clickatell.com/flow/workflow-management/create-new-flow/dynamic-api-workflows) to initiate WhatsApp conversations with customers.&#x20;

{% hint style="info" %}
When configuring the node, you can only select from the **approved** WhatsApp templates on your account. To find out how to apply for and manage your WhatsApp templates, see [here](https://app.gitbook.com/s/H9mbp0ZlSZKdmkQMXA0U/channel-capabilities/whatsapp-message-templates/add-message-templates).

Note that this node is not supported on the [Previewer](https://guides.clickatell.com/flow/workflow-management/using-the-previewer).
{% endhint %}

<figure><img src="https://content.gitbook.com/content/joAgInTNsBfDdfx1I23z/blobs/a7npvhhZhf9nNdrj9TKg/Send%20Template%20(GIF).gif" alt=""><figcaption><p>Configuring the Send Template action node</p></figcaption></figure>

<figure><img src="https://content.gitbook.com/content/joAgInTNsBfDdfx1I23z/blobs/GHREHUiv5ecq877KdOKX/image.png" alt=""><figcaption><p>Setup of a Send Template node.</p></figcaption></figure>

You can use the *Send Template* node to send any type of template. Depending on the type of template you select, the fields to configure adapt accordingly.

#### Text templates

Below is an example of how to configure the node if a text template is selected.

<figure><img src="https://content.gitbook.com/content/joAgInTNsBfDdfx1I23z/blobs/lXVxSeOwHEnX6GCAd5l6/image.png" alt="" width="563"><figcaption><p>Example of a text template.</p></figcaption></figure>

#### Templates with interactive buttons

Below is an example of configuring the node if a template with interactive buttons is selected.

The flow-builder can configure the next flow/step to execute when the customer selects each button. Additional data that needs to be sent for postback data can be added if required.

{% hint style="info" %}
Maximum of 10 buttons allowed.
{% endhint %}

<figure><img src="https://content.gitbook.com/content/joAgInTNsBfDdfx1I23z/blobs/Ykuh48MwL2lMYkg8dEGg/image.png" alt="" width="272"><figcaption><p>Example of a template with interactive buttons.</p></figcaption></figure>

If the template contains a dynamic URL, the flow-builder must capture the variable's value in the field as shown below.

<figure><img src="https://content.gitbook.com/content/joAgInTNsBfDdfx1I23z/blobs/cG7sTllbi0IIWVVaMLXe/image.png" alt="" width="272"><figcaption></figcaption></figure>

#### Templates with media headers

Below is an example of configuring the node if a media template is selected. You can add images, videos, and documents in the header of your template.&#x20;

The flow-builder must specify the media file to add to this template.&#x20;

{% hint style="info" %}
The preview will not show the media file, it will only be added upon sending.&#x20;
{% endhint %}

<figure><img src="https://content.gitbook.com/content/joAgInTNsBfDdfx1I23z/blobs/EOajjtXf55abJP8zSr9Q/image.png" alt="" width="563"><figcaption></figcaption></figure>

#### Templates with location headers

Below is an example of configuring the node if a location template is selected.&#x20;

{% hint style="info" %}
Only supported on Meta's Cloud environment.
{% endhint %}

<figure><img src="https://content.gitbook.com/content/joAgInTNsBfDdfx1I23z/blobs/EcDt8lmGqyVQREFyp5G4/image.png" alt="" width="563"><figcaption></figcaption></figure>
