A custom card is a small, purpose-built panel that lives directly on a Contact, Company, Deal, or custom object record. It can pull in data from anywhere, HubDB, an external system, a database you own, and it can let a rep take action without leaving the page. The teams that benefit most are the ones where reps are already switching tools to get the full picture on a record.
In This Article
What a custom card actually is
A custom card is a CRM UI Extension, a small React-based panel that HubSpot renders directly on a record's page, alongside the standard property panels and activity timeline. It isn't an iframe bolted onto the side of HubSpot. It's built with HubSpot's own component library, so it looks and feels like a native part of the record, not a plugin.
Behind that panel sits a serverless function you control. When the card loads, it can call out to HubDB, a database, or a third-party API, pull back exactly the data that record needs, and render it right there. Some cards are read-only, a quick reference panel. Others let the rep search, select, save, or trigger an action, all without a page reload.
The hidden cost custom cards remove
Most HubSpot portals accumulate the same problem over time: the CRM holds the relationship data, but some other system holds the operational data. A dealer network's inventory. A finance team's contract terms. A service team's asset history. None of that lives in HubSpot natively, so reps end up with a second monitor open, or a second browser tab, just to do their job on a single deal.
Every one of those tab-switches is small on its own. A few seconds to open the other tool, find the right record, read the number, switch back, type it in. But multiplied across every rep, every deal, every day, it adds up to real lost time, and worse, it adds up to typos and stale data, because manual copy-paste is where data quality problems start.
Three things a good custom card does
- Surfaces data that lives outside HubSpot. Inventory, asset history, account status in another system, anything the rep currently has to go look up somewhere else.
- Computes something HubSpot properties can't. A derived status, a match against another record, a calculation that depends on more context than a single property field.
- Lets the rep take action without leaving the record. Search, select, link, or save, right there, instead of opening another tab to do it and coming back to report the result manually.
A card that does none of these is usually just decoration. The strongest cards do at least one of the three well, and the best ones do all three.
A real pattern: matching a deal to its linked asset
One pattern that comes up often for businesses selling physical inventory, vehicles, vessels, equipment, is that the asset the deal is actually about lives as its own record, separate from the deal itself, exactly the kind of custom object worth building when a "thing" needs its own lifecycle. The rep working the deal needs to see and confirm which specific asset it's tied to, without leaving the deal record to go dig through another system.
A custom card built for this sits directly on the deal record. It searches the connected inventory source by identifier, shows the matching asset's key details right there, spec, status, current location, and lets the rep confirm or change the association with one click. The match logic underneath typically checks a primary identifier first, then falls back to a secondary one, so near-duplicate entries in the source data don't produce a wrong or missed match.
If your reps can describe, off the top of their head, the exact steps they take in another tool before they can finish updating a HubSpot record, that workflow is usually a strong candidate for a custom card.
When a custom card is worth building
Not every manual step needs a card. A custom card earns its place when the lookup happens often, when it happens on records reps are already viewing dozens of times a day, and when the data being surfaced is stable enough that a real-time card, rather than a periodic sync, is the right fit.
If the data only needs to be right once a day, a scheduled sync into a HubSpot property is usually simpler and cheaper to maintain than a card calling out live on every page load. Cards are the right tool when a rep needs to search, confirm, or act in the moment, not when the goal is just getting a number into a property field.
Map out exactly what the rep currently does in the other tool, step by step. A card that only shows data solves half the problem. A card that also lets the rep act, search, confirm, link, without leaving the record is the one that actually changes how the team works.