> 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/development/flow-studio/applications/workflow/user-step/time-input.md). # Time input A time input interaction item is used when the operator is required to enter a time input. Time inputs have the following properties: * **Target Variable**\ The name of the new variable in which to store the time entered. Time are stored in the HH:MM format. * **Prompt**\ The label to display over the time input field. * **Default Value**\ The default value must be in HH:MM format. If no default value is supplied, the present time will automatically be displayed by default. * **Condition To Hide** Add the condition that must be met for the control to be hidden. If left empty, the control will be visible in the user step. Note that when controls are hidden, empty variables will be created, unless default values or pre-defined data exist. * **Allow Empty Input**\ If set to **True**, the operator is allowed to move forward in the workflow without entering anything into the time field. * **Merge behavior** The control behavior at reloading, see [User step reloading](/development/flow-studio/applications/workflow/user-step.md#user-step-reloading). --- # 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/development/flow-studio/applications/workflow/user-step/time-input.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.