Stack Workflows / Pass Data
Being able to take a workflow, pull data and format it, then have that data (artifact) to be then sent to another agent that specializes in reporting. This would be instead of an agent, pulling the data, parsing and filter, then formatting the data into a report.
Log in to comment and vote
Comments1
Alex Bunyan
Apr 2
Problem:
Today, a single agent may need to handle the full chain of work: pulling data, parsing it, filtering it, transforming it, and then formatting it into a final report. This creates unnecessary complexity and makes workflows harder to maintain, reuse, and optimize.
Enable workflows to pass structured output or artifacts directly into downstream workflows or specialized agents.
This would support:
Passing parsed and transformed datasets from one workflow to another
Preserving structured data formats between workflow stages
Allowing downstream agents to consume prior outputs without redoing the same parsing or filtering work
Chaining specialized workflows together as part of a larger automation pipeline
Example Use Case
A workflow pulls raw operational data from multiple systems, filters and normalizes it, and produces a structured artifact. That artifact is then passed to a reporting-focused agent that specializes in generating summaries, dashboards, or customer-facing reports.
Without this capability, one agent must perform the entire sequence end to end:
Retrieve data
Parse and clean it
Filter and organize it
Format it into a report
With stacked workflows and artifact passing, responsibilities can be separated cleanly:
Workflow A: Data collection, parsing, filtering, transformation
Workflow B / Reporting Agent: Report generation, summarization, presentation