Create the field

Go to Campaign settings → Fields → + New field. Enter: Field name (display label), API/slug name (auto-generated from name, editable — this is what you use in placeholders: {{slug}}), Description (optional internal note). Choose the field type. Save.

Choose the right field type

Text — general input (names, notes, IDs, addresses). Number — numeric values (price, quantity, measurements). Date — dates only (deadlines, visit dates, reminders). Select — predefined dropdown options for segmentation and workflow branching (see Select fields article). Checkbox/boolean — yes/no flags for conditional automations. Data field (JSON) — advanced structured storage for arrays/objects.

Configure required rules

Two levels: Field-level required — set directly on the field, prevents any lead creation without it (strict, use sparingly — can break API integrations and older forms). Form-level required — @input[field-slug; required] in a form, only enforced when the form is submitted (recommended for most cases). Hard-required fields can cause issues for external APIs, partners posting leads, and forms that don't include the field.

Use the field across the campaign

Once saved, the field is available in: forms (via @input[slug]), booking forms, webpages, email/SMS templates (via {{slug}} or %slug%), automations (as trigger condition or action), and filters. All users with campaign access can see all fields — field-level visibility restriction does not exist in Hubhus.