> For the complete documentation index, see [llms.txt](https://design.mirakl.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://design.mirakl.com/design/components/actions.md). # Actions this are all the available actionable components


Action menu	An action menu shows a list of items presenting the user with actions that can have an immediate effect, or a redirection to another section of the Mirakl platform.	ActionMenu Card.png	Action menu
Buttons	A central component to guide users through their experience in the platform. They trigger actions and let users know what their options are.	Buttons Card.png	Buttons
Button group	Button group is used to gather multiple actions.	ButtonGroup Card.png	Button group
File download	This component allows users to download a file from Mirakl.	File Download Card.png	File download
Save bar	A Save Bar is an action bar that sticks to the bottom of the viewport as you scroll. It contains actions related to a page and allow users to scroll without loosing visibility on the different actions	Savebar Card.png	Save bar
Tasklist	Tasklists are designed to display multiple tasks users will have to complete to finalize a complex process (e.g. store or profile creation).	Tasklist Card.png	Tasklist
Toolbar	Toolbar allows users to filter and manage the display of the content a page	Toolbar Card.png	Contextual Toolbar

--- # 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://design.mirakl.com/design/components/actions.md?ask=&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.