Skip to main content
Use Sample Inputs and Sample Tools when you want reusable test data and tool definitions inside Fetch Hive. These pages give your team a shared place to store example payloads and JSON tool schemas that can be reused while building and testing.

​
Overview

Both pages use the same general pattern: a searchable table with pagination, a Columns menu, and dialogs for creating, editing, and deleting entries. Use Sample Inputs for example request bodies, text payloads, or structured inputs you want to keep around for testing. Use Sample Tools for reusable tool schemas edited as JSON.

​
How do I manage sample inputs?

Open Tools in the sidebar, then click Sample Inputs. Use the search field to filter the table by name or description. Click Add Sample Input to create a new saved input. Enter the name, add an optional description, and paste the sample value you want to store. Save the input to add it to the table. To update or remove an entry later, open it from the table and use the edit or delete flow. You can also use sample inputs inline while testing prompts and workflows. Prompt variable fields, workflow run start inputs, and workflow start input example fields include actions to load an existing sample input or save the current value as a new sample input. For workflow Array start inputs and examples, saved sample input text must be a valid JSON array before it can be loaded into the field.

​
How do I manage sample tools?

Open Tools in the sidebar, then click Sample Tools. Use Add Sample Tool to create a new tool schema. Enter the name and optional description, then define the schema in the JSON editor. Save the tool when the JSON is valid. If the JSON is invalid, fix the error in the editor before you save. To update or remove an existing schema, open it from the table and use the edit or delete flow.

​
When should I use each?

Use Sample Inputs when you need reusable example data to run through prompts, workflows, or agents. Use Sample Tools when you need reusable JSON tool definitions your team can keep consistent across editor work. See also: Integrations, Media library, Prompts, Workflows, and Agents