Types de questions avancés

Legal / Terms

A terms and conditions acceptance question that presents a statement and requires the respondent to accept or decline.

Type identifier: legal

Properties

Behavior

• Displays the legal text from buttonText.
• The respondent clicks "I accept" or "I don't accept".
• Typically used for privacy policies, terms of service, consent forms, and data processing agreements.

Validation

If required is true, the respondent must accept the terms to proceed. Declining (selecting "I don't accept") when the question is required will show a validation error.

Logic Jump Operators

equals, not_equals, is_answered, is_not_answered

When using equals, compare against true (accepted) or false (declined).

Answer Format

The answer is stored as a boolean (true for accept, false for decline, or null if unanswered).

Quiz Mode Scoring

Legal is a scorable question type:

• Knowledge Quiz: Set correctAnswers with "true" or "false".
• Lead Qualification: Set choiceScores with keys "true" and "false".
• Match Quiz: Set choiceOutcomes mapping acceptance/decline to end screens.

Payment

Collect payments from respondents as part of the form flow using Stripe integration. Supports two payment modes, configurable currencies, and fixed or variable amounts.

Type identifier: payment

Payment Modes

Properties

Behavior

• If price is set, the respondent sees the fixed amount and provides card details.
• If price is not set, the respondent enters their own amount (variable/donation mode).
• The Stripe Payment Element is rendered for secure card collection.
• On successful payment, the form auto-advances to the next question.

Validation

If required is true, the respondent must complete the payment to proceed.

Logic Jump Operators

equals, not_equals, is_answered, is_not_answered

Answer Format

The answer is stored as a PaymentResult object:

{
  "paymentIntentId": "pi_abc123",
  "amount": 2999,
  "currency": "usd",
  "status": "succeeded"
}

Date

A date picker that allows respondents to select a date. Supports configurable date formats.

Type identifier: date

Properties

Behavior

• Displays a date picker interface.
• The respondent can type a date manually or select from a calendar widget.
• The date is stored in ISO format regardless of the display format.

Validation

If required is true, the respondent must select a date.

Logic Jump Operators

equals, not_equals, is_answered, is_not_answered

Answer Format

The answer is stored as a string (the date value, typically in ISO format or the configured dateFormat).

Ranking

Present a list of items for the respondent to arrange in their preferred order by dragging and dropping.

Type identifier: ranking

Properties

Behavior

• Items are displayed in a list.
• The respondent drags items to reorder them.
• Drag handles indicate draggable items.
• Touch and mouse interaction are both supported.

Validation

If required is true, the respondent must submit a ranking.

Logic Jump Operators

equals, not_equals, is_answered, is_not_answered

Answer Format

The answer is stored as an array of strings (choice IDs in the respondent's ranked order).

Matrix

A grid-based question type where respondents rate multiple items across multiple categories.

Type identifier: matrix

Properties

Behavior

• Displays as a grid with rows on the left and columns across the top.
• The respondent selects one option per row.
• On mobile, the grid adapts to a stacked format for better usability.

Validation

If required is true, the respondent must select an option for every row.

Logic Jump Operators

equals, not_equals, is_answered, is_not_answered

Answer Format

The answer is stored as an object mapping row labels to selected column labels:

{
  "Quality": "Excellent",
  "Speed": "Good",
  "Support": "Average"
}

Contact Info

Collect structured contact information including name, email address, and phone number in a single question.

Type identifier: contact_info

Properties

Behavior

• Displays fields for First Name, Last Name, Email, and Phone Number.
• The phone field includes a country code selector.
• Each sub-field can be individually required or optional.

Validation

If required is true, all visible sub-fields must be completed.

Logic Jump Operators

equals, not_equals, is_answered, is_not_answered

Answer Format

The answer is stored as an object:

{
  "firstName": "Jane",
  "lastName": "Smith",
  "email": "jane@example.com",
  "phone": "+14155551234"
}

Address

Collect a full mailing address with optional autocomplete powered by Google Places.

Type identifier: address

Properties

Behavior

• Displays fields for street address, city, state/province, postal code, and country.
• When autocomplete is enabled, typing in the street field shows address suggestions.
• Selecting a suggestion auto-fills all address fields.

Validation

If required is true, all address fields must be completed.

Logic Jump Operators

equals, not_equals, is_answered, is_not_answered

Answer Format

The answer is stored as an object:

{
  "street": "123 Main St",
  "city": "San Francisco",
  "state": "CA",
  "postalCode": "94105",
  "country": "US"
}

Data Node

An invisible question type that makes HTTP API calls during the form flow. Data Nodes are not rendered to respondents — they execute automatically and can fetch data, validate answers, or trigger external actions.

Type identifier: data_node

Properties

Behavior

• Executes automatically when reached in the form flow.
• All {variableName} tokens in URL, headers, and body are replaced with current variable values.
• If dataNodeResponseVariable is set, the full JSON response is stored as a form variable.
• In silent mode, the request fires in the background with no loading indicator.
• In validation gate mode, a failing request blocks progression from the previous question.

Use Cases

• Fetch external data: Look up product details, pricing, or user profiles during the form flow.
• Validate answers: Check an email against your database, verify a coupon code, or validate an address.
• Trigger actions: Send data to a webhook, create a record in your CRM, or start a workflow.

Common Advanced Features

Rich Text in Titles and Descriptions

All advanced question types support rich text in their title and description fields. Rich text is entered through a Tiptap-based editor in the form builder and supports:

• Bold, italic, underline, and strikethrough
• Links (with href, target, rel attributes)
• Ordered and unordered lists
• Inline code
• Subscript and superscript
• Custom font families and colors via inline styles

The rich text is stored as HTML and sanitized before rendering using DOMPurify with a strict allowlist of tags and attributes.

Variable Substitution

All advanced question types support {variableName} substitution in their title and description fields. See the Variables guide.

Media Attachments

All advanced question types support media attachments (image, video, icon, QR code) with the full range of layout options. See the Creating Forms guide.