# Workflow Custom Action inputFieldDependencies

**URL:** <https://community.hubspot.com/t/workflow-custom-action-inputfielddependencies/72442>\
**Category:** APIs & Integrations\
**Created:** [January 9, 2023, 8:12am UTC](https://community.hubspot.com/t/workflow-custom-action-inputfielddependencies/72442 "2023-01-09T08:12:48Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![messagedots](https://avatars.discourse-cdn.com/v4/letter/m/e79b87/32.png) [@messagedots](https://community.hubspot.com/u/messagedots)\
**Post date:** [January 9, 2023, 8:12am UTC](https://community.hubspot.com/t/workflow-custom-action-inputfielddependencies/72442/1 "2023-01-09T08:12:48Z")

</div>

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

```lia-code-sample
{
 "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?

---

<div class="post-metadata">

**Author:** ![Jaycee\_Lewis](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/jaycee_lewis/32/61352_2.png) [@Jaycee\_Lewis](https://community.hubspot.com/u/Jaycee_Lewis)\
**Post date:** [January 9, 2023, 11:35pm UTC](https://community.hubspot.com/t/workflow-custom-action-inputfielddependencies/72442/2 "2023-01-09T23:35:24Z")

</div>

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

Thank you! — Jaycee

---

<div class="post-metadata">

**Author:** ![messagedots](https://avatars.discourse-cdn.com/v4/letter/m/e79b87/32.png) [@messagedots](https://community.hubspot.com/u/messagedots)\
**Post date:** [January 18, 2023, 8:18am UTC](https://community.hubspot.com/t/workflow-custom-action-inputfielddependencies/72442/3 "2023-01-18T08:18:25Z")

</div>

@JBeatty @ChrisChiha can you help please?

---

<div class="post-metadata">

**Author:** ![NParra](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/nparra/32/79385_2.png) [@NParra](https://community.hubspot.com/u/NParra)\
**Post date:** [May 31, 2023, 7:59pm UTC](https://community.hubspot.com/t/workflow-custom-action-inputfielddependencies/72442/4 "2023-05-31T19:59:18Z")

</div>

@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](https://developers.hubspot.com/docs/api/automation/custom-workflow-actions)

If it works for you, tell me.

---

<div class="post-metadata">

**Author:** ![messagedots](https://avatars.discourse-cdn.com/v4/letter/m/e79b87/32.png) [@messagedots](https://community.hubspot.com/u/messagedots)\
**Post date:** [June 29, 2023, 12:47pm UTC](https://community.hubspot.com/t/workflow-custom-action-inputfielddependencies/72442/5 "2023-06-29T12:47:23Z")

</div>

I’ve already created action\_param\_1 and action\_param\_2 in inputFields. Unfortunately it doesn’t work

---

<div class="post-metadata">

**Author:** ![dcharwood26](https://avatars.discourse-cdn.com/v4/letter/d/ea666f/32.png) [@dcharwood26](https://community.hubspot.com/u/dcharwood26)\
**Post date:** [June 29, 2023, 4:23pm UTC](https://community.hubspot.com/t/workflow-custom-action-inputfielddependencies/72442/6 "2023-06-29T16:23:56Z")

</div>

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.