Have the ability to add custom IDs to fields in the n8n built-in form and use those for reference down the line, instead of the auto-generated names that are based on the labels.
Form labels are user-facing, and as such are often not that great for code reference.
Additionally, and more critically, it looks like non-English labels are not supported properly. I have a form in Hebrew, with a file upload field called “קבצים לתרגום” (“Files to translate”). This is how the auto generated name appears for the uploaded files in n8n:
I think it would be beneficial to add this because:
Hi,
I second your request, but also have a workaround trick:
Label your inputs in English.
Insert Custom HTML fields in-between inputs and put Hebrew user-facing field labels into the HTML field.
Add a Custom Form Styling option and add the following rule there:
.form-group .form-label {
display: none;
}
This will hide ALL the English field labels and only leave the Custom HTML fields visible.
This workaround also provides an opportunity to use adequate field names in any form, e.g. user_file instead of Upload file here (less maintenance when user-facing labels change).
Google’s AI search overview incorrectly suggests that fieldName can be used (when defining fields in JSON), but in fact it triggers a “field not valid” error.
I wonder if there was a regression at some point.
I’d very much like prefer to have a custom field name option to the workaround above, of course.
Already used a custom HTML to add a “label” to that field. Didn’t bother with hiding the English for now, as it’s just an internal “quick-and-dirty” solution flow. Hopefully the next time the need arises the forms will already have custom IDs
I need this a lot! Have to create forms with multiple languages and since the question determines the key in the node’s output json it’s always different and suuuper hard to handle.
