> For the complete documentation index, see [llms.txt](https://docs.appfarm.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appfarm.io/library/action-nodes/open-confirm-dialog.md).

# Open confirm dialog

Open Confirm Dialog is a built-in UI for opening a modal dialog for the end-user.

Adding an Open Confirm Dialog to your action allows you to define the Title, Body Text and two buttons - a Confirm button and a Cancel button (you need to set these labels yourself).

When the execution of an action meets an Open Confirm Dialog, the execution will pause until either Cancel or Confirm button is clicked. When Confirm button is clicked (and only then), the action nodes inside the Open Confirm Dialog will be executed.

Please note that you may check *Enable Markdown* for a formatted text in the Title and Body Text with markdown formatting and preserving line breaks. See our [markdown section](/reference/platform-concepts/markdown.md) for more help.

{% hint style="info" %}
An example setup of Open Confirm Dialog is showcased in our [Showroom](https://showroom.appfarm.app/action-nodes/open-confirm-dialog)! You may view a demo, as well as access the setup in Appfarm Create. If you do not have access, you may register [here](https://showroom.appfarm.app/sign-up).
{% endhint %}


---

# 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.appfarm.io/library/action-nodes/open-confirm-dialog.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.