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

# Input field

> Collect text, numbers, choices, dates, and checkboxes on the card.

# Input field

**Input field** collects an answer that can be used in dynamic text, rules, and actions. It does not automatically write to a HubSpot property.

## Availability

Input field can be used in all placements. It must not be placed inside a Repeater, because every repeated row would otherwise share the same field key.

## Add and configure

Set:

* **Label** — up to 80 characters;
* **Field type** — short text, long text, number, dropdown, multiple choice, date, checkbox, or button group;
* **Required** — marks the control as required;
* **Default value** — fixed or dynamic.

The field key is created automatically and must be unique on the card.

## Choice fields

Dropdown, multiple choice, and button group must have either manual options or options from a data source — never both at the same time.

You can import up to 30 options from a HubSpot enumeration property. If the card uses an association list, the options can instead be associated records. Pick up to two properties as the visible label; the record ID is stored as the value.

The selected row becomes available as dynamic **Selected \[object]** fields and can be the target of a CRM update action.

## Validation

* Short text: email, phone, URL, or CVR format.
* Short/long text: minimum and maximum number of characters.
* Number: minimum and maximum value.

The schema allows a length limit of up to 5,000 characters. The minimum must not exceed the maximum. Validation errors are shown as you type; empty choices are checked separately as required.

## Save and write answers

Enable **Save form data on the record** in the card settings to keep Card Studio answers per record. Add the **Update a property on the record** action if the answer should go into an actual HubSpot property.

On flows, the field must also be checked under **Required fields on this step** if navigation should be blocked when the value is empty.

See [Input fields and validation](/building/forms) for a complete guide.

## Limitations and tips

The schema also has placeholder and description fields, but the current inspector does not show them. It also lacks a full editor for the labels/values of manual default options.

Choose labels that also work in error messages and action pickers. Avoid two fields with the same label, even if their internal keys are different.