Skip to main content
input_schema.json is the “face” of a script. By modifying this file, you can control what parameters users need to fill in before running the script (such as URLs, keywords, dates, etc.), and how these inputs are presented (dropdowns, checkboxes, text fields, and more).

1. Overall Structure

A standard configuration file consists of the following three parts:
  1. description: Introduces the purpose and usage of the script to users.
  2. b (Concurrency Key Field): Determines how the script splits tasks.
  3. properties: The list of configurable parameters.

💡 Example

Image

2. Root Field Descriptions


3. Parameter Properties (Inside properties)

Each parameter item can include the following attributes:
  • title: Label shown on the UI (e.g., “Search Keywords”).
  • name: Internal identifier, must be unique and must not contain Chinese characters.
  • type: Data type:
    • string: Text
    • integer: Number
    • boolean: Boolean (true / false)
    • array: List / multiple values
    • object: Object
  • editor: Determines how the input is rendered in the UI (see below).
  • description: Helper text shown below the input field.
  • default: Default value shown initially.
  • required: If set to true, the script cannot run unless this field is filled.

4. Editor Type Guide

Choose different editors to optimize user experience.

4.1 Basic Text & Numbers


4.2 Selectors


4.3 Date & Special Lists


5. Common Component Examples

5.1 Single-line Input

Image

5.2 Multi-line Textarea

Image

5.3 Number Input

Image

5.4 Dropdown Select

Image

5.5 Radio Buttons

Image

5.6 Checkboxes

Image

5.7 Date Picker

Image
Image Image

5.8 Switch

Image

5.9 URL List (requestList)

Image

5.10 URL List Source (requestListSource)

Image

5.11 String List

24832302876 211201030865 Dfd4d22f2d116a1917d333058ccdc33d

💡 Configuration Tips

  1. Write clear descriptions A well-written description improves discoverability and usability.
  2. Provide sensible defaults Good defaults allow users to run the script with minimal effort.
  3. Enforce required fields For critical parameters (e.g., login cookies or start URLs), always set "required": true.