On this page

Jump to any section using the links below

Custom fields define the data structure of each campaign.
Because Hubhus does not provide predefined fields inside campaigns, every piece of information you collect — name, address, product type, notes, technical data, etc. — is created entirely by you. This makes campaigns flexible and adaptable to any workflow or industry.

This article gives a simple overview of how custom fields work and how to design them effectively.

What are custom fields?

Custom fields store all data associated with a lead inside a campaign.
Examples include:

• Customer name

• Address

• Order number

• Notes

• Product selection

• Measurement dates

• Region

• Internal reference IDs

Every field you create:

• Has a type (text, number, select, JSON, etc.)

• Has an API name used for placeholders, logic, and API

• Is unique to the campaign in which it is created

Because campaigns represent different workflows, their fields will naturally differ — a “Quote” campaign does not share fields with an “Installation” or “Support” campaign.

Field types (text, number, select, date, etc.)

Hubhus supports several field types so your campaign structure can match your real-world process.

Text fields

Used for: names, free text, descriptions, addresses, notes.

Number fields

Used for: quantities, prices, measurements, numeric codes.

Date fields

Used for: deadlines, delivery dates, planned start dates.

Select fields (dropdowns)

Used when only specific values should be allowed (e.g. product type, region, urgency).
Select values are ideal for filtering, automation, and consistent reporting.

JSON / Data fields

Used for structured or nested data, lists, or large variable objects (e.g. technical specs, multi-item orders).
Often used in advanced workflows and integrations.

Checkbox / Boolean

Used for simple yes/no logic.

When to create custom fields

Create new fields when you need to:

• Store new information the workflow requires

• Filter or segment leads

• Build conditional logic in pages, emails, or automations

• Sync data from an integration or API

• Add structured inputs to a booking form

• Track process-specific details (e.g. measurements, product type, inspection results)

Avoid creating fields if:

• The information can be derived from an existing field

• It belongs in another campaign

• It is a temporary internal note

• A select field would serve better than free text

SELECT fields (lead-level data)

Select fields belong to the campaign data model.
They categorize leads and are used for:

• segmentation

• filtering

• reporting

• conditional logic (@if)

• automations

• API payloads

Examples:
customer_type, region, urgency, product_category.

Select fields describe the lead, not users or resources.

Tags

Resource tags

Resource tags classify resources — the entities that can be booked (technicians, teams, vehicles, rooms, etc.).

Resource tags are used for:

• controlling which resources a booking form is allowed to use

• routing based on skills, region, team, or capabilities

• filtering availability

• multi-resource logic

Examples:
Team North, Inspection, Installer, Vehicle Required.

Booking forms use resource tags to select the correct resources dynamically.

User tags

User tags organize users (internal staff) into permission or visibility groups.

User tags are used for:

• access control

• grouping users for internal workflows

• filtering internal views

• permissions for teams or departments

User tags do not affect availability directly.

Linking user tags to resource tags

Hubhus allows you to link user tags to resource tags.
This is used to control which users can be assigned via a booking form.

Important details:

• A resource tag can be associated with multiple user tags

• Users inherit the ability to be selected if their user tag matches a linked resource tag

• This creates clean control over who is eligible for certain tasks/services

Example:

• Resource tag: Inspection Technician

• Linked user tags: Tech Group A, Tech Group B

• Result: Only users in those groups can be assigned when the booking form requests an “Inspection Technician”.

Summary: SELECT fields vs. Resource Tags vs. User Tags

Field naming best practices

1. Use clear, descriptive names

Good: customer_address
Bad: addr2

2. Keep API slugs stable

Once used in automations or API → avoid renaming.

3. Group related fields with consistent patterns

Example:

• measurement_width

• measurement_height

• measurement_depth

4. Use select fields instead of free text

They improve filtering, reporting, and logic consistency.

5. Avoid unnecessary fields

Fields should represent actual process needs — not temporary data.

Learning outcome

After reading this, you should understand:

• What custom fields are and why all campaign fields are custom

• The different field types and when to use them

• When to create new fields

• The difference between select fields and resource tags

• How to name and structure fields for clean, scalable workflows

? Common searches

custom fields • field setup • data fields • field configuration

? Also known as

data field • custom field • input field

Related articles

Understanding the Hubhus data model
What is the Hubhus API?
Building workflows in Hubhus
Understanding action listeners
What is automation in Hubhus?