> 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/tutorials/components/button-groups/identifying-clicked-buttons.md).

# Identifying Clicked Buttons

## Overview

Knowing which button has been pressed in Salesforce Flows is crucial to ensure the right action is taken. This article will provide a comprehensive guide on using the [Avonni Button Group](/flow/flow-components/button-group.md) component, configuring the Row setting, and leveraging the "**`ClickedButtonName`**" attribute to determine the pressed button in a flow.

## Detailed Steps

1. Drag and drop the [Avonni Button Group](/flow/flow-components/button-group.md) component into your screen flow. This component allows you to create groups of buttons for seamless navigation and interaction.

<figure><img src="/files/SiYHKErrUO7qZAaxCWDa" alt=""><figcaption></figcaption></figure>

2. Leverage the "**`ClickedButtonName`**" Attribute to Identify the Pressed Button. Once you have set up the individual buttons within the Avonni Button Group component, the "**`ClickedButtonName`**" attribute becomes available.

<figure><img src="/files/G9E8SmhXXTCKXrAHcwKS" alt=""><figcaption></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 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/tutorials/components/button-groups/identifying-clicked-buttons.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.