On this page

Jump to any section using the links below

Good data quality is essential for workflows, automations, booking, and integrations.
Hubhus provides several layers of validation to ensure leads contain the information you need — including required fields, form-level validation, automation-based checks, and duplicate detection.

This article explains how each validation layer works and how to configure it safely.

1. System-level required fields (hard validation)

A field marked as Required at campaign level becomes a hard requirement.

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

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

• Users cannot save the lead without entering the value

• Automations or external integrations must include this field

This is the strictest form of validation and should only be used for fields that are always known at creation time.

Use system-level required fields for:

• Customer name

• Email

• Phone number

• Mandatory internal reference

• Absolutely critical workflow inputs

2. Form-level required fields (soft validation)

Forms and pages (e.g. booking forms, campaign pages, custom HTML forms) allow you to set required fields only for that specific form, without making the field required in the entire system.

How to make a field required in a form

Use the required flag inside an input component:

@input[company-name; required]

This prevents submission from that specific form, but does not block:

• API-created leads

• Internal user creation

• Automations

• Other forms

When to use form-level validation

• Making sure customers provide essential details

• Only requiring data for certain entry points

• Optional internal fields that shouldn’t block external workflows

Important caution

When working with external vendors or API integrations, be careful:

Requiring fields like:

• full address

• specific phone number formats

• country restrictions

• detailed product info

…can cause integrations to fail if external systems cannot deliver those values.

Use form-level required fields instead of system-level required fields if the field is not always guaranteed.

3. Using automations to validate data

Automations can check lead data after creation and flag incomplete or inconsistent data.

Examples of validation automations

• Move the lead to a “Missing info” status

• Notify internal staff when required information is missing

• Send a page to the customer requesting missing details

• Automatically fill defaults when certain fields are empty

• Perform follow-up loops until data is corrected

Common validation triggers

• “Field updated”

• “Lead created”

• “Status changes”

• “On interval” (runs every X minutes)

Automation-based validation is ideal for workflows where data is collected gradually.

4. Preventing incomplete leads

Hubhus offers multiple layers to prevent incomplete data:

A. System-level required fields

Lead cannot be created without them.

B. Form-level required fields

Forms (pages/booking forms) enforce validation only where needed.

C. Automations

Catch missing fields and trigger follow-up actions automatically.

D. Lead-table filters (“Has value in” / “Has no value in”)

Create dashboards or views showing which leads need attention.

E. File and relation checks

Verify whether customers have uploaded required documentation or completed tasks.

5. Duplicate detection (dubletkontrol)

Hubhus includes configurable duplicate detection to prevent multiple leads for the same person or case.

(Screenshot: Doublet settings panel)

You can configure duplicates by choosing:

Fields used to identify duplicates

Examples:

• Email

• Phone number

• Reference ID

You can choose:

• All fields must match

• Just one field must match

Select fields that must also match

For example:

• Reference groups

• Campaign sources

Status exceptions

You can specify statuses that should not trigger duplicate warnings.

Time window

You can restrict duplicate detection to leads created within a certain time period.

Automatic actions

When a duplicate is detected, you can automatically:

• Set status on the new duplicate lead

• Set a select value on the new duplicate lead

• Set status on the existing lead

• Set a select value on the existing lead

This allows internal routing or tagging of duplicates instead of merging.

Showing duplicate warnings

You can choose to show a warning on the lead profile page.

Hiding duplicates in the lead table

You can also hide or ignore duplicates in your lead-table view by filtering on:

• status

• select tags

• missing info

• or by using “Has relation” filters

Hubhus does not support merging leads — instead duplicates can be tagged, labelled, or routed using the rules above.

6. Integrations and external systems

For API-based lead creation:

• Required campaign fields must be included

• Form-level required flags do not affect API

• Duplicate detection will still run

• Automations will still run

• Validation errors prevent creation if fields are missing

External systems should always send:

• the correct source value

• mandatory data

• valid select slugs

7. Hiding duplicates or irrelevant leads using Table Options

If you use duplicate detection rules or tag duplicates with a dedicated status, you can hide them globally in the campaign’s lead table.

To configure this:

1. Open the campaign lead table

2. Click Options (top-right corner)

3. Scroll to Hide leads with these statuses from table

4. Select the statuses you want to hide

(Screenshot reference: "Table options" from your upload)

This setting is applied for all users, and is ideal for hiding:

• detected duplicates

• leads tagged by automation

• abandoned or “blocked” leads

• spam or invalid entries

• workflow end-states (e.g. “Customer declined”)

Using table-level hiding gives you a clean operational view without modifying or merging data.

Learning outcome

After reading this, you understand:

• The difference between system-level and form-level required fields

• How to apply validation without blocking external systems

• How to validate data using automations

• How Hubhus duplicate detection works

• Why Hubhus avoids merging and instead uses tagging/routing

• How to prevent incomplete or inconsistent leads

? 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?