n8n dynamic dropdown form template
A field structure for n8n dynamic dropdown forms that need cascading customer, site, user, asset, ticket, or license options.
An n8n dynamic dropdown form template should separate read-only option webhooks from the final submission webhook. Parent fields such as customer or organization should feed child dropdowns such as site, contact, user, device, ticket, or license SKU.
Use this template when the form is part of an operational workflow.
- Forms where the available options depend on the selected customer or tenant.
- Workflows that need source-system IDs before fulfillment.
- Replacing stale static dropdowns with live n8n webhook lookups.
Typical systems this template may need to read before n8n fulfills the request:
Fields this form should include
Add approval only when the selected option creates risk, spend, privileged access, or customer-visible change.
Each dropdown webhook should be read-only, fast, and scoped by parent field values. The final submission webhook should be separate and idempotent.
Build the form first, then wire the workflow.
Choose the parent field
Start with customer, organization, tenant, or site.
Build read-only n8n webhooks
Return option JSON with stable values and readable labels.
Map child fields
Pass parent values into child dropdown calls for cascading behavior.
Submit the final payload
Send selected IDs, labels, and organization context to the fulfillment workflow.