Input Types
Last updated
Last updated
Copyright © 2023 configure8, Inc. All rights reserved.
Actions have a section called user inputs to define the form elements you want to be filled when actions are run.
User inputs allow you to create a form with the configuration you define as JSON. In this configuration step, Configure8 provides a flexible range of usage.
In this section, you can use pre-defined input types like Email, URL, Datepicker, and Number inputs, select items from catalog using item selector, create dynamic inputs by defining conditions, or use specific catalog data in your form with the dynamic fields feature.
Field | Description | Notes |
---|---|---|
type | Required. Type of string | Supported types : |
title | Required. Human-readable title for the input parameter |
|
payloadName | Required. Unique input parameter identifier | Duplicates are not acceptable |
defaultValue | Optional. Human-readable example of the input parameter |
|
helpText | Optional. Human-readable description for the input parameter |
|
required | Optional. Boolean value. | All fields are assumed to be optional by default. To make an input mandatory, you can set |
condition | Optional. Array of condition object or condition object. | You can find detailed information and usage examples about conditions on the Dynamic user inputs page. |
options | Optional. Array of option objects. It is used to allow selection from a predefined list in | The 'option' object should consist of 'value' and 'label' fields. Example:
|
dataset | Optional. | The |
multiple | Optional. Boolean value. | The |
filter | Optional. Array of filter object or filter group with | The |
sensitive | Optional. Boolean value. | Hide injectable value in the input and obfuscate it in the action result's logs. See examples |
Read more about the supported user input types and their configurations: