Palpaca Palpaca
Palpaca Palpaca
Back to Blog
Article

HubSpot CRM Cards: What They Are and Why They Matter

Arrigo Lupori
Arrigo Lupori
Founder of Palpaca · March 15, 2026

If you’ve spent any time inside HubSpot, you’ve seen CRM cards — those contextual panels that surface relevant data right where your team is already working. They might look simple, but they’re one of the most underutilized features in the HubSpot ecosystem.

Let’s break down what CRM cards are, why they’re worth your attention, and how modern tooling is making them far easier to build.

What are CRM cards?

CRM cards are custom UI components that appear in the middle column and sidebar of HubSpot record pages — contacts, companies, deals, tickets, and custom objects. They let you display data, trigger actions, and embed interactive workflows without leaving the CRM.

HubSpot offers two flavors:

  • Classic CRM cards — server-side rendered cards defined through app card configuration. They support basic layouts like titles, properties, actions, and links. Simple to set up, but limited in interactivity.
  • UI extension CRM cards — built with HubSpot’s React-based UI Extensions framework. These are full custom components that run inside an iframe on the record page, giving you access to the HubSpot SDK, custom styling, and rich interactivity.

The UI extension approach is where most of the momentum is today. It’s what HubSpot recommends for anything beyond basic data display, and it unlocks a much wider range of use cases.

Why CRM cards matter

At their core, CRM cards solve a simple problem: context switching kills productivity. Every time a rep leaves HubSpot to check another tool, they lose focus. CRM cards bring the data to the rep instead of sending the rep to the data.

Here’s why that matters in practice:

Faster deal cycles. Sales reps can see pricing calculators, contract status, or competitive intel directly on the deal record. No tab-hopping, no copy-pasting between systems. The information is right there when the conversation is happening.

Better customer service. Support agents can view order history, subscription details, or product usage metrics without logging into a separate dashboard. When a customer is on the line, every second counts.

Cleaner data entry. Instead of asking reps to fill out forms in a separate tool and hoping they remember, CRM cards can embed input forms right on the record page. Data gets captured in context, which means it actually gets captured.

Operational visibility. CRM cards can pull data from external APIs — ERPs, billing systems, project management tools — and display it alongside HubSpot data. This gives managers a unified view without building a separate reporting layer.

Workflow triggers. Interactive cards can kick off processes directly from the record page: approve a discount, escalate a ticket, send a Slack notification, or push data to an external system. One click instead of a multi-step workaround.

The build challenge

Despite these benefits, most HubSpot portals have few or no custom CRM cards. The reason is straightforward: building them requires development effort.

For classic cards, you need to stand up a server that responds to HubSpot’s data fetch requests and returns structured JSON. For UI extension cards, you need to write React components using HubSpot’s SDK, manage a local development environment, and deploy through the HubSpot CLI.

Neither path is prohibitively hard, but both require a developer who understands the HubSpot platform. For many teams — especially those without dedicated HubSpot developers — that’s a blocker. The card sits on a wishlist while the team keeps context-switching between tabs.

How AI tooling is changing the equation

This is where things get interesting. A new generation of AI-powered development tools is starting to lower the barrier for building CRM cards significantly.

Tools like Palpaca take an AI-agent approach to HubSpot development. Instead of writing React components from scratch, you describe what you want the card to do — “show the customer’s Stripe subscription status on the contact record” or “add a pricing calculator to the deal sidebar” — and an AI agent generates the component code, wires up the SDK calls, and handles the deployment configuration.

This matters for a few reasons:

  • Non-developers can participate. A RevOps lead or a solutions architect can describe a card’s purpose and get a working prototype without writing code. The gap between “I wish we had this” and “let’s try it” shrinks dramatically.
  • Iteration is faster. Changing a card’s layout, adding a field, or adjusting logic becomes a conversation rather than a code review cycle. You can explore ideas quickly and commit to the ones that stick.
  • Best practices come built-in. AI agents that understand HubSpot’s SDK can generate code that follows platform conventions — proper use of hubspot.fetch(), correct component patterns, appropriate error handling — without the developer needing to memorize the docs.

The result isn’t that developers become unnecessary. Complex integrations, performance optimization, and security reviews still need human expertise. But the 80% of CRM cards that are “show this data here” or “let me click a button to do this thing” — those become dramatically more accessible.

Where to start

If you’re considering CRM cards for your HubSpot portal, start with the pain points. Where does your team leave HubSpot most often? What data do they wish they could see on a record page? What manual steps could be replaced with a single button?

Those answers will point you toward your first card. And with AI-powered tools making the build process faster, there’s less reason to leave those ideas on the backlog.