Workflow Custom Action inputFieldDependencies

Developer Support APIs & Integrations
1

Hi all, I am configuring a workflow action using inputFieldDependencies but I observe a weird behaviour. Here an example:

{
 "typeDefinition": {
 "name": "wa_template_params_number",
 "type": "option_1",
 "fieldType": "select",
 "options": [
 {
 "label": "0",
 "value": "0"
 },
 {
 "label": "1",
 "value": "1"
 },
 {
 "label": "2",
 "value": "2"
 }
 ]
 },
 "supportedValueTypes": [
 "STATIC_VALUE"
 ],
 "isRequired": true,
 "automationFieldType": null
}

"inputFieldDependencies": [
 {
 "dependencyType": "CONDITIONAL_SINGLE_FIELD",
 "controllingFieldName": "option_1",
 "controllingFieldValue": "1",
 "dependentFieldNames": ["action_param_1"]
 },
 {
 "dependencyType": "CONDITIONAL_SINGLE_FIELD",
 "controllingFieldName": "option_1",
 "controllingFieldValue": "2",
 "dependentFieldNames": ["action_param_1","action_param_2"]
 }
 ],

If I select “1”, I only see the action_param_1 option available (as it should be). If I select “2”, I would expect to see both action_param_1 and action_param_2 available but I only see action_param_2. . It seems like action_param_1 is overwritten by the previous condition… any ideas?

2

Hi, @messagedots :waving_hand: Thanks for reaching out! Hey, @JBeatty @ChrisChiha, do you have any experience here?

Thank you! — Jaycee

3

@JBeatty @ChrisChiha can you help please?

4

@messagedots

you need to create “action_param_1” and “action_param_2” fields inside of the

inputFields attribute in the JSON.

Look the example 3 here:

- Accounts Dashboard | HubSpot

If it works for you, tell me.

5

I’ve already created action_param_1 and action_param_2 in inputFields. Unfortunately it doesn’t work

6

hi @messagedots , you are right. i’m seeing exactly the same issue today.
perhaps it will help if i provide an example also:
creating a custom workflow action in JSON.
define 2 input fields.
one is an enumeration with the options “red”, “white” and “blue”.
the other is a booleancheckbox (it could be anything).
when “red” or “white” is selected, i want to see the checkbox.
when “blue” is selected, i do not.
when testing, we see that this works as expected for “red” and “blue”, but not “white”.
it seems to be exiting the logic at the earliest point…ie, i am NOT red, so i’m not showing it at all. rather than proceeding to the next dependency to check “white”.
shame the “controllingFieldValue” can’t handle an array or a wildcard.
not sure how to build complex actions going forward.