Dynamic input field descriptions

Questions
1 
	{
		displayName: 'Voice',
		description: 'Select the voice to use for the speech synthesis',
		name: 'voiceId',
		type: 'resourceLocator',
		default: { mode: 'list', value: null },
		required: true,
		modes: [
			{
				displayName: 'From list',
				name: 'list',
				type: 'list',
				typeOptions: {
					searchListMethod: 'getVoices',
					searchable: true,
				},
			},
			{
				displayName: 'ID',
				name: 'id',
				type: 'string',
				placeholder: 'en-US-natalie',
			},
		],
	},

	{
		displayName: 'Output Locale',
		name: 'multiNativeLocale',
		type: 'resourceLocator',
		default: { mode: 'list', value: '' },
		description:
			'Language for generated audio',
		modes: [
			{
				displayName: 'From list',
				name: 'list',
				type: 'list',
				typeOptions: {
					searchListMethod: 'getSupportedLocales',
					searchable: true,
				},
			},
			{
				displayName: 'Locale Code',
				name: 'id',
				type: 'string',
				placeholder: 'en-US',
			},
		],
	},
	{
		displayName: 'Voice Style',
		name: 'style',
		type: 'resourceLocator',
		default: { mode: 'list', value: '' },
		description: 'The voice style to be used for voiceover generation. Available styles depend on the selected voice and locale.',
		modes: [
			{
				displayName: 'From list',
				name: 'list',
				type: 'list',
				typeOptions: {
					searchListMethod: 'getAvailableStyles',
					searchable: true,
				},
			},

		],
	},

is it possible to reset the value of certain fields based on value of other fields

lets say in above description if voiceid changes then style and Output Locale should reset to empty can we have this kind of dynamic updation of input values

2

Ok, I will :rofl:

I mean… would you like to add more details or would it be more entertaining if we tried to guess what exactly you are doing and asking?

Thank you for putting details into your post.

when you say changes, what do you mean? changes where?

1 Like
3

in here if voiceid field value changes then style should be set back to empy if it has certain value before

image
image838Ă—644 26 KB

4

I am sorry, I still struggle to understand both what you are trying to achieve as well as which node is on the screenshot. If you think you have explained the issue clearly and provided enough details, maybe wait for somebody else to answer in this thread.

5

Hi so what i am trying to achieve is to create a custom node for n8n. As part of it i am trying to build a specific action in my node and above screenshot is part of that.What i was trying to achieve can one field be made dependent on other .Currently from the docs i can see we can hide one inpt based on another can we change value as well.

6

I don’t believe there are listeners to achieve this, the closest you can get to dynamically setting the value is probably with loadOptionsMethod.

7

i tried loadoptions its creating a connection to load one field based on other but on ui though it cant change i.e clear before selected value

8

Hi @Saketh_Repaka,

I also explored n8n’s current UI capabilities, and it seems you’re right — there’s no built-in mechanism to automatically reset the value of one field when another changes. As others mentioned, loadOptionsMethod lets you dynamically populate choices based on another field, but it doesn’t clear previously selected values. :contentReference[oaicite:1]{index=1}

Here are a couple of ideas you might consider:

  1. Use a dummy “reset” option — add an explicit option like “— Select —” in the style or locale field. If another field (e.g. voiceId) changes, manually check in code and programmatically set the dependent field back to that placeholder value.

  2. Custom UI workaround – although not trivial, you could try extending your node’s settings logic to detect value changes and force a UI refresh or force re-evaluation of dependent fields. This might involve digging into n8n’s frontend code or raising a feature request on repo if community support for dynamic value clearing is needed.

  3. Feature request – since this isn’t currently supported, consider posting a feature request on the n8n GitHub, explaining the use case (dependent fields and auto-reset behavior). If enough users support it, the team may consider adding the necessary listeners in future versions.

Hope this helps — I’d like this functionality too, especially when building complex dependent field UIs! Let me know if you figure out a workaround.