Refresh time depends on how much data is in your data source and how HubSpot’s API responds at the moment. The connector never caches HubSpot data — every refresh re-queries HubSpot — so the speed you see is dominated by the size of the query and HubSpot’s API throughput.
Large datasets (many objects, many properties, or many records) take longer to refresh. This is especially noticeable if:
- You include multiple objects in one data source.
- You don’t apply filters and refresh the whole table every time.
- You schedule refreshes too frequently and they overlap.
- The HubSpot account is close to its per-portal API rate limit or daily request cap.
To improve performance, you can:
- Reduce the amount of data — add filters on each object so the refresh only pulls the rows you actually report on. See Filter Rows.
- Split a large data source into smaller, focused ones rather than one wide data source covering many objects.
- Adjust the refresh schedule in Power BI Service so two refreshes don’t overlap or fight HubSpot’s rate limits at the same time of day.
- Set up incremental refresh in Power BI so only the most recently changed records are pulled on each refresh — see Set Up Incremental Refresh in Power BI.
If refreshes start failing outright (rather than just running slowly), the cause is usually that HubSpot’s API rate limits have been exceeded. See Why are HubSpot API limits showing up in my refresh errors?
