Dynamic dropdown forms powered by webhooks
Create forms whose dropdowns load live options from n8n, ConnectWise, CIPP, NinjaOne, HaloPSA, Hudu, ITGlue, or any API that returns JSON.
FormNode lets any select field load options from a webhook or REST endpoint in real time. That makes it useful for forms where the right answer depends on a customer, tenant, device, license, site, ticket, user, or other source-system record.
The form is part of the workflow, not just the front door.
- A customer selection should filter the next dropdown to that customer's sites, users, tickets, or assets.
- The options change often enough that static form choices become stale.
- The form should validate against a source system before submission.
- The workflow needs both the human-readable label and the source-system ID.
Customer-to-site cascading dropdown
A ticket intake form should let a requester pick a customer, then show only that customer's ConnectWise sites and contacts in the next fields.
The submission stores both the visible label and source-system IDs, so the workflow creates the ticket against the right company and site.
Why a workflow-first form layer matters
What is a dynamic dropdown form?
A dynamic dropdown form loads options from another system instead of hard-coding them in the form builder. In FormNode, those options can come from any webhook or REST endpoint that returns JSON.
What is an n8n dynamic dropdown form?
An n8n dynamic dropdown form is a form where dropdown options load from an n8n webhook while the user fills out the form. FormNode handles the field UI and parsing; n8n returns customer-specific options from the systems it can reach.
Can dynamic dropdowns cascade from one field to another?
Yes. FormNode supports cascading fields, so a selected customer can filter the next dropdown to only that customer's users, sites, devices, or tickets.