WhatsApp

Prerequisites

• A Meta developer app (opens in a new tab). Check out this article (opens in a new tab) to learn more about the setup.
• A WhatsApp Business Account to be your bot's interface on WhatsApp
• A Botpress Cloud account (opens in a new tab) and a Botpress Bot (opens in a new tab)

Setting up the WhatsApp integration in Botpress

1. Go to the Integration Hub (opens in a new tab) in Botpress Cloud (if you don't have the integration installed yet).
2. Find and open the WhatsApp integration then click on the "Install to Bot" button, now go back to your bot.

The WhatsApp integration will have the following settings:

1. Verify Token

The Verify Token is used by Meta to verify that you are the real owner of the provided webhook. You can generate any random alphanumeric string for this configuration. Paste it in your Verify Token channel configuration.

2. Phone Number ID

1. In your Meta App's left sidebar, expand the WhatsApp menu and select Getting Started
2. In the Send and receive messages section, beside the label Phone Number ID click Copy then paste it in the Phone Number ID field in Botpress

3. Access Token

The Phone Number ID and Access Token are used to send and receive messages to/from the WhatsApp API.

1. In your Meta App's left sidebar, expand the WhatsApp menu and select Getting Started
2. In the Temporary access token section, click Copy and then paste it in the Access Token field in Botpress

4. (Optional): Permanent Access Token

Permanent Access Token can be used to send and receive messages to/from the WhatsApp API without the need to refresh the token every 24 hours.

1. Navigate to Business Settings (opens in a new tab).
2. Choose the business account associated with your app.
3. Click on Add under System Users.
4. Enter a name for the system user, assign the Admin role, and click Create System User.
5. Click on Create Asset and select Apps from the asset type Tab.
6. Select your app and toggle Manage App (full control).
7. Click Generate New Token and select whatsapp_business_messaging and whatsapp_business_management permission.
8. Copy and save your token.

Finalizing Channel Configuration

The next step is to Enable the channel from the top of the screen and then copy the webhook URL from the button below the webhook URL.

In the last step, click Save.

Now we can go back to Step (3) & Step (4) in this article (opens in a new tab).

Webhook Fields

We need to subscribe to the webhook fields below

• Messages: For the chat to work properly, you need to subscribe to the messages webhook field.

Content Types Mapping

From Botpress to WhatsApp

• Text is mapped to Text Object (opens in a new tab)
• Text with Markdown is mapped to Text Object (opens in a new tab)
• Image is mapped to Media Image Object (opens in a new tab)
• Audio is mapped to Media Audio Object (opens in a new tab)
• Video is mapped to Media Video Object (opens in a new tab)
• File is mapped to Media File Object (opens in a new tab)
• Location is mapped to Location Object (opens in a new tab)

Special behaviors to consider

Choices (buttons), dropdowns, cards, and carousels are all mapped to Interactive List Objects. (opens in a new tab)

This comes with a few restrictions and behaviors specific to WhatsApp:

Choices (buttons) and Dropdowns

• When there are 3 or fewer choices as buttons or in a dropdown, they will be rendered as buttons.
• When there are more than 3 choices as buttons or in a dropdown, they will be rendered as a dropdown.
• If there are more than 10 choices in a dropdown, the multiple dropdown messages will be sent with up to 10 choices in each messsage.
  • For example, if your bot has a dropdown with 10 choices, the user will receive two messages: the first message will have a dropdown with 10 choices, and the second messge will have a dropdown with two choices.
• Each dropdown requires a label but the Studio currently doesn’t support specifying one, so the label “Choose…” is used for all dropdowns by default.
• Button labels are limited to 20 characters, and dropdown labels are limited to 24 characters.
  • Labels exceeding these limits are automatically truncated. For example, the label "This button label is very long" would become "This button label i…" on a button and "This button label is ve…" on a dropdown.

Carousels and Cards

• Each card in a carousel will be sent individually.
• There is a limit of 3 action buttons on each card.
• Whatsapp requires cards to only use "reply" buttons. If the card has a URL action or no action at all, it won't be able to be displayed and will be down-rendered using multiple text/image messages instead.

Files

• When files are sent over Whatsapp, the Studio doesn't store the original filename (for security reasons) but only the file extension, so the file will be sent with a generic filename ("file") followed by the extension of the file. For example, if you send a PNG file, it will be sent as "file.png".

From WhatsApp to Botpress

Text

Text messages are directly mapped to Botpress text messages, and readable through event.preview.

Location

Use a “Wait for User Input” card on your bot, check that event.type equals "location", and then read event.payload which will contain the following properties:

• latitude
• longitude
• address (not always provided)
• title (not always provided)

Other message types

• Buttons and interactive replies from a list or button are mapped to a plain text response from the user, so you can use event.preview to get the value.
• Botpress does not currently support other Whatsapp message types.

Tips

• To get the phone number of the user you can read the following variable:

  {{ event.tags.conversation['whatsapp:userPhone'] }}.

  This number also contains the country code and has no spaces, dashes or signs.

• To get the Whatsapp Phone Number ID of your bot that the user is interacting with (useful when pointing multiple Phone Number IDs to the same bot):

  {{ event.tags.conversation['whatsapp:phoneNumberId'] }}

Receiving a Location

When WhatsApp shares a location it is mapped to the Botpress location object and the location information is found in the event.payload object. In the conversation, you can use a text message card asking the user to send their location using the built-in "Send Your Current Location" feature of Whatsapp followed by a "Wait for Message" card to await the user's response with their location.

Once you get the response, you will be able to access the properties of the location using the variables below:

• Location Title: {{event.payload.title}}
• Location Address: {{event.payload.address}}
• Location Longitude: {{event.payload.longitude}}
• Location Latitude: {{event.payload.latitude}}

Example:

• [Text card]: Where are you? Please use Whatsapp's "Send Location" feature.
• [Wait for Message card]
• [Text card]: Thank you! You are located at {{event.payload.title}}, {{event.payload.address}} with longitude {{event.payload.longitude}} and latitude {{event.payload.latitude}}.

Starting a Conversation Proactively

As required by WhatsApp, a conversation with a user can be proactively initiated only by using Message Templates (opens in a new tab), which need to be created in your WhatsApp Manager (opens in a new tab) dashboard first and then reviewed and approved by WhatsApp in order to use them.

Once you have a message template approved by WhatsApp, it's very easy to have your bot start a conversation with a user by just using the Whatsapp "Start Conversation" card:

Loading...

Then you just need to pass the following fields to proactively start a Whatsapp conversation with a user:

1. User Phone: The phone number of the user, including the country code (e.g. +1 123 456 7890).
2. Template Name: The name of your WhatsApp message template to use for the first message of the conversation. The template should be already approved by WhatsApp in order to use it.
3. Template Language (optional): The language code of your WhatsApp message template (see below for more details).
4. Template Variables JSON (optional): The values of the variables for your WhatsApp message template, specified as a JSON array representing the list of values (see below for more details).
5. Sender Phone Number ID (optional): The Whatsapp Phone Number ID you want to use as sender of the message if you have multiple phone numbers available in your Meta Developers dashboard. If you don't specify this field, the Default Phone Number ID specified in the Whatsapp configuration of your bot in your Botpress Cloud dashboard will be used by default.

Loading...

Once the conversation is created, if the user replies back it will be processed by your bot as a normal incoming message, so nothing else needs to be done.

Template Language

If the language you selected for your template in the Whatsapp Manager dashboard has a country qualifier, then the value for "Template Language" needs to be specified in the language_COUNTRY format where language is the 2-letter lowercase ISO code for the language (opens in a new tab), and COUNTRY is the 2-letter uppercase ISO code for the country (opens in a new tab). On the other hand, if the language in Whatsapp Manager doesn't specify a country then you can enter just the 2-letter lowercase ISO code for the language.

For example:

• If you selected the "English (US)" option for the language of your Message Template in Whatsapp Manager, then the value you need to enter for "Template Language" in Botpress is en_US.
• If you selected the "English (UK)" option, then the value you need to enter is en_GB.
• If you selected the "French" option, which doesn't have a country qualifier, then the value you need to enter is just fr.

Template Variables

Template variables need to be passed as a JSON array of string or numeric values representing the list of variable values, as Whatsapp only allows referring to them by their position in your message template (e.g. {{1}} for the first variable, {{2}} for the second variable, and so on).

For example, if your Message Template expects a first variable (referred to as {{1}} in the template) with the person's first name and then a second variable ({{2}} in the template) with an account number, then you would pass the following JSON array as the value for the "Template Variables" field:

["John", "12345"]

Accessing the Botpress Conversation ID

If you need to access the ID of the conversation created in Botpress Cloud by this action, you can choose to store the output value of this action in a variable. The output value of this action will be an object with the following structure:

{
  conversationId: 'ffa09762-6c37-4ebd-a82f-307048929c97'
}

So for example, if you choose to store the output value of this action in a variable named bpWhatsappAction, you can use {{ workflow.bpWhatsappAction.conversationId }} in input fields of the Studio (where supported) to insert the conversation ID, or use workflow.bpWhatsappAction.conversationId to access it in code.

Creating the conversation using the Botpress Client

Note: This only works for bots created from code only.

If you're building a bot as code (instead of using Botpress Studio), you can use the Botpress Client instance provided to your bot's handlers to call this action programmatically as shown in the following example:

const result = await client.callAction({
  type: 'whatsapp:startConversation',
  input: {
    userPhone: '+1 123 456 7890', // The full phone number of the Whatsapp user you want to initiate the conversation with.
    templateName: 'test_message', // This is the name (identifier) of your WhatsApp message template.
    templateLanguage: 'en_US', // Optional (defaults to `en_US`)
    templateVariablesJson: JSON.stringify(['John', '12345']), // Optional (only needed if your message template uses variables)
  },
})
 
console.log('Botpress conversation ID: ' + result.conversationId)