Skip to documentation

Feedback Page question types and validation

Choose among rating, text, choice, structured input, attachment and layout fields.

Updated Read as Markdown

The form API and builder support 18 question and layout types. Content blocks and section headers organize a form; they do not collect answers.

Type Use and configuration
thumbs Binary feedback, scores 0/1
stars 1–5 star rating
csat 1–5 satisfaction
nps 0–10 recommendation
emoji Five sentiment choices, scores 1–5
text Single-line or multiline input; placeholder, length and optional validation
single_choice One answer from configured options
multi_choice Multiple answers from configured options
dropdown A compact single selection; options, placeholder and optional search
ranking Reorder configured options; first item is rank 1
email An email address with format validation
phone Phone input with formatting options
number Numeric input with minimum, maximum, step and optional unit
date Date input, optionally including a time
file_upload One or more allowed attachments
voice A browser-recorded audio attachment
content_block Display-only Markdown, stored in config.markdown
section_header Display-only heading with an optional description

Configure validation

Mark a question required only when the workflow needs an answer. A required field that is later cleared must be answered again before submission. Display-only fields are excluded from required-answer validation.

For text, choose single-line or multiline and, when appropriate, email, phone, URL or regular-expression validation. Provide a clear validation message. Number fields can enforce a range and step; test a valid value, a boundary and a value between steps. Date fields can have minimum/maximum dates and an optional time input.

json
{
  "type": "number",
  "prompt": "How many seats do you need?",
  "required": true,
  "config": { "min": 1, "max": 100, "step": 1, "unit": "seats" }
}

This is an example question object, not a complete create-form request. See the forms API for the full payload.

Layout and content

Use section headers for groups and content blocks for instructions, links or code examples. Markdown is presentation content, not a mechanism for adding custom executable scripts to a form. Use a short prompt as the editor's label for a content block and put its actual text in the Markdown setting.

Review output, not just the editor

Submit the form with realistic test values and inspect the saved response. Ratings use scores; text, number and date answers have their own stored representations; choice/ranking and uploaded attachments have different structures. Do not treat every answer as a comment string.

For attachment limits and microphone requirements, see drafts and attachments. For question-by-question public visibility, see live results.