As of yesterday afternoon, one of our Custom Cards tied to Custom Objects started failing. HubSpot support mentioned they hadn’t noticed any issues on their end. Anyone else?
I actually ran into something pretty similar yesterday with a custom card tied to our deals object. It suddenly started throwing errors out of the blue, even though nothing had changed on our side. HubSpot support told us the same thing (no issues on their end), but we did notice some odd behavior with API responses, fields coming back as null that used to have values.
Try re-publishing or redeploying your card (sometimes the connection just gets stale, and a fresh deploy helps). Double-check if any field mappings or property IDs on the custom object were changed or deleted accidentally.
If your card fetches data from HubSpot’s API, test the endpoint outside the card to see if the data structure has changed. HubSpot occasionally tweaks things, and that can break integrations even if support hasn’t flagged anything yet.
Also, sometimes browser caching causes issues with card rendering after backend updates, so clearing cache or using incognito mode might be worth a shot.
Initially, we thought it seems like a URL issue in the post request-
{“status”:“error”,“message”:“Unable to infer object type from: dials”)
And then we thought it could be related to the change HubSpot made with naming custom objects in request URLs without the ID - which happened in June - but ultimately was what we found to be the issue.
The change to the reference naming convention in API endpoints forced us to deploy a change that updated the endpoints to use “p_dials” instead of “dials,” for our custom objects properties.