Introduces two major capabilities: - Workflow runtime: graph-based execution engine for composing deterministic execution flows for agentic apps, with support for routing, fan-out/fan-in, loops, retry, state management, dynamic nodes, human-in-the-loop, and nested workflows - Task API: structured agent-to-agent delegation with multi-turn task mode, single-turn controlled output, mixed delegation patterns, human-in-the-loop, and task agents as workflow nodes Co-Authored-By: Bo Yang <ybo@google.com> Co-Authored-By: George Weale <gweale@google.com> Co-Authored-By: Sean Zhou <seanzhougoogle@google.com> Co-Authored-By: Shangjie Chen <deanchen@google.com> Co-Authored-By: Swapnil Agarwal <swapnilag@google.com> Co-Authored-By: Wei Sun <weisun@google.com> Co-Authored-By: Xuan Yang <xygoogle@google.com> Co-Authored-By: Yifan Wang <wanyif@google.com> Change-Id: I35932c50cfe29ff68559e3781713dbb5eb7b3382
ADK Workflow Nested Workflow Sample
Overview
This sample demonstrates how to compose workflows by embedding one workflow inside another as a single node in ADK Workflows.
It takes a 4-digit year as input and performs two tasks in parallel:
- Historical Event (
find_historical_event): A straightforward Agent node that generates a 2-sentence description of an event that happened that year. - Famous Person (
find_famous_person): A nested Workflow that first finds a person born in that year (find_name), and then forwards that name to another agent to write a biography (generate_bio).
From the perspective of the root_agent workflow, find_famous_person is just another node. The root workflow doesn't need to know the internal steps; it just waits for the parallel branches to finish, then synchronizes their outputs using a JoinNode before formatting them in aggregate_results.
Sample Inputs
196920001984
Graph
Root Workflow (root_agent)
[ START ]
|
v
[process_input]
/ \
/ \
/ \
v v
[find_historical_event] [find_famous_person]
(AGENT) (WORKFLOW)
\ /
\ /
\ /
v v
[join_for_aggregation]
(JOIN)
|
v
[aggregate_results]
Nested Workflow (find_famous_person)
[ START ]
|
v
[find_name]
|
v
[generate_bio]
How To
-
Define your sub-workflow just like any regular workflow. Ensure it accepts the required state (e.g.,
year) and outputs the expected state (e.g.,person_bio).find_famous_person = Workflow( name="find_famous_person", edges=[("START", find_name, generate_bio)], ) -
Treat the sub-workflow as a normal node when defining the edges of the parent workflow. To run them concurrently, place the nodes in a tuple, then use a
JoinNodeto synchronize their parallel executions before the final aggregation.root_agent = Workflow( name="root_agent", edges=[ ("START", process_input, (find_famous_person, find_historical_event), join_for_aggregation, aggregate_results), ], )