Input

📸 Screenshots

Here are visual examples of this section:

Input - Worker Configuration Interface

1. Overview and Purpose

The Input worker serves as the entry point for workflows, defining the schema of incoming requests and providing input values to downstream workers. It automatically maps request parameters to output handles, making external data available throughout the workflow execution.

2. Configuration Parameters

This worker does not require any configuration parameters. It operates based on the handles defined in the workflow.

3. Input/Output Handles

• Output handles are dynamically created based on the workflow schema
• Each handle corresponds to a field in the incoming request
• Handle values are populated from the request input or mock data in debug mode

4. Usage Examples with Code

// The Input worker automatically receives request data
// and makes it available through its output handles
// No direct API calls needed - it's configured through the workflow schema

5. Integration Examples

The Input worker is typically the first worker in any workflow, providing the foundation for data flow to all subsequent processing workers.

6. Best Practices

• Define clear handle names that match your expected request parameters
• Provide mock data for handles when testing in debug mode
• Keep input schemas simple and well-documented for API consumers
• Use descriptive handle names that indicate the type of data expected

7. Troubleshooting Tips

• If handles are empty, verify that request parameter names match handle names exactly
• In debug mode, ensure mock values are provided for testing
• Check that the request data is being passed correctly to the workflow
• Verify handle configuration matches the expected input schema