Sai Saran Kalugutla
04/29/2026, 4:01 PMkapa.ai
04/29/2026, 4:01 PMproperties object in the synced records. [Contacts List]
⢠The connector also creates top-level flattened columns prefixed with properties_ for each property name. For example, a property named hs_time_in_prospect would also appear as properties_hs_time_in_prospect at the top level. [source-hubspot components]
So for your custom properties, the column names in the destination table would likely follow this pattern:
⢠properties_cb_-_hcs_profile_status (or similar, depending on how HubSpot's internal API name is defined)
Important caveat: The actual column name depends on the internal API name of the property in HubSpot (not the display label shown in the UI). For example, "CB - HCS Profile Status" in the UI might have an internal API name like cb_hcs_profile_status or something entirely different assigned when the property was created.
To find the exact column names, I'd recommend:
1. Checking the HubSpot property settings to find the internal field name/API name for each property.
2. That internal name, prefixed with properties_, will typically be the column name in your destination table.
The knowledge sources do not provide a definitive mapping for these specific custom properties. š 0 button š 0 button ā¹ļø Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.Sai Saran Kalugutla
04/29/2026, 4:02 PMSai Saran Kalugutla
04/29/2026, 4:04 PMkapa.ai
04/29/2026, 4:04 PMdataSensitivity). If your "CB - HCS/HCW/LTC/SL Profile Status" properties are flagged as sensitive in HubSpot, they would be excluded from the sync. [fix source-hubspot]
2. Property chunking limits: The connector uses character-based property chunking with a 15,000 character limit per request. If the total length of all property names exceeds this limit across chunks, some properties could potentially be missed. [property chunking]
3. Schema discovery: The connector dynamically discovers properties via the HubSpot properties API. If the properties were created after the last schema refresh, they may not yet be reflected.
Recommended next steps:
⢠Check in HubSpot whether these properties have "Sensitive data" enabled ā if so, they will be excluded by design.
⢠Verify the internal API name of these properties in HubSpot's property settings (not the display label), as that determines the column name.
⢠Try refreshing the connection schema in Airbyte to pick up any newly discovered properties.
The knowledge sources do not provide more specific troubleshooting guidance for this scenario. š 0 button š 0 button ā¹ļø Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.Sai Saran Kalugutla
04/29/2026, 4:14 PMkapa.ai
04/29/2026, 4:14 PMdataSensitivity: "high") is only available on HubSpot Enterprise plans (Marketing Hub Enterprise, Sales Hub Enterprise, Service Hub Enterprise, etc.). [fix source-hubspot]
⢠The Airbyte HubSpot connector's v3 properties API (/crm/v3/properties/{entity}) excludes sensitive properties by default, which is why they won't appear in the sync. [fix source-hubspot]
For checking whether a property is marked as sensitive, I'd recommend consulting HubSpot's own documentation or support, as the knowledge sources here don't cover the HubSpot UI navigation steps for this. Generally, you would look at the property settings in HubSpot under Settings ā Properties, find the specific property, and check if the "Sensitive data" option is enabled.
Alternatively, you can use the HubSpot v2 properties API (/properties/v2/{entity}/properties) to inspect the dataSensitivity field for each property ā if it returns "high", the property is flagged as sensitive and will be excluded from Airbyte syncs. The v3 API (/crm/v3/properties/{entity}) used by Airbyte simply omits those properties entirely. [fix source-hubspot] š 0 button š 0 button ā¹ļø Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.