Since the form UI is rendered by n8n, injecting custom JavaScript to modify the message also isn’t supported. What I usually do in these cases is avoid relying on the built-in validation and instead handle the validation inside the workflow, where I can return a custom message in the desired language. If full localization is required, another option is using an external form and sending the data to n8n via a Webhook.
Hi @Uneerup Welcome!
On self hosted you can this work around where you set N8N_DEFAULT_LOCALE to your target language, also if the goal is to transform data you can do that after the form node using code node for more customization, as currently you cannot do much on n8n cloud. (Using custom webhooks and webpages with HTML node can work in this situation as @tamy.santos has suggested)
@Uneerup I’m really happy to hear this helped
If this solution solved the issue for you, please consider leaving a like or marking the reply as the solution ( it helps others find the answer more easily and also supports community contributors.)