It’d be nice to be able to present the user with a default value on a form.
I have a form with a date, but I want to put the next Sunday as the default value, as in my form this will almost always be the case.
I could work on it, but not sure that I’d have time to write tests, docs, release notes, …
This would be amazing,
I have buit the form for voice recognition using Whisper.
Most of the time I use the same settings, but occasionaly I need to change them, and therefore, currently, I had to fill the form every time with values that could be defaulted.
+1. A default value would be well appreciated even if it simply defaults to the first value in the list.
+1 Default value is very usefull
Yes. Default value is very usefull
Hey guys !
I made my way with a little workaround by editing the variables before processing it :
Hope It helps !
Can you give an example of how a workflow would look like ? I need something similar but can’t figure out how. Thanks
+1 need this
+1 - That would be amazing
There is a good workaround for now. You can use query parameters in the link you share the form with then that will prefill the form.
For example:
sub.n8n.cloud/form/my-form?name=Jane Doe
If the link gets too messy then use a short link like from bit.ly or short.io
Seems like this doesn’t work for all field types - text fields can be populated, but a dropdown list not
Hi. This works for initial forms. Nice. I think a lot of use cases need to add something like this for the “Next Form Page” node.
It should be easy to implement, since the “Hidden Field” has exactly that behavior: It has the property “Field Value“. This should be available for all input types.
INFO: I try to load values from an API, manipulate it via an N8N form and than save it in another API
FWIW, I’m using a radio button with a single choice ‘Yes’ (not a required field) followed by a Set node with `{{ $json.Delete ?? ‘No’ }}`
If the user skips that field, it is set to No otherwise it is set to Yes
+1 need this.
I would like to prefill some form fields with default values based on an HTTP request. The user should still have the option to manually adjust the values in the form or simply keep the values provided by the HTTP request and submit them as-is.
Hey all, just wanted to say ‘Thank you!’ for this feature request. We finally got to add this in n8n version 1.123.0. It works across all field types except Custom HTML, File, Hidden Field, and Password.
Beyond a standard form use case, this should also be valuable in Human-in-the-Loop scenarios, using the Custom Form response type (in the ‘Send message and wait for response’ actions across Slack, MS Teams, Email, and more).
Let us know what you think!
