> For the complete documentation index, see [llms.txt](https://docs.getmesa.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.getmesa.com/workflow-builder/fields.md).

# Fields

### Required vs. Optional Fields

When referencing a field in your workflow's steps, you'll want to identify whether it's a required or optional field. All required fields are marked with a red asterisk.

To ensure the workflow is completed successfully, please make sure to fill in any required fields you see in a step. Your attention to these details will help you move forward smoothly!

## Text

Text fields are a key feature in MESA, making configuration a breeze. The field name sets up the configuration, the field label gives clear details on how to use it, and the placeholder offers a handy example of the expected input. Here’s a great example of a text field in action:

<figure><img src="/files/H3CCgYes6fHgT6UKohxF" alt="Screenshot of an example text field in a MESA step showing the field name, label, and placeholder, spotlight the text field input."><figcaption></figcaption></figure>

## Drop-down Menus

Drop-down menu fields are fantastic for selecting from a list of predefined options. You'll recognize them by the arrow pointing down at the end of the field. There are a few different kinds of drop-down menus within steps:

**Typeahead**

The drop-down menu shows suggestions as you type, letting you quickly choose from a list of matching options.

**Select List**

The drop-down menu with predefined options will appear for you to select from. Here is an example of where to select:

<figure><img src="/files/ShQ3GFCkFAoSb6qkQof2" alt="Screenshot of a Select List drop-down menu field in a MESA step with its predefined options open, spotlight the drop-down menu."><figcaption></figcaption></figure>

**Custom Value**

In certain instances, you will want to use a [variable](/workflow-builder/fields/variables.md) from a previous step or a hard-coded value that did not appear in the drop-down list. Simply select "Enter custom product ID" to access the variable selector or enter your own custom value:

<figure><img src="/files/mX1Xq3hTvOCR1SuTUbKh" alt="Screenshot of a Custom Value drop-down field in a MESA step, spotlight the Enter custom product ID option."><figcaption></figcaption></figure>

**Custom Option with a Text Input**

<figure><img src="/files/1p3uWTi7Q1XjORlOUI02" alt="Screenshot of a Custom Value drop-down field in a MESA step with a custom text input open, spotlight the custom text input."><figcaption></figcaption></figure>

**Custom Option with a Variable**

<figure><img src="/files/lFxr9SPlElZsCIxDugwB" alt="Screenshot of a Custom Value drop-down field in a MESA step using the variable selector, spotlight the selected variable."><figcaption></figcaption></figure>

**Multi-select List**

The drop-down menu allows you to pick more than one option from a list

**Boolean**

The drop-down menu lets you select between two options, such as "Yes" or "No" or "True" or "False."

## Files

File fields work like text fields but are designed to accept a URL. This URL needs to be publicly accessible and should not require authentication for MESA to access it. Currently, Google Drive and Dropbox URLs are not supported, and direct file uploads aren’t available in MESA. Instead, we suggest uploading your files to a service like [Shopify Files](https://help.shopify.com/en/manual/shopify-admin/productivity-tools/file-uploads) and then using the URL provided.

Here is an example file field:

<figure><img src="/files/0kXQLvhqlYSoiBlwdLCM" alt="Screenshot of an example file field in a MESA step that accepts a publicly accessible URL, spotlight the file URL input."><figcaption></figcaption></figure>

## Mapping

Mapping fields are straightforward and powerful, consisting of two parts: 'Key' and 'Value.' They’re often used to create key/value pairs from static, manually entered data. Sometimes, you’ll enter the key of a property manually while pulling the value from another service.

They’re also great for passing extra information to or from an API. When needed, mapping fields allow you to send key/value pairs, which are then converted into an object by the API.

Here is an example of the mapping fields:

<figure><img src="/files/IG48ohqgMou4V8lckTUj" alt="Screenshot of example mapping fields in a MESA step showing the Key and Value pairs, spotlight the Key and Value inputs."><figcaption></figcaption></figure>

### Additional Fields

{% hint style="info" %}
Additional fields enhance the functionality of your workflows beyond the standard capabilities MESA provides.
{% endhint %}

Sometimes, you may want to capture more specific information or add preferences. Selecting the **More Options** button allows you to add optional fields to a step. Here is an example of where to find that:

<figure><img src="/files/X6vfVVNWon4fMLxcdun7" alt="Screenshot of a MESA step where additional optional fields can be added, spotlight the More Options button."><figcaption></figcaption></figure>

<figure><img src="/files/Y4b68wHSwLBDS9ucwmTA" alt="Screenshot of a MESA step with the More Options list expanded showing the additional fields available to add, spotlight the list of additional fields."><figcaption></figcaption></figure>
