Skip to main content
The Address input type enables field workers to enter a free-text address as part of a task.

What is the Address Input?

Address captures a multi-line text string representing a physical location. Unlike the Coordinate component, Address has no GPS or geofencing features — it is a passive text field that stores whatever the worker types. Use Cases:
  • Delivery address display: Show the customer’s address on the task card and mobile form
  • Import source for geocoding: Provide the address during task import and let the system convert it to coordinates automatically
  • Manual address entry: Allow workers to record a location in plain text when GPS is not required

Address Properties

Address component configuration
Address type of input settings:
  1. Title — Component label shown to field workers (e.g., “Customer Address”, “Address User”)
  2. Type of Input — Set to Address
  3. Default Value — Pre-filled address text. A task created with this flow will use this value unless overridden. Supports multiple lines.
  4. Required — If on, the field must be filled before page completion
  5. Visible — Controls display on Create Task (web and mobile) and View Task (mobile).
  6. Reverse Geocode: If on, automatically populates this Address field from a linked Coordinate component. Reveals:
    • Generate Address From: Select the Coordinate (Geolocation type) component to use as the reverse geocoding source
The Reverse Geocode toggle is only visible to MileApp internal accounts. It is not available to customer organizations in the builder UI while mile-v3-mobile does not yet fill a paired Address on the mobile app.
Address has no Geolock settings. Geocode (address → coordinate) is configured on the Coordinate component that references this field. Address does have its own Reverse Geocode setting (coordinate → address), described below.

How to Configure Address

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 Address.

Step 2: Set Basic Properties

Enter the component Title (e.g., “Customer Address”). Toggle Required and Visible as needed. Optionally enter a Default Value — this is a multi-line textarea.

Step 3: Configure Show As (optional)

In the Configuration section:
  • Set Show As to content — the address text appears as the main description line on the task card in the task list.
  • Set Show As to title — the address text appears as the task’s title (use only when there is no dedicated name field).
  • Set Show As to label — the address appears as a smaller label on the task card.
This drives coordinate population from this Address, the opposite direction of the setting below. To enable it:
  1. Add a Coordinate component to the same flow.
  2. Open the Coordinate component’s settings.
  3. Toggle Geocode on and select this Address component in Generate Coordinate From.
Once linked, the Coordinate component drives the relationship: it is auto-populated during task import when address text is provided. See Coordinate Component for the full forward-geocoding behavior.

Step 5: Enable Reverse Geocode (optional)

Available to MileApp internal accounts only. Customer organizations do not see this toggle in the Flow Builder.
Toggle Reverse Geocode on to automatically populate this Address field from a Coordinate component in the flow:
  1. Add a Coordinate component to the same page.
  2. Open this Address component’s settings.
  3. Toggle Reverse Geocode on.
  4. In Generate Address From, select the Coordinate component that should supply the location.
  5. Save the flow.
A flow cannot pair the same two components in both directions at once. If the selected Coordinate component already has Geocode on and points back at this Address, saving the flow fails with a circular-pairing error. Remove one of the two settings before saving.

Reverse Geocode: Coordinate → Address

When Reverse Geocode is enabled, the Coordinate field drives the Address field:
The Generate Address From dropdown only shows Input / Geolocation components. If no options appear, add a Coordinate-type input component to the flow first.

Validation Rules

  • Generate Address From must reference a valid Coordinate (Geolocation type) component in the same page when Reverse Geocode is on
  • A flow is rejected on save if the paired Coordinate also points its own Geocode setting back at this Address (circular pairing)
  • Reverse Geocode has no effect for organizations without the internal-account gate; the setting cannot be turned on through the Flow Builder UI, though the underlying flow JSON keys are not blocked at the API level

How Address Works in Tasks

When a field worker opens a task on the mobile app:
  1. The Address field shows a multi-line text area with placeholder text
  2. The worker can type freely, or the field may already be populated:
    • From task creation: If the task was created with an address value (e.g., from Data Source or manual entry), the field is pre-filled
  3. The worker can edit the text before completing the page