Hi all,
I’m using the calling extensions sdk to build a new application for an integration between hubspot and my company. One question that I have is, is there a best practice or best place to put custom properties that pertain to that app install? This would be very helpful to store some application information on the hubspot instance.
I see we can create custom properties / objects, but if I just want one singular object to store all this but not have it affect other crm or other hubs, is there something that this would be best placed? I see apps are currently allowed to only have custom properties like dropdowns, and checkboxes,… but that doesn’t help in regards to saving properties that may be useful to connect hubspot and the application that is trying to integrate.
Hi @jrac
One strategy (that I think is underutilised) is to create an App Settings Page for your integration.
You would store the “custom properties” on your sever and users can change the settings themselves (if you want them to).
Have fun
Mike
Here to learn more about HubSpot and share my HubSpot Knowledge. I’m the founder of Webalite a Gold HubSpot Partner Agency based in Wellington, New Zealand and the founder of Portal-iQ the world’s first automated HubSpot Portal Audit that helps you work smarter with HubSpot.
Hi Mike,
I originally thought that was going to be my solution. However, I think the main crux of that problem is that the app settings page only has access to a few input types… None of which are useful, like a button/dropdown/etc… A simple text input unique to an application install would fix this issue. Wel.. that and having a configurable iframe url… none the less..
What I think is interesting is what you’re saying about storing the custom properties on my server… I think what I’m struggling with here is how exactly would hubspot know details of my backend server. The main things I’d want to store on hubspot would be server domain and details actually lol, so there would be a connection from hubspot to server. Am I missing some simple piece of auth here that solves this? What I’m using currently for the iframe for example is the backend server that my dev hubspot instance would want to be connected to. I’m looking for ways to abstract that out so that the iframe url can be more generalized since it looks like the iframe url is shared between all application installs. This would also apply to the oauth process in general since a redirect url needs to be registered.
Cheers and appreciate the help thus far,
James.
Hi @jrac
you can call an iframe on the button click on the App setting page and there you can create custom property and store value. Public app documentation will help you out. here is the link to how to do that -
Here is a link for your reference - Legacy public apps - HubSpot docs
I hope this will help you out. Please mark it as Solution Accepted and upvote to help another Community member.
Thanks!