I am creating a custom workflow action, My actions will have some input fields, one of those input field will be a dropdown of property list. Now in that field I need a list of all object(selected trigger) properties. Currently I am using "supportedValueTypes": ["OBJECT_PROPERTY"], but this field return me selected property value not the label. I need a selected label (Property name) name. Can you please help me on this?
As far as I'm aware, this is not currently possible. HubSpot will only ever supply your workflow endpoint (i.e. the workflow action's specified "actionUrl") the value(s) of the specified inputFields.
The only workaround I can think of is to require your app users to specify the relevant property label or internal property name themselves within a static inputField (rather than have them select a property from a dropdown list). This would require you to change your workflow action inputField to type "STATIC_VALUE" (rather than "OBJECT_PROPERTY"). I know this is not the user experience you were hoping to build, but I don't see any other option given your described use case.
I hope that proves useful. Please let me know if you have any follow-up questions.
All the best,
Zach
--
Zach Klein HubSpot Integrations & App Developer Meanjin / Brisbane, Australia
@zach_threadint I'm making same thing and I've used things as per your suggestion and it's worked for me. Do you've any idea about how to attach property options in the workflow action inputField.
As far as I'm aware, this is not currently possible. HubSpot will only ever supply your workflow endpoint (i.e. the workflow action's specified "actionUrl") the value(s) of the specified inputFields.
The only workaround I can think of is to require your app users to specify the relevant property label or internal property name themselves within a static inputField (rather than have them select a property from a dropdown list). This would require you to change your workflow action inputField to type "STATIC_VALUE" (rather than "OBJECT_PROPERTY"). I know this is not the user experience you were hoping to build, but I don't see any other option given your described use case.
I hope that proves useful. Please let me know if you have any follow-up questions.
All the best,
Zach
--
Zach Klein HubSpot Integrations & App Developer Meanjin / Brisbane, Australia