How to build an n8n dynamic dropdown form
Build an n8n dynamic dropdown form with FormNode, where dropdown options come from an n8n webhook and the final structured payload returns to n8n.
To build an n8n dynamic dropdown form, create a FormNode dropdown, enable dynamic data, point it at an n8n webhook that returns options, test the parsed response, then send the completed form submission to a second n8n workflow for fulfillment. This pattern is the practical path when you need a form builder for n8n with live dropdown options instead of static form choices.
Build it in the right order.
Create the FormNode dropdown
Add a dropdown field to the form and enable Dynamic data in the field settings.
Create the n8n options webhook
Build an n8n webhook workflow that returns JSON options with value and label fields.
Connect the field to n8n
Paste the n8n webhook URL into the dropdown's dynamic data configuration and choose the request method.
Test the response
Use the FormNode test action to verify the webhook response parses into visible dropdown options.
Submit to fulfillment
Point the form's submission webhook at the n8n workflow that creates tickets, provisions users, or runs the target automation.
- Return stable IDs as values and human-readable names as labels.
- Include the selected organization or customer in child dropdown calls.
- Cache slow source-system lookups in n8n when options do not change often.
- Keep the options webhook separate from the final submission workflow.
- Keep option-loading webhooks read-only; do not mutate tickets, users, licenses, or assets from a dropdown request.
Can FormNode use n8n for dropdown options?
Yes. FormNode can call an n8n webhook while a user fills out the form and use the response to populate dropdown options.
Should the options webhook and submission webhook be the same n8n workflow?
Usually no. Keep option-loading workflows fast and read-only, then use a separate submission workflow for fulfillment.
What should an n8n dropdown webhook return?
Return stable values for automation and readable labels for humans. The value should usually be the source-system ID that the final n8n workflow needs.