Customization | Entry 16
CRM cards are custom interfaces inside HubSpot that display record-specific information or let staff take action without leaving the record they are viewing. HubSpot now generally calls these integration-based experiences app cards. A well-designed app card can guide a nonprofit process, update CRM records, or securely exchange selected information with a connected system.
Depending on its design and supported location, an app card can turn a CRM record into a practical workspace. Staff may be able to:
App cards can be supplied by a Marketplace app, a private app built for one organization, or an internal integration connecting HubSpot with another nonprofit system.
Standard HubSpot cards use functionality already available in the platform. These can include property lists, data highlights, association tables, reports, activity summaries, stage trackers, and quick actions.
An app card is supplied by an installed or custom-built application. It can collect input, validate that input, call an external service, coordinate changes across several records, and return a useful result to the user.
A standard association table might show a contact's memberships. An app card could guide a staff member through creating a membership, connecting it to the correct person and household, applying the right labels, and starting the renewal process.
A supporter mails in a paper membership form. Instead of creating and connecting each record manually, staff open a guided card on the contact record.
A volunteer coordinator can request a screening from the applicant's record, then see its operational status in HubSpot.
Add a guided process that HubSpot does not provide in the exact form the nonprofit needs, such as creating a household membership, assigning a volunteer, or validating a complex record before submission.
Display useful details from a connected platform, such as training completion, event check-in, accounting payment status, sponsorship benefits, or program eligibility.
Use approved HubSpot information to initiate an action elsewhere, such as requesting a background check, registering a volunteer for training, or starting an electronic-signature process.
A single card may combine all three functions. That does not mean the outside platform's complete interface is embedded in HubSpot. The exact experience depends on HubSpot's supported components and the provider's APIs, authentication, and security rules.
An app card is the staff-facing interface for a larger technical process. The complete solution may require a HubSpot app, UI extensions, APIs, serverless or external services, authentication, permissions, validation, duplicate prevention, workflows, error handling, logging, and monitoring.
The process also needs clear business rules. For a membership, the application must know which object to use, which fields are required, how households are identified, which labels to apply, how duplicate memberships are handled, and what should happen if only part of the process succeeds.
Start with the outcome a staff member should be able to complete from the record, not the amount of data that can fit on a card. A useful app card should make the following clear:
Validation should happen before a consequential action. Error messages should explain the specific issue and the next step. If a multi-step process only partially succeeds, the card should show what completed, what failed, and whether staff can retry safely.
Some app-card processes involve sensitive or regulated data. A background-check card does not mean a detailed screening report should be copied into HubSpot or shown to every user. The nonprofit should define:
Exchange only the information required for the approved process. In many cases, HubSpot needs an operational status, not a complete external report.
No. First determine whether a property list, association table, report card, record-creation form, workflow, playbook, quick action, existing connected-app card, or better record customization can solve the need.
Custom development is most valuable when it meaningfully simplifies a complex or cross-system process. An unnecessary card can add development cost, maintenance, security risk, slow record pages, and create another experience staff must learn.
The exact experience depends on the nonprofit's HubSpot subscription, app type, card location, object and record layout, installed apps, developer resources, external APIs, authentication, permissions, data sensitivity, and ongoing support capacity.
Before promising an app card, confirm:
HubSpot's app-card framework continues to evolve. Supported locations, components, app-object features, migration guidance, and developer limits should be verified during implementation.