HubSpot custom app cards

I build HubSpot app cards that bring relevant information onto the record, with clear status labels and an explicit data-access design.

My renewal-status card reads the linked License and displays its status on a deal. The card is read-only, with its function hosted in HubSpot for that implementation. See the renewal-status card case.

What the card includes

I start with the question someone needs to answer on a record. The work includes:

Design: record location, data sources and status labels with colour rules.
Access: associated objects and scopes, with explicit handling for missing records.
Build: a React UI Extension and appropriate data-fetching route, tested in a development or sandbox environment.
Rollout: verify the card on live records and document the visibility rules and change process.

Testing and maintenance

I test the status logic and the paths for missing or unavailable data. Written labels explain each status alongside its colour.

Documentation covers the sources, permissions and maintenance owner, including how changes to fields or associations affect the card.

Hosting and access

Data access and hosting depend on the subscription and platform version. Some integrations use an external backend, with its own costs and maintenance.

On platform 2026.03, private app functions need an Enterprise subscription or a free developer test account. I confirm scopes and runtime limits, and agree whether the card reads data or can write changes.

More about my approach

Questions about this area of HubSpot? Get in touch.