Skip to content

SDK Reference

The AI agent generates code using the HubSpot UI Extension SDK. This reference covers the key components, hooks, and patterns available. You do not need to know these details to use Palpaca — the agent handles the code — but understanding them helps you write better prompts and review generated output.

The SDK provides 40 components organized into eight categories:

CategoryExamplesUse Case
LayoutFlex, Box, Tile, DividerStructure and spacing
NavigationLink, Button, StepIndicatorUser actions and navigation
Data DisplayText, Tag, Badge, DescriptionList, TableShowing information
InputsInput, Select, DateInput, Toggle, NumberInputCollecting user input
FeedbackAlert, LoadingSpinner, EmptyState, ProgressBarStatus and feedback
OverlaysModal, Panel, TooltipLayered content
ChartsBarChart, LineChart, DonutChartData visualization
CRMCrmAssociationTable, CrmActionButton, CrmStageTrackerHubSpot-specific widgets

Browse the full list in the Gallery tab in the top bar.

Fetches properties from the current CRM record.

hubspot.fetchCrmObjectProperties(objectType, properties)

Returns the requested property values for the record the card is displayed on.

Calls a serverless function to perform backend operations like creating records, updating data, or calling external APIs.

Opens a modal iframe within HubSpot for more complex interactions.

Displays a notification toast to the user with success, warning, or error messages.

Cards can respond to user interactions through standard event handlers on SDK components:

  • onClick — button clicks and tappable elements
  • onChange — input value changes
  • onSubmit — form submissions

The agent generates these handlers automatically based on your prompt descriptions.

SDK components follow the HubSpot design system. You can customize appearance through:

  • Variant props — many components accept a variant prop for different visual styles
  • Flex and Box — layout components for controlling spacing, alignment, and direction
  • Inline styles — for fine-grained control when component props are not enough

The agent uses these patterns to match the look and feel you describe in your prompts.