---
title: 'Citrus HubSpot MQL→SQL Automation: Single-Select Field Logic'
type: article
created: '2026-01-29'
updated: '2026-01-29'
source_docs:
- raw/2026-01-29-weekly-call-w-ben-118278820.md
tags:
- hubspot
- automation
- citrus
- mql
- sql
- lead-qualification
layer: 2
client_source: null
industry_context: null
transferable: true
---

# Citrus HubSpot MQL→SQL Automation: Single-Select Field Logic

## Overview

The Citrus HubSpot workflow that promotes Marketing Qualified Leads (MQLs) to Sales Qualified Leads (SQLs) had a logic error in its trigger conditions. The automation was configured with `is equal to all of` on fields that are functionally single-select — meaning a lead would only qualify if a user checked *every* listed option simultaneously, which is both impossible in practice and contrary to the intended qualification logic.

This article documents the diagnosis, fix, and a recommended field-level improvement to prevent recurrence.

## The Problem

The MQL→SQL enrollment trigger used `is equal to all of` for fields like budget range. Because `all of` requires *every* listed value to be selected, no lead could ever satisfy the condition — a user filling out a form would only ever select one option (e.g., "$5,000–$10,000"), not all options at once.

**Root cause:** The trigger operator was set incorrectly for single-select field semantics. The `all of` operator is appropriate for multi-select fields where multiple values can be simultaneously true (e.g., a "features interested in" checkbox group). It is not appropriate for mutually exclusive options like budget tiers.

## The Fix

Change the trigger operator from `is equal to all of` → `is equal to` for any field where only one value can logically apply at a time.

This ensures the automation fires when a lead selects *the one correct qualifying option*, rather than requiring an impossible multi-selection.

**Steps:**
1. Open the MQL→SQL workflow in HubSpot.
2. Locate each enrollment trigger condition using `is equal to all of`.
3. For any field that represents a mutually exclusive choice (budget range, company size, service interest, etc.), change the operator to `is equal to`.
4. Confirm the qualifying value(s) match Miriam's SQL criteria from the qualification spreadsheet.
5. Save and re-activate the workflow.

## Recommended Field-Level Improvement

Beyond fixing the trigger logic, the underlying HubSpot form fields should be converted to **single-select radio buttons** (rather than checkbox groups) wherever only one answer is valid.

**Why this matters:**
- Prevents users from accidentally selecting multiple options.
- Makes the data cleaner and the automation logic unambiguous.
- A single-select field paired with `is equal to` is the correct pattern for mutually exclusive qualification criteria.

**How to configure in HubSpot:**
- Edit the contact/deal property.
- Change the field type from "Checkboxes" to "Radio select" (or "Dropdown select").
- This enforces one-selection-only at the form level.

> Note: This field-type change was flagged as a follow-up item during the 2026-01-29 call. As of that date, the immediate priority was correcting the trigger operator; the field-type update is a secondary improvement to coordinate with Miriam.

## Context

- **Client:** [[wiki/clients/citrus/_index|Citrus]]
- **Contact:** Miriam (Citrus internal stakeholder for HubSpot configuration)
- **Status as of 2026-01-29:** Automation logic fix assigned to Ben; field-type improvement pending coordination with Miriam. The broken automation was not actively blocking Citrus's sales process at the time of discovery.

## Related

- [[wiki/clients/citrus/_index|Citrus Client Overview]]
- [[wiki/knowledge/hubspot/|HubSpot Knowledge Base]]
- Source meeting: [[raw/2026-01-29-weekly-call-w-ben-118278820|Weekly Call w/ Ben — 2026-01-29]]