Dynamic dropdown form checklist
A checklist for dynamic dropdown and cascading field forms that load customer, site, user, asset, ticket, or license options from webhooks.
A dynamic dropdown form checklist should verify parent-child field order, read-only option webhooks, fast response times, stable option values, readable labels, empty-state behavior, caching strategy, and final payload mapping.
Verify these before publishing.
Start with the parent field
Customer, organization, tenant, or site should usually scope later dropdowns.
Return stable values
Option values should be durable IDs, not display labels that may change.
Return readable labels
Labels should help users choose correctly while values remain workflow-safe.
Keep option webhooks read-only
Dropdown loading should not create tickets, users, or other records.
Handle empty results
Give users a clear state when no sites, users, devices, or licenses are available.
Test parent changes
Changing a parent field should clear or reload dependent child choices.
Map labels and IDs in final payload
n8n should receive the selected ID and enough label context for debugging.
- The child dropdown keeps an old value after the parent changes.
- n8n receives only a label instead of a durable ID.
- A slow option webhook makes the form feel broken.
- An empty response looks like a failed request.
- A dropdown endpoint leaks options from another customer or tenant.
What should a dynamic dropdown webhook return?
Return JSON options with stable values and readable labels. The stable value should be the ID used by the downstream workflow.
How fast should a dropdown webhook be?
Fast enough that the form still feels responsive. Cache low-change data in the workflow or source system when live reads are slow.