Configuration
| Option | Required | Description |
|---|---|---|
| Name | No | Label for the step in the workflow canvas. |
| Schema Items | Yes | Rows in Schema Items. Each row has a Key and a Value / Description field. |
| Add this step from the Utilities group in Search steps…. |
{{step_2.output.items}} can produce an array that an Iteration step can use later. You can also build a JSON array literal from multiple array variables, such as [{{step_2.output.items}},{{step_3.output.items}}]; this creates an array of arrays, not a flattened concatenation.
Output
Click Run in the step header to test the step. Fetch Hive shows the generated result in Output after the run completes. Use the variable picker in a later step to insert the exact output path for your run. The base reference is:Example
Add JSON Schema from the Utilities group in Search steps…. Set Name to something likeArticle fields.
In Schema Items, add keys such as title, summary, and sentiment.
For each item, describe what the value should contain in Value / Description. If a field should depend on earlier workflow data, click Insert Variable and add that reference.
Click Run and review the structured result in Output before using those keys in later steps.
Notes
- The settings sheet lets you add and remove schema rows with Add Item and the delete action on each row.
- This step editor does not show a When the step fails control in its settings sheet.
- JSON Schema preserves resolved JSON arrays and objects for downstream steps, including Iteration. It does not currently merge two arrays into one flat array automatically.
- Use the variable picker after a test run if you want to confirm the exact keys available to later steps.

