I’m developing a public HubSpot application for a client using UI Extensions (version 2025.1 - legacy). I’m encountering an issue with the support email configuration.
Context:
The application is public and intended for the marketplace
I want to configure my client’s support email address
In the “Support Details” interface, the “Support Email” field is read-only
On hover, a tooltip says: “Cannot modify this application here. This application was created by the connect project (build #40). To make changes, update the public-app.json configuration file locally, then redeploy the project.”
What I’ve tried:
I added the support email address to my project’s public-app.json file
After deployment, the email address appeared correctly in the application settings page
I had actually succeeded in making the email address appear in the past, but I don’t remember how I wrote it in the public-app.json to make it work
BUT: when a user clicks the “Contact Connect” button in my UI Extension (card provided by a third-party application), the page simply reloads without doing anything - no email is sent, no form opens
My question:
How do I properly configure the support email in the public-app.json file so that the “Contact support” link from UI Extensions actually works?
What is the correct syntax/structure in the JSON file? I managed to make the email display once, but can’t remember the exact format I used.
Has anyone encountered this issue with Legacy UI Extensions? Is there a specific configuration or particular field to add in the JSON?
Hi @EDoyen,
Thank you for posting to the Community!
I understand that you’re looking for the correct syntax or structure to configure the support email in your public-app.json file so that the “Contact support” link in your Legacy UI Extension works properly, although the email displays correctly after deployment, clicking the “Contact Connect” button currently does not trigger any email action or form.
I’d like to tag in some of our Top Contributors to see if they can reproduce this -- Hi @mangelet@Bortami and @Gonzalo Have any of you all experienced this before? If so, how did you resolve?
Thank you!
Cassie, Community Manager
Update: Issue persists after upgrading to UI Extensions 2025.2
Following up on this issue - I’ve since upgraded the application from Legacy UI Extensions 2025.1 to 2025.2, hoping it might resolve the support contact link problem.
Unfortunately, the issue remains unchanged:
The support email still displays correctly in the application settings
However, when clicking the “Contact Connect” button, nothing happens - the page simply reloads
When I hover over or inspect the link element, I can see it’s targeting the current page instead of opening an email client or contact form
I’m attaching a screenshot showing the link behavior when inspected.
Has this been resolved in version 2025.2 for anyone else? Or is there a specific configuration change required when migrating from 2025.1 to 2025.2 for the support contact
functionality to work properly?
Any help would be greatly appreciated as we still have a client waiting for this functionality.
I figured out what was happening. It turns out the supportEmail parameter is most likely only used to display an email on the app’s listing page in the marketplace.
The parameter that actually controls the “Contact [App Name]” link is supportUrl, which is located just below supportEmail in the configuration. This parameter sets the URL that the link points to. So the link isn’t meant to trigger a mailto: action—it simply redirects to whatever support URL you’ve configured.
Hope this helps anyone else who was confused by this!
Thank you @EDoyen for sharing this helpful info!
Your clarity will definitely help others who run into the same issue.
Really appreciate you contributing to the community!
Bérangère
