> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mileapp.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Text

The **Text** input type enables field workers to enter free-form text or alphanumeric values as part of a task.

## What is the Text Input?

Text captures a single-line string for any free-form information that does not require a specific format. It is the most flexible input type and is commonly used when no structured validation (such as date, number, or phone format) is needed.

**Use Cases:**

* **Customer name**: Capture the recipient's name on a delivery task
* **Reference code**: Record an order number, SKU, or any short identifier
* **Free-form notes**: Capture brief observations or remarks from the field

## Text Properties

<div align="center">
  <img src="https://mintcdn.com/mileapp-c1584fbc/OPAMjeo91qoaLUGM/images/flow/component-input-text-settings.png?fit=max&auto=format&n=OPAMjeo91qoaLUGM&q=85&s=314403cc80bd251e16f2840230389f7c" alt="image" width="600" data-path="images/flow/component-input-text-settings.png" />

  <p><i>Component text input settings</i></p>
</div>

1. **Default Value:** This setting allows you to set a pre-filled value for this component. If a value is specified, any task created with this flow will use it as the initial value.
2. **Toggle Required:** This option makes the text input mandatory. If not filled, users cannot proceed to other activities.
3. **Toggle Visible:** This setting affects the visibility of the component during task creation on the web and mobile, as well as task viewing on the mobile app. If the component is not visible, it will not be shown in the UI. However, both visible and hidden component data will be exported, regardless of their visibility status.
4. **Toggle Use Data Source:** This option allows the component to retrieve its value from a data source instead of being filled in manually.
5. **Show As:** This configuration, controls how the input value is displayed within the task. The value of this component will appear on the task table in the **Task** menu as the **Title**, **Content**, or **Label**, depending on the option selected.
6. **Route As:** This configuration, links the component to a form field in the **Routing/Visit** menu. The form field in Routing/Visit will be filled in automatically based on the option selected in the dropdown. For Text Input, this component can be mapped to **Visit Name**, **Address**, **Tag**, or **Visit Group**.

## How to Configure Text

### Step 1: Add the Component

In the Flow Builder, click **Add Component** on the target page. Set **Component Type** to **Input** and **Type Of Input** to **Text**.

### Step 2: Set Basic Properties

Enter the component **Title** (e.g., "Customer Name"). Toggle **Required** and **Visible** as needed. Optionally enter a **Default Value**.

### Step 3: Configure Show As (optional)

In the **Configuration** section, choose how the value should appear on the task list in the Task menu:

* **Title** — the text appears as the task's main title
* **Content** — the text appears as the secondary description line
* **Label** — the text appears as a smaller tag/label on the task card

### Step 4: Configure Route As (optional)

Still in the **Configuration** section, select a Routing/Visit field to map this value into. The Routing/Visit form will be auto-filled with this component's value. Valid options for Text Input: **Visit Name**, **Address**, **Tag**, or **Visit Group**.

### Step 5: Enable Use Data Source (optional)

Toggle **Use Data Source** on to populate the field's value from a configured data source instead of free-form entry.

## How Text Works in Tasks

<div align="center">
  <img src="https://mintcdn.com/mileapp-c1584fbc/OPAMjeo91qoaLUGM/images/flow/component-input-text-mobile.png?fit=max&auto=format&n=OPAMjeo91qoaLUGM&q=85&s=e18a4edf32d682e96d67a5fa8ddbdd94" alt="image" width="300" data-path="images/flow/component-input-text-mobile.png" />

  <p><i>Text input on mobile preview</i></p>
</div>

When a field worker opens a task on the mobile app:

1. The Text field shows a **single-line text input** with placeholder or default text
2. The worker can type freely, or the field may already be populated:
   * **From task creation**: If the task was created with a value (via web form, Excel import, API, or Data Source), the field is pre-filled
   * **From Default Value**: The flow-level default appears if no value was provided at creation
3. The worker can edit the text before completing the page

## Related

* [Number Component](/pages/flow/flow-builder/component-input-type/number) — Numeric-only input
* [Address Component](/pages/flow/flow-builder/component-input-type/address) — Multi-line address text
* [Input Component Overview](/pages/flow/flow-builder/component-input-type/component-input)