On this page

Jump to any section using the links below

Good lead data is essential for bookings, automations, workflows, and integrations.
Hubhus provides multiple validation layers that ensure fields are filled correctly, formats are valid, and duplicates are handled safely.

This article explains how required fields work, how to use form-level validation, how automations can enforce data quality, and how to prevent incomplete or duplicate leads.

1. Required field validation (System-level)

System-level required fields apply to the entire campaign, not just a single form.

How to mark a field as required

1. Open the campaign

2. Go to Fields

3. Select a field

4. Enable Required

5. Save

What this means

• The lead cannot be created unless the required field is filled

• Internal users cannot save the lead without completing it

• API and external integrations must provide the field

• This is the strictest validation layer

When to use system-level required fields

Use this only for data that is always known at creation time, for example:

• Name

• Email

• Phone

• Mandatory internal reference

• Core business identifiers

2. Form-level validation (Soft required fields)

Hubhus forms (booking forms, pages, campaign forms) allow you to require fields only when submitted through that specific form, without restricting API or internal creation.

How to mark fields as required in a form

Using input components:

@input[company-name; required]

What this means

• The customer must fill the field to submit the form

• Internal users and API integrations are not blocked

• Does not globally mark the field as required

Best practice

Use form-level required fields for:

• Customer-facing forms

• Booking forms

• Conditional steps

• Situations where not all leads originate from the same channel

Warning for external vendors

If partners or integrations create leads:

• Avoid requiring fields that they cannot always provide

• Avoid strict formatting (e.g., full address, Danish phone formats)

• These restrictions should only be set at the form-level

Use system-level required fields only when you control all entry points.

3. Custom validation rules

Each field can include custom format or logic rules.

You can define:

• allowed values (in-list rules)

• formatting restrictions (length, numeric, matching patterns)

• conditional visibility (fields appear only when related values are set)

• country-based rules when applicable

These rules enforce structure but remain flexible compared to system-required fields.

4. Using automations for validation

Automations can check lead data and react when fields are missing or invalid.

Common validation automations

• Move lead to a “Missing info” or “Needs attention” status

• Send an internal notification

• Send customer page link to complete missing information

• Re-check lead data on interval until resolved

• Auto-populate fields when default values are acceptable

Typical triggers

• Lead created

• Field updated

• Status changed

• Interval runs (every X minutes)

Automations are the best tool for ongoing data cleanup.

5. Preventing incomplete leads

Here are the main strategies:

A. System-level required fields

Hard validation — prevents creation without required data.

B. Form-level required fields

Soft validation — ensures customer input is complete without blocking all sources.

C. Automations

Catch missing or invalid values after lead creation.

D. Lead-table filters

Use Has value in / Has no value in to create dashboards for missing data.

E. File upload and relation checks

Ensure documents or required files are uploaded before moving forward.

6. Duplicate detection (Doublet settings)

Hubhus detects duplicates (doublets) based on configurable rules.

(Screenshot reference: Doublet settings)

You can configure:

Fields used to identify duplicates

Examples:

• Email

• Phone number

You can choose:

• All fields must match

• Just one field must match

Select fields that must also match

Useful when duplicates should only be flagged within the same category or reference value.

Statuses to ignore

If a lead is in a specific status (e.g., “Closed”), duplicates will not trigger warnings.

Time window

Require duplicates to be created within X minutes/hours/days.

Automatic actions

When a duplicate is detected, set:

• status on the new duplicate lead

• select field on the new duplicate lead

• status on the existing lead

• select field on the existing lead

This lets you tag duplicates instead of merging them.

Important: Hubhus does not support merging leads.

Instead, duplicates are:

• flagged

• tagged

• auto-classified

• visually filtered out

7. Hiding duplicates in the lead table

After duplicates are tagged with a specific status, you can hide that status from the lead table.

How to hide statuses globally

1. Open the lead table

2. Click Options

3. Find Hide leads with these statuses from table

4. Select the statuses to hide

(Screenshot reference: Table Options)

This removes duplicates from daily operations without deleting or merging them.

Learning outcome

After reading this, you understand:

• The difference between system-level and form-level validation

• How to validate customer input safely without blocking API integrations

• How to use automations for ongoing data validation

• How Hubhus handles duplicate detection

• How to hide duplicates from your lead table

• How to maintain high data quality across workflows

? Common searches

lead management • lead tracking • customer management

? Also known as

customer • contact • prospect

Related articles

How do I validate lead data automatically?
Configuring search settings
How do I filter leads by specific criteria?
How do I give API access to a specific campaign?
How do I set up a new campaign?