Resolve a dropdown property's options

Fetches the legal values for a property the schema marks dynamic — the fields listed in dynamicFields on the action/trigger detail, i.e. those whose propertyType is DROPDOWN, MULTI_SELECT or DYNAMIC. Their values are NOT in the schema; this endpoint is the only way to learn them.

POST because the request carries the partially-filled configuration (values), the connectionId whose credentials the piece needs, and an optional searchQuery for pickers that filter server-side. Resolution runs on a worker (the API never decrypts credentials), except for the workspace pickers below.

THERE IS NO TRIGGERS/OPTIONS ROUTE. A dropdown that belongs to a TRIGGER must still be fetched through this actions path; the piece id and property name are what select the handler. The two workspace pickers served directly by the API — errortrigger/runfinishedtrigger with propertyName=watch_workflow (returns All workflows plus every workflow in the workspace) and subflow with propertyName=workflow_id (returns the workspace's workflows, callable ones first, each label stating its trigger and whether it is unpublished) — accept any actionId in the path.

A piece that declares no dynamic options answers 400 NOT_SUPPORTED.

Send Content-Type: application/json.

Requires workflow:read. Resolving a dynamic value is not a catalog read: it can return tenant data (the subflow piece's workflow_id option is this workspace's whole workflow list) and, when the request carries a connectionId, the credential is resolved and decrypted on a worker so the piece can call the third party.