How do I manage SELECT fields and dropdown options?
SELECT fields are predefined dropdown lists that ensure consistent data entry and power filters, automations, conditional logic, and API integrations. They're one of the most important tools for structuring your campaigns.
TL;DR
Campaign Settings → Selects → New select field. Add options — each gets a label and a slug. The slug is used in @if logic, automations, filters, and API. Never change slugs once in use — it breaks logic. Each option can trigger actions (send email, set status, assign user) when selected.
Get started in 4 steps
Create: Campaign Settings → Selects → New select field. Give it a name (e.g. "Customer type") and add options. Each option gets a label (displayed to user) and an auto-generated slug (used in logic). The select field is now available in forms, booking forms, automations, filters, and templates.
Add/edit options: Campaign Settings → Selects → click the list → add options, edit labels, reorder. Do not change slugs unless absolutely necessary — slugs are referenced in automations, @if logic, filters, and API payloads. Changing a slug silently breaks existing logic.
Use in filters and logic
Lead table: select "Customer type = Commercial" from the filter bar.
Campaign filter: customer-type.slug = commercial
Automation/@if: @if(@select[customer-type,slug] == commercial){ ... }@endif
Trigger actions per option: click "Add action" next to any option to configure what happens when that value is selected — send email, send SMS, set status, assign user, submit HTTP request, etc. Actions fire immediately when the user picks that option.
Read more⌄
Conditional activation (requirements)
You can make a SELECT field conditionally active — it only appears when the lead meets certain criteria (status, origin, assigned user, email activity, etc.). Open the field → Edit requirements → "This field is conditionally active" → choose conditions → Save.
If requirements are not met: the field is inactive, cannot be changed, and its option-actions will not trigger.
Best practices
- Use select fields instead of free text for any categorization
- Keep slugs short and code-safe (no spaces, lowercase)
- Group related select lists logically: Sources, Regions, Visit types
- Never change slugs once used in automations, filters, or API integrations
- Use select-based automations instead of comparing text values
Common searches
select field • dropdown options • add select option • select slug • manage dropdown values
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