App Actions UI Extensions

Some very interesting words together here. A few folks on the team are big fans of UI extensions, and the reason is that you can design a process to match whatever the team wants because you have done the work on the data model. With AI there is nothing too complex about curating data together so it is one button click, see exactly what you need to see. Unified customer view and unified revenue concepts come from seeing everything you need on a record view, on a CRM index page, or on a dashboard.

The hardest part has been doing all the work for a UI extension on the record view and then not being able to do anything on the index page. You sell the index page as easy as a spreadsheet, then people see what the extension can do on the record and ask whether they can have that over here, and the answer was not really. Now, the way this reads, we can: select records, trigger an action, and HubSpot renders your custom React component as a pop-up or panel with the selected record IDs in context. The sky is the limit. Sent straight to Ryan Ginsberg, and it sounds like a workshop topic.