> For the complete documentation index, see [llms.txt](https://helpdocumentation.gitbook.io/user-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdocumentation.gitbook.io/user-documentation/bot-builder/whatsapp-chatbot/create-whatsapp-native-flows-from-wa-manager-and-send-them-to-users.md).

# Create WhatsApp Native Flows From WA Manager And Send Them To Users

#### **1. Setting up Flow in WhatsApp Manager**

* Access the **WhatsApp** official API, click on the **three dots** > select **"WA Manager."**
* On the left menu, choose **"Message Templates"** > click **"Create a Template."**
* For template type, select **"Marketing"** > **"Form"**.
* Fill in the **template name, language,** and **body.**
* Use the **drag-and-drop UI** to design your flow with screens, questions, and buttons.
* **Save** the flow and **submit** it for approval.

#### **2. Bot Flow Integration**

* Post approval, create a **bot flow** in the **Bot Builder.**
* **Create four custom fields** in the CRM for the flow responses and answers.
* In the Bot Builder, **create a new bot flow**, set a **trigger keyword**, and use the **"Interactive Flow"** option to ask a user question.
* **Select** the published flow from WA Manager and **paste** the flow ID and token into the bot flow setup.
* Configure the **screen ID, response save location,** and **expected answer type.**
* **Save, enable,** and **test** the bot flow.

#### **3. Processing and Exporting Data**

* Upon user submission, flow data is saved in the custom fields.
* Utilize the **"Extract JSON from String"** automation to parse the flow response data into separate custom fields.
* **Export contacts** from the CRM for a structured data set of user responses.

{% embed url="<https://youtu.be/f-hmTFUcKEA>" %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://helpdocumentation.gitbook.io/user-documentation/bot-builder/whatsapp-chatbot/create-whatsapp-native-flows-from-wa-manager-and-send-them-to-users.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.