> For the complete documentation index, see [llms.txt](https://docs.zingy.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zingy.ai/app-editor/page-flow/toolbox-blocks/show-menu.md).

# Show Menu

{% hint style="info" %}
**Block Information**

Available in: Page Flow

Toolbox Category: Action - Menu

Block Type: [Regular](/app-editor/page-flow/block-anatomy.md#regular-block)
{% endhint %}

The **`Show Menu`** block is used to dynamically present a [Popup Menu](/app-editor/page-editor/built-in-elements/popup-menu.md) with options to the user of your app.

<div align="left"><figure><img src="https://3401585094-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmnBepgycwgisXr9ya1N4%2Fuploads%2FIXAio7E5374o3RVNqcL2%2Fimage.png?alt=media&amp;token=17e34613-20cb-4bb9-8ae5-db197e107d6d" alt=""><figcaption><p>Show Menu block</p></figcaption></figure></div>

The block consists of the following (from top to bottom):

* *Options List*: [Value Parameter](/app-editor/page-flow/block-anatomy.md#value-parameters) that accepts a [*list*](/app-editor/page-flow/references/value-types.md) value containing the options you want to present.
* *X Position*: [Value Parameter](/app-editor/page-flow/block-anatomy.md#value-parameters) that accepts a [*numeric*](/app-editor/page-flow/references/value-types.md) value for the X coordinate position where the menu will appear. The *xpos* property from the [Action/Event Info](/app-editor/page-flow/toolbox-blocks/action-event-info.md) block comes pre-attached as a default. You can attach any [*numeric*](/app-editor/page-flow/references/value-types.md) value here to change that.
* *Y Position*: [Value Parameter](/app-editor/page-flow/block-anatomy.md#value-parameters) that accepts a [*numeric*](/app-editor/page-flow/references/value-types.md) value for the Y coordinate position where the menu will appear. The y*pos* property from the [Action/Event Info](/app-editor/page-flow/toolbox-blocks/action-event-info.md) block comes pre-attached as a default. You can attach any [*numeric*](/app-editor/page-flow/references/value-types.md) value here to change that.
* *Selection Tasks*: a [Flow Parameter](/app-editor/page-flow/block-anatomy.md#flow-parameters) where you connect blocks that specify what you want done after a selection is made. Use the [Menu Text](/app-editor/page-flow/toolbox-blocks/menu-text.md) and/or the [Menu Index](/app-editor/page-flow/toolbox-blocks/menu-index.md) blocks to know what option the user selected.

***

## Usage Example

The example below shows the Show Menu block used to present a menu with two options when button is clicked. Since the *X Position* and *Y Position* [value parameters](/app-editor/page-flow/block-anatomy.md#value-parameters) are using their pre-attached values, the menu will be shown at the location where the click occurred.

<figure><img src="https://3401585094-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmnBepgycwgisXr9ya1N4%2Fuploads%2FbPb44fa0D05uJkwSbE47%2Fimage.png?alt=media&amp;token=e2eece74-b7b6-4da7-ae4f-d29f00996403" alt=""><figcaption><p>Example of Show Menu Form</p></figcaption></figure>


---

# 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://docs.zingy.ai/app-editor/page-flow/toolbox-blocks/show-menu.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.