dropdown JSON example

n8n dynamic dropdown JSON example

Example JSON responses for an n8n webhook that populates a FormNode dynamic dropdown or cascading field.

Direct answer

An n8n dynamic dropdown webhook should return JSON options with stable values and readable labels. The value should usually be the ID n8n needs later, while the label should help the user choose the right option.

Example options response
{
  "options": [
    {
      "value": "tenant_acme",
      "label": "Acme Manufacturing",
      "meta": {
        "connectwiseCompanyId": "250",
        "status": "active"
      }
    },
    {
      "value": "tenant_northwind",
      "label": "Northwind Traders",
      "meta": {
        "connectwiseCompanyId": "318",
        "status": "active"
      }
    }
  ]
}
Notes
  • Keep the dropdown webhook read-only. It should list options, not mutate users, tickets, licenses, or devices.
  • For cascading fields, include the parent field value in the request and filter the returned options server-side.
  • Return an empty options array when no choices are available instead of returning an ambiguous error shape.
  • Use labels for humans and values for workflow actions.
Common questions

What JSON should n8n return for a dynamic dropdown?

Return an array of options or an object containing an options array. Each option should have a stable value and a readable label.

Can dropdown options include extra metadata?

Yes. Metadata is useful for debugging or later workflow steps, but n8n should still treat the stable value as the primary selected identifier.

Related pages