Understanding custom fields
All fields in Hubhus are custom fields — there are no predefined system fields inside campaigns. Every piece of data you collect is a field you create. This gives campaigns complete flexibility to match any workflow or industry.
TL;DR
Fields define the data model for a campaign. Types: text, number, date, select (dropdown), JSON/data, checkbox. Select fields categorize leads (used in @if logic and automation). Resource tags classify resources for booking routing. User tags group users for access control. Keep API slugs stable once in use.
6 field types to know
Text
Free-form input — names, addresses, descriptions, notes, order references. Most flexible but hardest to filter precisely. Use select fields when only specific values are valid.
Number
Quantities, prices, measurements, numeric codes. Supports numeric comparison in @if expressions and automation rules.
Date
Deadlines, delivery dates, planned start dates. Supports date comparison (before/after) in automations and @if logic.
Select (dropdown)
Only pre-defined values allowed — e.g. product type, region, urgency. Essential for filtering, automation, consistent reporting, and conditional logic. Always prefer select over free text for categorization.
JSON / Data field
Structured or nested data, lists, multi-item orders, technical specs. Used in advanced workflows and integrations. Set via jQuery('#df_slug').val(JSON.stringify(data)).
Checkbox / Boolean
Simple yes/no. Useful for opt-ins, consent flags, internal status flags. Evaluates as true/false in @if and automation conditions.
Read more⌄
Select fields vs. Resource tags vs. User tags
- Select fields — categorize leads. Used in @if logic, automation conditions, API payloads, and dashboards. Examples:
customer_type,region,product_category. - Resource tags — classify resources (technicians, teams, vehicles). Control which resources a booking form is allowed to use. Examples: Team North, Installer.
- User tags — group users for access control and permissions. Can be linked to resource tags to control which users appear as eligible assignees in booking forms.
Field naming best practices
- Use clear, descriptive names:
customer_address— notaddr2 - Keep API slugs stable once used in automations or API integrations
- Group related fields with consistent prefixes:
measurement_width,measurement_height - Use select fields instead of free text for categorization
- Only create fields for actual process needs — don't pre-create fields "just in case"
Common searches
custom fields Hubhus • field types • select field • resource tags • data field • field configuration
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article