Structured and dynamic object inputs for custom connectors

Custom connector actions now support two new input types that let you represent complex data directly on the canvas - no code step required.

Structured object inputs group related sub-inputs into a single named object. For example, a "Mailing Address" input can expose individual street, city, state, and zip fields rather than forcing builders to construct the object manually. In your action's perform function, the value is a plain object accessible by field name (e.g. inputs.address.city).

Dynamic object inputs show a different set of sub-inputs depending on which record type or configuration the builder selects. For example, a "Create Record" action can present Account, Lead, or Contact input fields based on the builder's choice, with inputs.record.configuration identifying the selection and inputs.record.values holding the corresponding field values.

See structured object inputs and dynamic object inputs for usage and code examples.