> For the complete documentation index, see [llms.txt](https://helpdocumentation.gitbook.io/user/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/whatsapp-mini-apps/send-whatsapp-native-flow-and-store-responses-in-crm.md).

# Send WhatsApp Native Flow & Store Responses in CRM

#### 1. Create the First Bot Flow

1. Go to **Chatbot → Create Botflow**.
2. Enter a relevant title for the flow.
3. Click **+** and select **WhatsApp Chatbot**.
4. Select the trigger, channel, and required condition.
5. Add an **Ask a Question** block and select **WhatsApp Mini App**.
6. Enter the required **body text, header, footer, and button label**.
7. Select the required Mini App flow and landing screen.
8. Choose **Flow Response** to save the user's submitted data.
9. Save the block, save the workflow, and **Enable** it.

#### 2. Capture the Mini App Submission

1. Create another **Botflow** to handle the Mini App submission.
2. Select **WhatsApp Chatbot** and choose the **Mini App Submission** trigger.
3. Select the required channel and Mini App.
4. Select the relevant **submission history** and save the response.

#### 3. Save the Response in CRM

1. Add the **Save Variable Value** tool from **Native Tools**.
2. Select the required **Super Field** where you want to store the response.
3. Map the Mini App response to the selected field.
4. Add additional fields, such as **Email**, and map their respective values.
5. Save and **Enable** the workflow.

This allows Mini App responses submitted through WhatsApp to be captured and stored as structured data in the CRM.

{% embed url="<https://youtu.be/6dr5X0XDhtc>" %}


---

# 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/whatsapp-mini-apps/send-whatsapp-native-flow-and-store-responses-in-crm.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.