A fix was deployed and all connections to Hubspot are working again. We have confirmed that customers are able to route and update Hubspot records properly.
It was noted that not all Hubspot CRM customers became impacted by this issue immediately. We began receiving reports as early as 3pm EDT(7pm UTC) and so you may see issues in routing for at least this amount of time. During that time, customers may not have been able to route / book a call.
If you find that your Chili Piper account is still not properly connected to Hubspot, or if you continue to experience issues with routing and are a Hubspot customer, please try browsing to your integration settings within the Chili Piper admin panel and reconnecting Hubspot.
The root cause appears to be related to a permission scope that Hubspot used to provide "as requested" now requires explicit permissions for it to work. Since we didn't authenticate this permission in the past, all authorizations were failing. We have deployed a fix which essentially removes the need for this scope.
Our team will explore if this scope is going to be needed in the future and will take appropriate measures if this is the case. We will also continue monitoring to ensure that all instances are back up and running properly with this provided hotfix.
We have had reports that Hubspot is no longer functional for all customers due to a new scope being requested on the authorization.
Our teams are investigating the source, but the issue has caused all Hubspot API connections to drop. This will cause issues routing with Concierge, or properly updating Hubspot records.
We are investigating a potential solution, or temporary workaround, that can be provided until we identify the root cause.
Posted Aug 19, 2025 - 21:49 UTC
This incident affected: Demand Conversion Platform (Fire) (ChiliCal, ChiliCal Scheduler (Handoff), Concierge Routing) and HubSpot CRM API.