> For the complete documentation index, see [llms.txt](https://docs.zbrain.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zbrain.ai/zbrain-documentation/zbrain-builder/flows/flow-components/inputs.md).

# Inputs

Enable data capture through inputs to trigger and guide workflows within ZBrain.

ZBrain supports a wide array of input options to enhance data handling and processing capabilities.

### **How to Use Different Input Components in ZBrain Flow?** <a href="#how-to-use-different-input-components-in-zbrain-flow" id="how-to-use-different-input-components-in-zbrain-flow"></a>

To use different input components, choose from a range of input options.

* Json: Add JSON.
* Long text: Add Long Text.
* Number: Add a Number.
* Read File: Read a file from the file system.
* Text: Add Text.
* Text List: Add Text List.

#### **Additional Settings for Text Component** <a href="#additional-settings-for-text-component" id="additional-settings-for-text-component"></a>

**Text Field:** You can enter or dynamically capture text, such as webhook responses or user inputs, to be used within your workflow.

#### **Additional Settings for Text List Component** <a href="#additional-settings-for-text-list-component" id="additional-settings-for-text-list-component"></a>

**Add Item**: Enables the addition of individual text entries to the list, facilitating the compilation of multiple discrete data points.

#### **Additional Settings for Long Text List Component**  <a href="#additional-settings-for-long-text-list-component" id="additional-settings-for-long-text-list-component"></a>

**Text**: Enables entering long text input.

#### **Additional Settings for Number Component**  <a href="#additional-settings-for-number-component" id="additional-settings-for-number-component"></a>

**Number:** Enables entering number input.

#### **Additional Settings for JSON Input Component** <a href="#additional-settings-for-json-input-component" id="additional-settings-for-json-input-component"></a>

This component allows you to input structured data in JSON format, enabling complex data manipulation and parameterization within your workflow.

* **Json Field**: Enter or paste JSON data directly into this field to be used in the workflow.

#### **Additional Settings for Reading File Input** <a href="#additional-settings-for-reading-file-input" id="additional-settings-for-reading-file-input"></a>

This component allows you to input and read data from a file directly within your workflow.

* **File**: Upload the file that you wish to read. This field accepts various file formats depending on your workflow requirements.
* **Output Format**: Select the desired format for the output data after the file is read, such as text or Base64 format.


---

# 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.zbrain.ai/zbrain-documentation/zbrain-builder/flows/flow-components/inputs.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.
