> For the complete documentation index, see [llms.txt](https://docs.avonnicomponents.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avonnicomponents.com/flow/actions/ui-and-navigation/new-button-menu-item-collection.md).

# New Button Menu Item Collection

## Overview

This action lets you create a dropdown menu with multiple actions linked to the [Avonni Button Menu](/flow/flow-components/button-menu.md) in your flow. This helps you provide a clean and organized way for users to access different options.

***

## How it Helps

Imagine you have a button labeled "Actions" on a record page in your flow. Instead of cluttering the page with separate buttons for "Edit," "Delete," and other actions, you can use this action to create a neat dropdown menu that contains all these options.

***

## When to Use It

This action is great for:

* **Grouping related actions under a single button.**
* **Providing a compact way to access multiple options.**
* **Improving the organization and usability of your flows.**
* **Creating context-specific menus for different parts of your flow.**

***

## Example

To create an "Account Actions" menu:

1. **Configure the Action:** Provide a label for the action collection (e.g., "Account Actions Menu").
2. **Add Menu Items:** For each item, specify the label (e.g., "Edit"), an optional icon name (e.g., "utility:edit"), and a unique name (e.g., "editAccount").
3. **Connect to Button:** Connect this action collection to a button component in your flow.

***

## Key Considerations

* **Action Triggers:** You'll need to add logic to your flow to define what happens when each menu item is clicked.
* **Menu Placement:** Consider where you'll place the button menu within your flow's layout.
* **Accessibility:** Use clear labels and icons that are easy for all users to understand


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.avonnicomponents.com/flow/actions/ui-and-navigation/new-button-menu-item-collection.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.