How to add custom fields to booking forms

Modified on Thu, 4 Dec at 11:33 AM

How to add custom fields to booking forms

Booking forms can collect additional information by adding custom Hubhus fields directly into the form layout.

On this page

Jump to any section using the links below

Booking forms can collect additional information by adding custom Hubhus fields directly into the form layout. These fields can be validated, shown conditionally, and used in emails and automations.

This article explains how to add custom fields, set validation rules, and ensure the data is available for later use.

Adding custom fields to a booking form

Table of Contents

Adding custom fields to a booking form

Example

Making fields required
Field validation options
Using custom field data in emails

Example usage:

Best practices
Summary

In the booking form editor, you can insert fields using the standard Hubhus input syntax:

@input[field-slug]

Where field-slug is the API name of your custom field.
You can place the field in:

Part 1 (before selecting date)
Part 2 (during the booking process)
Part 3 (confirmation step)
Part 4 (post-submission content)

Use the placement that matches your user flow.

Example

@input[project-description]

This adds a text field linked to the custom field “project-description”.

Making fields required

To require a field inside a booking form, use the required attribute:

@input[project-description; required]

Important distinction:

Form-level required
Only applies to this booking form. Prevents submission unless filled.
Field-level required in campaign settings
Prevents creation of a lead if the field is missing.
Use this with care, especially for external vendors.

Field validation options

Validation depends on the field type:

Text fields can be required or pattern-validated
Number fields can enforce numeric input
Select fields enforce one of the defined options
Date/time fields can use validation attributes (minute steps, min/max dates)
Address fields rely on the DAWA component built into the form

For select fields, always use slugs for logic later in automations or templates.

Using custom field data in emails

Any field added to a booking form becomes available as a placeholder in:

Confirmation emails
Automation emails
Internal notifications
HTML components
Campaign pages

To find the correct placeholder, press:

CTRL+K on Windows
CMD+K on Mac

Search by the field’s name or slug.

Example usage:

@if({{project-description}}){
The project description you entered: {{project-description}}
}@endif

Best practices

Keep booking forms simple; only ask for what you truly need
Place important fields early (Part 1) to avoid abandoned bookings
Use descriptive field names to improve placeholder search
Use required fields sparingly for external vendors
Use select fields instead of free text when you need consistent reporting
Insert JavaScript only in the Styling → Custom JavaScript section or in a reusable HTML component

Summary

To add custom fields to booking forms, insert them using @input[field-slug], optionally make them required, and position them across the booking flow as needed. All collected data becomes available for emails and automations, allowing you to personalize communication and drive workflows efficiently.

? Common searches

booking setup • calendar setup • appointment scheduling • booking configuration

? Also known as

appointment • scheduling • reservation • calendar event

How to calculate values and format numbers in templates
How to format dates and calculate time differences
How to use custom fields in automation and triggers
How do I create custom fields?
How do I manage SELECT fields and dropdown options?