← Saturday, October 3, 2026AgentsGuide

ADK graph workflows combine parallel steps, routing and human review

cloud.google.com by Annie Wang, Shangjie Chen 12 min read Editor score 7/10

A refund workflow demonstrates fan-out and fan-in, deterministic and agent-based routing, human review pauses, and dynamic orchestration alongside static graphs. These patterns help engineers choose how to structure agent workflows and where to keep control deterministic.

What: ADK Workflows turn graph designs into executable processes using functions and agents.
How: In the refund example, order, payment, and refund-history lookups run in parallel, then a JoinNode waits for their results before the policy decision.
Why it matters: Separating work into nodes lets engineers control parallelism, routing, human review, and whether paths are static or dynamically scheduled.

Three refund lookups run in parallel and join before the workflow continues. Sketched from the article's own text.

Read on cloud.google.com →

Discussion

Discussion is not switched on yet. Use Note above to keep your own thoughts on this story.

Headline, summary, brief and diagram are written by a model from the source's own text; the link, byline and numbers come from the source. Read the original before relying on a claim.