feat(workflow): Node-to-Node Data Flows#943
Open
baptmont wants to merge 2 commits into
Open
Conversation
baptmont
requested review from
hanorik and
wolo-lab
and removed request for
wolo-lab
wolo-lab
approved these changes
Jun 2, 2026
hanorik
approved these changes
Jun 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Overview
This Pull Request implements self healing Node-to-Node Data Flows
To support the complex runtime dynamics of declarative graphs, this PR introduces robust, self-healing data adapters across core workflow nodes (
ToolNode,FunctionNode). These adapters automatically bridge data formatting mismatches (e.g., stringified JSON, conversational envelopes) between upstream and downstream nodes without requiring manual glue code.Self-Healing Node-to-Node Data Flows (
workflow)ToolNodeSelf-Healing Input Parsing: Upstream text nodes often serialize structured arguments into JSON strings. If the incoming input toToolNodeis a JSON-serialized string, it will automatically attempt to unmarshal it into a structuredmap[string]anyconforming to the tool's input schema, preventing schema verification crashes.FunctionNodeDirect Event Propagation: When a registered custom function explicitly returns a*session.Event, it is now propagated directly down the stream instead of being wrapped inside an.Outputfield. This allows custom workflow nodes to declare explicit routing tags (ev.Routes) to trigger complex conditional branches.