Understanding custom fields
All fields in Hubhus campaigns are custom fields you create. Field types are semantic (Default, Phone, Email, Number, Date, Check, JSON, and more). There is no Field type named Select - dropdowns are created with field Rules or with dedicated lists under Selects.
TL;DR
Fields define the campaign data model. Types include Default, Phone, Email, Number, Date, Check, JSON/data - not a type called Select. For dropdown values: open the field’s Rules (“Must be one of these options”). Resource tags classify resources for booking. User tags group users for access. Keep API slugs stable once in use.
6 things to know
Default and text-like fields
Default (and similar free-form types) store names, notes, references, and many business values. Most flexible. When only specific values are valid, constrain them with Rules instead of inventing a Select type.
Number
Quantities, prices, measurements, numeric codes. Supports numeric comparison in conditions and automation rules.
Date / time types
Deadlines, delivery dates, planned start dates, and related date/time variants in the Field type list. Useful for automations and comparisons.
Dropdowns via Rules (not a Select type)
There is no Field type called Select. Create/open a field (often Default) → Rules → Must be one of these options (single) or multi-select rule → enter options. Rules available change with field type. For named lists with slugs and per-option actions, use Campaign settings → Selects - see the dropdown options article.
JSON / Data field
Structured or nested data, lists, multi-item orders, technical specs. Used in advanced workflows and integrations.
Check / boolean
Simple yes/no (Field type Check). Useful for opt-ins, consent flags, and internal flags in conditions.
Read more⌄
Lead categorization vs. Resource tags vs. User tags
- Lead dropdown / constrained fields - categorize leads via Rules options or Selects lists. Used in conditions, automations, filters, and reporting.
- Resource tags - classify resources (technicians, teams, vehicles). Control which resources a booking form may use.
- User tags - group users for access control and permissions. Can link to resource tags for assignment eligibility.
Field naming best practices
- Use clear, descriptive names - not cryptic codes
- Keep API slugs stable once used in automations or API integrations
- Group related fields with consistent prefixes when helpful
- Prefer constrained options (Rules / Selects) over free text for categorization
- Only create fields for actual process needs
Common searches
custom fields Hubhus • field types • Default field • field rules • dropdown • no select type • resource tags • data field
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