How do I validate lead data automatically?

Modified on Tue, 5 May at 11:31 AM

How do I validate lead data automatically?

Good data quality is essential for automations, bookings, and integrations. Hubhus offers four layers of validation — from hard required fields to automation-based checks — so leads always contain the information your workflows need.

TL;DR

Mark critical fields as required at system level (Campaign Settings → Fields). Use form-level required for booking/form input only. Use automations to flag missing data after creation. Use lead-table filters to spot incomplete leads. Enable duplicate detection for clean customer records.

4 validation layers in Hubhus

System-level required fields (hard)

Mark a field as required in Campaign Settings → Fields. A lead cannot be saved unless the field has a value. Use only for data that is always known at creation time — e.g. name, email, phone.

Form-level required fields (soft)

Mark fields as required directly in a booking form or lead form. Prevents the form from submitting without the value, but does not block saving the lead from other sources (e.g. API, import).

Automations for post-creation checks

Use automation rules to detect incomplete leads after they're created — e.g. trigger when a lead is created, check if email is empty, then set a status flag or notify an admin. More flexible than hard required fields.

Lead-table filters and duplicate detection

Use "Has value in" / "Has no value in" filters in the lead table to spot incomplete records. Enable duplicate detection in Campaign Settings to prevent the same customer appearing twice.

Read more⌄

Automation validation examples

Trigger: Lead created
Condition: email is empty
Action: set status = "Missing email" + notify admin

Trigger: Lead created (delay 30 min)
Condition: phone AND email are both empty
Action: set status = "Incomplete" + send internal alert

Best practices

Use system-level required fields only for data that is always available at creation time — avoid blocking leads from being created via API.
Use form-level required for booking forms and customer-facing input.
Use automations for flexible, post-creation validation without hard blocking.
When adding a new required field, consider existing leads — don't break historical records with retroactive requirements.
Combine duplicate detection with auto-relate rules to keep your customer records clean.

Common searches

required field lead • validate lead data • duplicate detection • missing email lead • incomplete lead automation

How do I create automation rules?
How do I create custom fields?
How do I set up a new campaign?
Understanding the lead lifecycle