> For the complete documentation index, see [llms.txt](https://help.novacuraflow.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.novacuraflow.com/6.11/development/flow-studio/applications/workflow/user-step/text-input.md).

# Text input

A text input interaction item is used when the user is required to supply **textual information containing letters and/or digits**, either manually (using a keyboard) or with the aid of a barcode scanner.

Text inputs have the following properties:

* **Target Variable**\
   The name of the new variable in which to store the text entered.
* **Prompt**\
   The label to display over the text input field. For readability, it's often better to use a **Text Header** interaction item in user tasks with a single text input.
* **Default Text**\
   The text that will be entered as default when the user first enters the user task.
* **Allow Empty Input**\
   If set to **True**, the user is allowed to move forward in the workflow without entering anything into the text field.
* **Multiline**\
   If set to True, the text box will expand into a multi-line text editor allowing line breaks.
* **Force Uppercase**\
   If set to **True**, the contents of the text input will automatically be translated into UPPERCASE before being stored in the target variable.
* **Enable Text Correction**\
   If set to **True**, the text input will be enabled for spell checking, word suggestions and auto correction, on host systems that support such features. Use this only for human language text fields (e.g. work order error descriptions).
* **Trim Input Automatically**\
   If set to **True**, the contents of the text input will be trimmed (leading and trailing whitespace removed) before being stored in the target variable.
* **Use Password Mask**\
   If set to **True**, the text entered will show up as bullets like in a password input field.

![](https://543770944-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LtPTgZOYmpJka4jqs1v%2F-M-ofsU-lH2Rxn2G9fIM%2F-M-ofx0_S_rPRF6Fwg_W%2Fhelp_root_applications_workflow_user_items_text_input.png?alt=media\&token=e738e359-6d36-460b-94dc-b0040d1a4b4d)


---

# 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://help.novacuraflow.com/6.11/development/flow-studio/applications/workflow/user-step/text-input.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.