October brings us webhooks for private apps, multiple updates to the HubSpot CMS, and updates for UI Extensions using React.
Beginning October 31st, 2023, private apps will have support for webhook subscriptions. This is only supported for Private apps created via the private apps UI; apps created via a project do not currently support webhooks. See the developer documentation for more details and limitations.
Similar to webhooks for public apps, there is a maximum of 1000 subscriptions per app.
Read more about private app webhook support for private apps in our developer documentation.
We have updated our icon field to support Font Awesome version 6.4.2.
HubSpot users can now add a module to export or delete a contact's data on their customizable subscription page. Contacts can then directly request their data to be exported or deleted in addition to managing their preferences on the subscriptions page. Learn more about this module in your product updates area.
The content staging tool now lets you clone existing HubSpot-hosted pages, and publish them as brand new pages. Previously you needed to create new staged pages from scratch each time, slowing down the process by not being able to start from existing pages. Now you'll be able to more quickly create new pages as a clone from an existing page and publish them as brand new pages. This new third option will appear when clicking "Stage" in the content staging tool. When the page is published, it will publish as a new page instead of replacing the existing page.
See the documentation on staging for more details.
Updates for this version of the CLI include:
hs project devhs project upload will now log any files being ignored when run in debug modehs project create
We are excited to introduce a new beta feature in our CTA editor - the 'Embedded HTML' CTA type. This feature can be found under Advanced Options when you go to Marketing -> Lead Capture -> CTAs, click 'Create' and 'Start from scratch'.
With this new feature, you can now edit the link of your CTA text and add Custom CSS Classes and/or Custom CSS rules onto your CTA. This provides higher customization and flexibility, allowing you to create engaging, pixel-perfect CTAs for your websites and email.
Use Case:
This feature is handy for customers who need more flexibility and want to add custom CSS to their CTAs. This could be adding custom fonts, hover states, or easily matching the CTA with the website theme. Previously, this was impossible as the new CTAs are rendered inside an iFrame. With the introduction of the new, purely HTML CTA type, customers can now add their custom CSS, enhancing their ability to create personalized and engaging CTAs.
The latest public beta for UIE extensions has added new features and improvements. Users can now add custom cards to the right sidebar of the record page and enjoy better logs and error handling for local development. Additionally, a new footnote at the bottom-left corner displays the app's builder and a recent bug fix that made the local dev mode (hs project dev) portal-specific. See below for more information.
crm.record.sidebar as an eligible location property in your card's configuration file. See the example below:app.json file and informs the user about who built the app. We will continue to gather feedback from our customers and partners to improve this feature in the future further. See the example below.hs project dev) portal specific. This implies that the portal the user selects from the prompt when running hs project dev must match the portal navigated to in the browser; otherwise, the local dev connection will not work. This change addressed an issue reported by users regarding serverless functions encountering errors when run locally due to a mismatch in the portal ID. Users have two options to specify the account: either use the hs project dev --account command or run the command without the account flag, hs project dev. The latter option will launch an interactive prompt where users can select either the default account or one of the associated sandbox accounts. See the example below.
If you have any inquiries or concerns, please contact us via the Developer Slack channel, #crm-customization-beta.
When connecting a domain, CMS Hub Enterprise users will have an opportunity to indicate if they are setting up a reverse proxy connection. If they are setting up a reverse proxy connection and their connection is not set up correctly, we will inform the user with in-app messaging and insights into what they need to fix. This beta will be rolling out to portals through November. Read more about setting up a reverse proxy connection on our knowledgebase.
Questions or comments? Join us in the developer forums.