🎨 Multi-Agent Workflow Gallery

Explore complete multi-agent systems in action. Click on any agent to see its system prompt, tools, and responsibilities.

E-commerce Return System

Orchestrator pattern with sequential execution for structured return processing

Orchestrator Pattern Sequential Execution Content-Based Routing

πŸ’‘ Key Insights

  • Central orchestrator coordinates all steps in a defined sequence
  • Each agent has a single, clear responsibility
  • State is passed forward from each agent to the next
  • Failure at any step triggers compensation of previous actions
Request Flow: Customer initiates return request
πŸ‘€
Customer Request
"I want to return my order"
🎯
Return Orchestrator
Coordinates the workflow
πŸ“‹
Policy Agent
Step 1: Check eligibility
πŸ“¦
Inventory Agent
Step 2: Update stock
πŸ’°
Refund Agent
Step 3: Process refund
βœ‰οΈ
Communication Agent
Step 4: Notify customer
βœ…
Return Processed
Customer receives confirmation
User Input
Orchestrator
Worker Agent
Final Response

State Management

Ephemeral Workflow context passed between agents

Error Handling

Compensation pattern - rollback completed steps on failure

Coordination

Pessimistic locking for inventory updates

Market Analysis Report

Orchestrator pattern with parallel execution for fast data gathering

Orchestrator Pattern Parallel Execution High Performance

πŸ’‘ Key Insights

  • Multiple agents run simultaneously to minimize total execution time
  • Each agent queries a different data source independently
  • Synthesis agent combines all results into final report
  • Ideal when tasks have no dependencies on each other
Request Flow: Generate comprehensive market report
πŸ‘€
Analyst Request
"Analyze Company X"
🎯
Analysis Orchestrator
Splits into parallel tasks
πŸ“°
News Agent
Recent news
πŸ“ˆ
Stock Agent
Price data
πŸ”
Competitor Agent
Competitor analysis
πŸ“Š
Synthesis Agent
Combines all results
πŸ“‹
Final Report
Comprehensive analysis

State Management

Ephemeral Results aggregated at synthesis

Error Handling

Fallback - use cached data if source unavailable

Performance

3x faster than sequential (tasks run simultaneously)

Customer Support Router

Orchestrator pattern with conditional branching for intelligent routing

Orchestrator Pattern Conditional Logic Priority-Based

πŸ’‘ Key Insights

  • Classifier agent determines the type and priority of request
  • Different paths for different request types (technical, billing, account)
  • Urgent requests escalate immediately to human agents
  • Demonstrates decision trees in multi-agent systems
Request Flow: Customer submits support ticket
πŸ‘€
Customer Request
"I have a problem..."
🎯
Support Router
Classifies request
πŸ”
Classifier Agent
Analyzes content & urgency
⚠️ Conditional Branching ⚠️
IF TECHNICAL
πŸ”§
Tech Agent
Bug fixes
IF BILLING
πŸ’³
Billing Agent
Payments
IF ACCOUNT
πŸ‘€
Account Agent
Access issues
IF URGENT
🚨
Human Agent
Immediate attention
βœ…
Issue Resolved
Customer receives solution

State Management

Persistent Ticket history stored

Error Handling

Human escalation for low-confidence classifications

Routing Strategy

Content-based + priority-based routing

Network Diagnostics System

Peer-to-peer pattern with dynamic agent coordination

Peer-to-Peer Pattern Decentralized Dynamic Coordination

πŸ’‘ Key Insights

  • No central orchestrator - agents communicate directly
  • Monitoring agent decides which other agents to consult
  • Agents coordinate dynamically based on what they discover
  • More flexible but harder to trace and debug
Request Flow: Anomaly detected in network
⚠️
Network Anomaly
High latency detected
πŸ“‘
Monitoring Agent
Detects and investigates
↕️ Direct Agent-to-Agent Communication ↕️
πŸ—ΊοΈ
Topology Agent
Network layout
πŸ“
Log Analysis Agent
Device logs
πŸ“Š
Traffic Agent
Pattern analysis
↕️ Agents Share Findings Directly ↕️
πŸ”¬
Diagnosis Agent
Synthesizes findings
βœ…
Root Cause Found
Remediation suggested

State Management

Ephemeral Findings shared between agents

Error Handling

Retry + fallback for data source failures

Coordination

Event broadcasting for state changes

Multi-Agent RAG System

Specialized pattern for complex question answering with multiple sources

Orchestrator Pattern Parallel Retrieval Multi-Source

πŸ’‘ Key Insights

  • Coordinator breaks complex questions into sub-questions
  • Specialized retrieval agents query different knowledge sources
  • Synthesis agent combines information with source attribution
  • Critical for questions requiring multiple perspectives or domains
Request Flow: Complex research question
πŸ‘€
Research Question
"How does X compare to Y?"
🎯
Query Coordinator
Decomposes question
Parallel Retrieval from Multiple Sources
πŸ—‚οΈ
Internal Docs Agent
Company knowledge
🌐
Web Search Agent
Public sources
πŸ’Ύ
Database Agent
Structured data
πŸ“
Synthesis Agent
Combines + cites sources
πŸ“š
Comprehensive Answer
With source citations

State Management

Ephemeral Query context passed forward

Error Handling

Continue with available sources if one fails

Coordination

No concurrency issues (read-only operations)