Response

📸 Screenshots

Here are visual examples of this section:

Response - Worker Configuration Interface

The Response worker serves as a schema for collecting and outputting workflow response data. It aggregates values from all connected handles and provides them as the final output of an agent workflow. This worker acts as the termination point for data flows in your AI agent pipelines.

2. Configuration Parameters

This worker does not require any configuration parameters. It automatically processes all connected input handles.

3. Input/Output Handles

Dynamic input handles: Accepts any number of input connections with custom names and data types
output: Output handle - returns an object containing all input values keyed by handle name

4. Usage Examples with Code

// The Response worker automatically collects all input values
// Example output structure based on connected handles:
{
  "textResult": "Generated text content",
  "imageUrl": "https://example.com/image.png",
  "metadata": { "timestamp": "2024-01-01T00:00:00Z" }
}

5. Integration Examples

The Response worker is typically placed at the end of agent workflows to collect final results from multiple processing branches and provide a structured output for external consumption.

6. Best Practices

Use descriptive names for input handles to create clear response schemas
Connect all relevant workflow outputs that should be included in the final response
Place the Response worker as the final step in your agent workflow
Consider the structure of your output object when designing upstream connections

7. Troubleshooting Tips

If expected data is missing from output, verify that input handles have active connections
Check that upstream workers are properly executing and providing values to their output handles
Ensure handle names are unique to avoid data conflicts in the response object
Review the agent execution flow if the Response worker is not receiving expected inputs