​

Input fields and validation

Input fields collect data right on the card. The answers live in the form’s scope and can be used in texts, rules, and actions.

​

Field types

Card Studio offers:

• short text;
• long text;
• number;
• dropdown;
• multiple choice;
• date;
• checkbox;
• button group.

Each input field has a unique internal field key. The designer creates it automatically. Two input fields must never end up with the same key.

​

Basic settings

• Label is the user-facing label and is required.
• Field type determines the control and which validations apply.
• Required marks the field as required in the rendered component.
• Default value can be fixed or bound to a HubSpot property, for example.

A default value from a CRM property is useful for editing existing data. Checkboxes interpret values such as true, 1, yes, and ja as checked. HubSpot multi-select values are split at semicolons.

​

Options

Dropdown, multiple choice, and button group need options. You can:

• use the manual default options;
• copy options from a HubSpot enumeration property;
• fetch rows from an associated-records data source.

On import, up to 30 options are copied into the card. Changes to the HubSpot property’s options are not synced automatically after import; import again or update the card. The current designer does not have a full editor for renaming the manual default options one by one. Use import from a HubSpot property or an association data source when the actual labels matter. With dynamic association options, hs_object_id is used as the value. You can pick a primary and a secondary field for the visible label. The selected row’s fields become available elsewhere on the card.

​

Validation

Short text can be validated as:

• an email address;
• a phone number;
• a URL starting with http:// or https://;
• an eight-digit CVR number (spaces are accepted).

Short and long text can have a minimum and maximum number of characters. Numbers can have a minimum and maximum value. The minimum must not be greater than the maximum. Format errors are shown while the user types. Empty values pass format validation; the required check is handled separately.

​

Required fields in flows

On a multi-step card, you must also mark the input field under Required fields on this step if Continue or Submit should be blocked until the value is filled in. A required checkbox must be checked. When jumping forward to a later step, all intermediate steps are validated. Backward navigation does not validate.

​

Save answers per record

Enable Save form data on the record in Card settings to save the form scope per record. Changed fields are saved as a delta, and remote updates are merged in without overwriting fields the user is currently editing. This is Card Studio’s form storage, not a HubSpot property. If the answer needs to be used by HubSpot lists, workflows, or reporting, add an action that updates the relevant CRM property.

​

Write to HubSpot

Add a regular button or a submit action:

1. choose Update a property on the record;
2. choose the HubSpot property;
3. choose Form · [input field] as the new value;
4. optionally add Show a message afterwards.

Test the data type and the HubSpot property permissions. A text answer cannot necessarily be written to a numeric or enumeration-based property without a compatible format.