topic Re: Retrieving Data for CRM Cards in 2025.2 in APIs & Integrations

Retrieving Data for CRM Cards in 2025.2

DCozens — Tue, 23 Sep 2025 13:56:27 GMT

I've got some "legacy" CRM Cards that we use extensively. They broadly follow a pattern of:

Get object from context
Get schema to retrieve IDs for custom objects
Query associated object(s) and display data
Update associated object(s)

However, 2025.2 doesn't appear to be able to call serverless functions any more and I can't see how to create the same functionality without spinning up my own server somewhere and using hubspot.fetch()

And the documentation is fragmented, tends not to reference what version it applies to and is frequentally just plain wrong

Advice appreciated

Re: Retrieving Data for CRM Cards in 2025.2

BérangèreL — Wed, 24 Sep 2025 10:03:36 GMT

Hi @DCozens,

Thank you for bringing up this important question about CRM Cards in 2025.2 and sharing your experiences with legacy workflows on the HubSpot Community!

We appreciate your valuable feedback about the documentation, thank you.

If you can share details about where the documentation is incomplete or inaccurate (link to the documentation you used), please let us know.

This helps us fix issues faster for everyone and so that I can share your concerns with our documentation team so that we can continue improving clarity and accuracy for the developer community.

I’m also tagging some of our Developer Experts who may be able to weigh in with how they’ve handled similar migrations: Hi @sylvain_tirreau, @Anton and @zach_threadint do you have best practices to share with @DCozens, please?

Have a great day and thanks so much!
Bérangère

Re: Retrieving Data for CRM Cards in 2025.2

suprdense — Mon, 29 Sep 2025 08:14:25 GMT

Hey @DCozens ,

If your card is part of a private project, you don’t necessarily need to spin up a server. As long as your hsprojects.json is on a version that still supports serverless, you can call functions with hubspot.serverless() and run everything inside HubSpot using your private app token.

If it’s a public app, or your project or account doesn’t support serverless anymore, then you’ll need a small backend. The card hits it with hubspot.fetch(), the backend manages OAuth/refresh tokens, makes the HubSpot API calls, and sends back only what the card needs.

Here's a little check you can perform, try a simple serverless function from the card. If it works, keep it in HubSpot. If not, set up the backend route. Either way, make sure tokens are stored safely, scopes are correct, and add basic retry/caching for reliability.

I hope this provides the clarity you were looking for. If it resolves your question, kindly mark it as the accepted solution and upvote it to assist others in the community.