> For the complete documentation index, see [llms.txt](https://docs.helmut.de/helmut4-releases/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.helmut.de/helmut4-releases/v4.8.0/helmut4-components/streamdesigner/nodes/actions/helmut-6/helmut-input-dialog-action.md).

# Helmut Input Dialog Action

The "Helmut Input Dialog Action" node allows you to create an interactive input dialog within Helmut. Users can respond to a question posed in the dialog by typing their answer directly into the input field. Alternatively, users have the option to decline the input action.

This node includes the ability to set a default placeholder text within the input field. Additionally, it features a timeout mechanism; if the specified timeout period elapses without a response, the node will fail.

Based on the user's interaction (either providing an answer or denying the input), the node will generate a response accessible via the wildcard {stream.last\_result} or {node.result.?}. This response captures the user's input or the outcome of the action, facilitating further processing within the Helmut environment.

<figure><img src="/files/kICezSfEkV7KLit7Bz2z" alt="" width="354"><figcaption><p>Helmut Input Dialog Action</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 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.helmut.de/helmut4-releases/v4.8.0/helmut4-components/streamdesigner/nodes/actions/helmut-6/helmut-input-dialog-action.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.