Hi @MaxTarq , the API behavior you’re seeing is normal today.
HubSpot only exposes email-based subscription preferences through the public endpoint, so even if your account has WhatsApp or other custom channels configured, those live purely in the UI and aren’t returned by the Subscription Preferences API. That’s why you can query channel=EMAIL but nothing else.
(Accounts Dashboard | HubSpot )
For your follow-up question, communication preference changes also don’t fire workflow enrollment. There’s no native trigger tied to “subscribed/unsubscribed” for non-email channels, and they’re not available as webhook events either
When teams need automation around those custom channels, the workaround is to mirror each channel’s opt-in into its own contact property and maintain it through a small internal flow. Once the property changes, you have a stable trigger for downstream actions without depending on unsupported channel events. If these opt-ins also need to stay synchronized with an external messaging system, Stacksync keeps those consent fields aligned in real time so your workflows act on clean, consistent data.