Feature Request: Support multi-robot workflows with ordered execution
Summary
Enable the ability to chain multiple robots in a single workflow, allowing:
- Robot A: scrapes pages and extracts a list of links
- Robot B: takes output from Robot A, performs extractions, returns results
Execution should be sequential, as if running a single robot.
Use Case
Current limitation:
- Each robot is executed individually.
- To perform multi-step extraction, users need to orchestrate robots outside Maxun (custom scripts, microservices).
Desired behavior:
- Create a workflow containing multiple robots
- Define execution order
- Optionally pass outputs from one robot to the next
- Run the workflow as a single entity
Example:
Workflow: Products scraping
- Step 1: Robot A → scrape product pages, returns list of URLs
- Step 2: Robot B → extract specs from URLs returned by Robot A
- Step 3: Return combined JSON
Proposed Solution
- UI: allow users to create “workflow robots” that chain existing robots
- API: provide endpoint to define and run multi-robot workflows
- Ensure output of a robot can be passed as input to the next robot
- Optional parallel execution for independent robots (advanced)
Benefits
- Full orchestration inside Maxun
- Avoids external scripting for multi-step tasks
- Clean, modular, reusable robots
- Scalable workflows
Compatibility
- Backward compatible: existing single-robot executions remain unchanged.
Feature Request: Support multi-robot workflows with ordered execution
Summary
Enable the ability to chain multiple robots in a single workflow, allowing:
Execution should be sequential, as if running a single robot.
Use Case
Current limitation:
Desired behavior:
Example:
Proposed Solution
Benefits
Compatibility