Question 1

Can Ana query HubSpot custom properties?

Accepted Answer

Yes. The HubSpot API connector exposes every standard and custom property on contacts, companies, deals, and custom objects. Ana can filter and aggregate by any property you have defined in HubSpot, and join those properties with warehouse dimensions during analysis.

Question 2

Does Ana respect HubSpot rate limits?

Accepted Answer

Yes. TextQL includes built-in rate limit handling for HubSpot's burst and daily quotas. Ana automatically backs off and retries when needed, and the connector caches frequently accessed entities within a session to minimize API usage without returning stale results.

Question 3

How are HubSpot tokens secured?

Accepted Answer

OAuth refresh tokens are encrypted at rest in the TextQL credential vault. When Ana makes an API request, tokens are injected at the network layer by our egress proxy. Ana's Python sandbox only sees a helper function — never the token value itself.

Question 4

Can I restrict which HubSpot scopes Ana uses?

Accepted Answer

Absolutely. During OAuth setup the admin selects only the scopes they want to grant. Read-only is the default. You can later re-authorize with broader scopes if you want Ana to write notes, update deal stages, or create tasks on your behalf.

Question 5

Is HubSpot data cached?

Accepted Answer

By default no — Ana fetches live data per question so answers always reflect the current CRM state. Optional short-lived session caching can be enabled to speed up multi-step analyses where the same objects are referenced repeatedly.