> 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/how-to-store-hidden-values-with-buttons-and-use-them-for-bots-button-payloads.md).

# How To Store Hidden Values With Buttons And Use Them For Bots - Button Payloads ?

Taking an example of task management system to understand the use of button payloads:

1. Create a Google Sheet to track tasks. Include columns for Task ID, Employee Contact Number, Task Description, and Status which can be taken from a bot.
2. Assign custom row numbers as Task IDs for each new task.
3. Send a button template message to the employee's contact number. The message should include the Task Description and a "Done" button for them to report task completion.
4. When an employee clicks the "Done" button, trigger a new flow in your application. This flow should capture the payload, which contains the Task ID.
5. Use Google Sheets to search for the Task ID in your sheet and update the Task Status to "Done".

Implementing these steps will allow for efficient task management and status tracking using Google Sheets.

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


---

# 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/how-to-store-hidden-values-with-buttons-and-use-them-for-bots-button-payloads.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.