Input Data in Agent Catalyst Workflows

Agent Catalyst workflows can leverage input data in two main ways to process and generate meaningful outputs:

1. Static Data: Predefined and embedded directly in the workflow.

2. User Input: Dynamically provided by the user at runtime.

Static Data

Static data is defined in the workflow’s frontmatter metadata using the data field. These values are accessible throughout the workflow during execution.

Example: Static Data

• Accessing Data: Reference static data fields like quote or langs using {} syntax, e.g., {quote} or {langs}.

• Complex Structures: Data can include simple strings, nested objects, or arrays.

User Input

User inputs allow workflows to be reusable by prompting for specific input values during execution. Inputs are defined using the input field in the frontmatter metadata.

Example: User Input

• Dynamic Prompts: The user is prompted to input a quote during execution.

• Reusability: The workflow adapts to different inputs without modification.

Input Types

Agent Catalyst supports diverse input types for flexible user interaction. Inputs are specified as key-value pairs under the input field.

1. Text Input

Prompts the user for a single-line or multi-line text.

Example:

2. Select Input

Prompts the user to choose from a list of options.

Example:

3. File Input

Prompts the user to upload a file or specify a file path.

Example:

4. Array Input

Prompts the user to enter multiple text values, which are returned as an array.

Example:

Variable Naming Rules

• Uniqueness: All variable names (from inputs or actions) must be unique within the workflow. Duplicate names will cause a compilation error.

• Nested Scopes: Variables can be reused within nested scopes (e.g., within <Loop /> or <Cond />).

Example of Block Scoping:

In this example:

• item and subitem are scoped to their respective loops.

• Parent variables must be explicitly passed using provide.