Composite (Workflow)

Overview

The Composite Tool enables you to create workflows by combining multiple tools, conditional logic, and data transformations into a single Agent-accessible tool. With this capability, Agents can execute complex, multi-step operations such as fetching, validating, and aggregating data seamlessly within one workflow.

Composite Tools support:

• Sequential or parallel tool execution.

• Conditional branching (if/else).

• Looping over collections.

• Logging (using probes) for visibility.

• Structured output definitions.

This makes the Composite Tool an orchestration layer that brings together various Dataworkz tools into cohesive workflows.

When to Use

Use the Composite Tool when you need to:

• Combine multiple tool calls into a single operation.

• Apply conditional checks or looping within a workflow.

• Aggregate outputs from different tools into a single structured response.

• Automate business processes that require multiple steps or validations.

Prerequisites

• Ensure that all underlying tools you plan to use (such as RAG Apps, REST APIs, or database tools) are already created and available in your workspace.

• Define the input parameters and output structures you want the composite workflow to support.

Set up

Creating a Composite Tool

To create a Composite Tool, go to Agents > Create Tool and select Composite from the tool options.

About Tool

Provide the basic information for the tool:

• Tool Name: A descriptive name for the composite workflow.

• Description: A clear explanation of what the workflow accomplishes.

Workflow

Define the workflow steps that make up the composite tool. These steps can be added/edited by clicking "View As JSON" option. Below is an example of the JSON.

This JSON structure can be edited to:

• Call other tools.

• Add probes to log data during execution.

• Apply conditional branching and loops.

• Transform intermediate results into final outputs.

Input Parameters

These parameters are the input to the composite workflow and can be alternatively defined in the JSON as well. Each parameter should include its type and description so the Agent can invoke the tool correctly.

Output

Define the structure of the final response returned by the workflow. Outputs are also expressed as a JSON schema and can include nested fields and metadata.

Configuration (Advanced)

Optionally, add key-value properties to customize tool behavior or provide reusable constants for workflow steps.

Validation

Use the Test Tool panel to provide values for input parameters and execute the workflow. Logs and probes can help verify intermediate steps. Ensure the output matches the defined schema before saving.