Custom Workflow Actions - Hidden/Dynamic Input Fields

Developer Support APIs & Integrations
1

I’m having an issue with the Custom Workflow Actions API. I’ve read the documentation front to back like 10 times but its lacking on explaining different InputField and InputFieldDependcy possibility which we’re trying to get working for our app use case.

We’re trying to extend the criteria in the contact based actions to target associated objects. It looks very similar to how HubSpot has its “Set property Value” action but a little more in depth. So what I’m trying to do it when the user selects the associated object they want to target I then load that objects properties and after they select the property I’d like to load the corresponding fieldType for them to select the new value but the issue is I’m not sure if I can then hide other inputFields (corresponding to other fieldTypes), they are just grayed out (which makes for a whole mess of inputFields).

I see HubSpot has some sort of logic built in into the workflows where inputFields are hidden until the dependant inputFields are build but in the custom workflow actions API it just grays them out and there is nothing in the documentation about this.A possible solution would either be to enable dynamic inputFields such as this

 {
 "typeDefinition": {
 "name": "newValue",
 "type": {{ dynamicType }}
 "fieldType": {{ dynamicFieldType }}
 "options": [],
 "optionsUrl": null,
 "referencedObjectType": null,
 "externalOptions": false,
 "externalOptionsReferenceType": null
 },
 "supportedValueTypes": [
 "STATIC_VALUE"
 ],
 "isRequired": true,
 "automationFieldType": null
 }

Or for me to be able to place all different fieldTypes into seperate inputFields but be able to hide them (not just gray them out=

Also there is next to no documentation available for “inputFieldDependencies” for some reason.
The final question would be if there is a way to hide not only gray out inputFields or if anyone has tried if making dynamic fieldTypes is possible?

2

Hey, @AnzeKoprivec :waving_hand: Thanks for your question.

It sounds like you’re looking for a more dynamic and flexible way to handle input fields in custom workflow actions than what’s currently available or documented. Unfortunately, if certain functionalities like dynamic field types or the ability to hide (not just gray out) input fields are not documented, it typically means these features are not supported in the current API version (including situations where you may find similar options available in-app).

Let’s invite some of our community members to the conversation — hey @Teun @MatthiasKunz @ChrisoKlepke, do you have any thoughts on other approaches @AnzeKoprivec might take?

Thank you for taking a look! — Jaycee

3

Hey @Jaycee_Lewis , this was our thought as well that these featues are most likely not available through the API.
Would there be a way for me to get this on HubSpots board somehow as I’m sure a lot of apps could take advatange of features like this

4

Hey, @AnzeKoprivec :waving_hand: Our best tool is to create an Ideas post. This is the most direct way we can get requests in front of the product team. Here’s a link — Ideas Community.

Best,

Jaycee