This page lists all possible input blocks for the Huwise Forms feature, and how to configure them.

See this page for more information about the feature and instructions on how to edit your forms.

Every input block in your form is automatically assigned a technical ID.

The technical ID is a unique identifier that identifies the corresponding field in the dataset created for your form's results.

In general, if you wish to change these IDs, we strongly recommend doing so before you publish and share your form, in order to avoid any discrepancies arising from results arriving before and after any change to an ID.

Most blocks offer two setting toggles:

Unique values: Toggle this to require that the value entered does not repeat any previously entered values.

Required: To make responding to this question or field obligatory.

And in general, regarding blocks that require users to input text:

• You can add placeholder text by typing directly into the input field (the first red box in the image below)

• You can provide helper text (the second red box below)

Your form can be made to adapt to user input by displaying new blocks only if they're relevant to that user.

For example, if your form allows users to report an issue, the questions can be tailored to the specific type of issue, such as a technical problem versus a billing issue. To achieve this, define the conditions for hiding or displaying each block.

To add a condition, double-click the block you want to edit and select "Add a condition." and defines:

• An action: Show the target (display it only when conditions are met) or Hide the target (hide it when conditions are met).

• An operator: AND (all conditions must be true) or OR (at least one condition must be true).

• One or more conditions, each linked to a source field in the form.

The exact configuration options you're shown in the interface will depend on the type of input block and how constrained the user's answers are. A block where the user chooses from predefined values, or example, will have different options than a block where the user can freely enter their own responses.

You will decide whether the block is visible based on user input, considering conditions that depend on the type of the source field:

Note that "contains" and "does not contain" are case insensitive. In blocks with multiple possible responses, "is" or "is not" are inclusive—they require all of the designated responses to be present. If you want only one response to be enough, use "is any of."

Note that circular dependencies are not allowed. If field A's visibility depends on field B, then field B's visibility cannot depend on field A. The platform validates this automatically and prevents you from saving a circular configuration.

A general-purpose text input for collecting short or long written answers — names, descriptions, feedback, or any free-form text.

A text input specifically designed for web addresses. The platform automatically validates that the entered value is a properly formatted URL (e.g., https://example.com).

A specialized input for French business identification numbers. SIRET stands for "Systeme d'Identification du Repertoire des Etablissements" — it's a 14-digit code that uniquely identifies a business establishment in France. The platform automatically validates the SIRET checksum to ensure the number is correctly formatted and mathematically valid.

Note that SIRET validation is strict: the platform checks not only the length and format but also the mathematical checksum of the number. A random sequence of 14 digits won't pass validation.

A numeric input that accepts either whole numbers or decimal values, with optional minimum and maximum boundaries.

A visual rating input that lets respondents express a level of satisfaction or agreement. You can choose between a star-based pictogram scale or a wider numeric scale.

A single- or multiple-choice question with a predefined list of options. You control how the options are displayed and whether respondents can add their own answers.

A choice field whose options are loaded automatically froma dataset on your workspace. This is useful when the list of options changes frequently or is too large to maintain manually.

An enhanced version of Dynamic Choice that goes one step further: when the respondent selects an option, other fields in the form are automatically populated with related data from the same source. For example, selecting a company name could auto-fill the company address and phone number.

Auto-Fill inherits all settings from Dynamic Choice, plus:

A selection field that lets respondents pick one or more datasets from your workspace. The platform validates that the selected datasets exist.

A tag-style input that lets respondents add multiple keywords or tags. Each keyword is entered individually, and the field displays them as removable chips.

A structured block that collects contact information through multiple subfields. Unlike adding several separate Text fields, the Contact block groups related information together and provides specialized validation for each piece of data.

The Contact block includes six subfields, each of which you can independently configure:

Each subfield has its own label, placeholder, help text, and required toggle — all of which support localization.

In addition to the per-subfield settings, the Contact block offers these options:

Note that email and phone number uniqueness are checked independently. You can enable uniqueness on one, both, or neither.

A location input for collecting postal addresses or specific geographic identifiers. You can configure it to collect a full address or narrow it down to a postal code, city name, or INSEE code (a French commune identifier).

INSEE code is a 5-digit code used in France to uniquely identify each commune (municipality). It's commonly used in administrative and statistical contexts.

Note that when the input type is set to Postal code, the platform validates that the entered value follows the 5-digit format.

A flexible picker for collecting dates, times, or time slots. You can configure it to collect just a date, just a time, or a time range with opening and closing times.

A file upload field for collecting documents, spreadsheets, PDFs, and other files from respondents. You control whether respondents upload files directly, provide a URL reference, or both.

Note that when a submission is deleted or updated, any files that are no longer referenced are automatically cleaned up from storage.

An image-specific upload field with built-in image format validation. It works like the File Picker but is restricted to image files.

A yes/no checkbox for collecting binary answers (true/false, agree/disagree, opt-in/opt-out).

A geographic location picker that lets respondents select a point on an interactive map. This is useful for collecting precise coordinates — for example, the location of an event, a reported issue, or a point of interest.

A mandatory consent block for collecting agreement to privacy policies, terms of use, or custom legal terms. Unlike other field types, the Legal block doesn't have a configurable label — it displays the legal text directly.

There are two important things to know about Legal fields:

• Acceptance is mandatory. Every respondent must check the consent checkbox before submitting the form. The platform validates this automatically.

• Consent data is not stored. Legal field responses are validated at submission time but are not included in the stored submission data. This means Legal fields are also excluded from dataset extraction. They serve solely to collect the respondent's agreement at the moment of submission.