Citrus America: HubSpot MQL→SQL Automation Review (2026-01-29)

Reviewed during ^[1]. Ben identified a logic error in the cloned MQL→SQL automation workflow that was preventing leads from qualifying correctly.

Problem

The MQL-to-SQL automation trigger was configured with is equal to all of on fields that are functionally single-select (e.g., budget range). This logic requires a contact record to match all listed values simultaneously — an impossible condition for a single-select field where a user can only choose one option.

As a result, no leads were advancing from MQL to SQL through this automation.

Root Cause

The underlying HubSpot fields were set up as multi-checkbox fields rather than single-select (radio button) fields. This allowed the all of operator to be applied, even though the intent was always to match a single qualifying value.

Resolution

Immediate fix: Change the trigger operator from is equal to all of to is equal to for each affected single-select field. This allows a lead to qualify when any one correct option is selected.

Follow-up improvement: Convert the affected fields to single-select radio button fields in HubSpot. This enforces the one-answer constraint at the data-entry level and prevents the all of logic error from recurring.

Action Items

[ ] Update Citrus HubSpot MQL→SQL automation: change trigger logic from is equal to all of to is equal to for all single-select fields (@Ben San Fratello)
[ ] Reconfigure affected HubSpot fields as single-select radio buttons to prevent multi-selection (@Ben San Fratello)
[ ] Coordinate with Miriam to confirm qualifying criteria per field before finalizing logic (@Ben San Fratello)

Context

Ben noted this automation is not currently blocking Citrus's sales process — they are focused on event prep at the moment. Work is ongoing in coordination with Miriam. The automation was originally cloned from an existing MQL workflow and adapted for SQL qualification.

^[2]
^[3]