How to handle multi-step branches

Hi team!

I'm converting an N8N workflow to Mastra and struggling with how to properly implement branching logic where each branch needs to execute multiple steps before merging back to the main workflow.

Use Case:
I'm processing inbound emails and need to branch based on security checks:

Email Processing Workflow:

START
  ↓
[Step 1] Receive Email
  ↓
[Step 2] Security Check
  ↓
  ├─── IF Security Issues Detected:
  │      ↓
  │    [Branch A1] Log Security Incident
  │      ↓
  │    [Branch A2] Quarantine Email
  │      ↓
  │    [Branch A3] Send Security Alert
  │      ↓
  │    [Merge Point]
  │
  └─── IF No Security Issues:
         ↓
       [Branch B1] Validate Sender
         ↓
       [Branch B2] Extract Email Content
         ↓
       [Branch B3] Classify Email Type
         ↓
       [Branch B4] Process Content
         ↓
       [Branch B5] Update Database
         ↓
       [Merge Point]
  ↓
[Step 3] Send Confirmation/Response
  ↓
END

Email Processing Workflow:

START
  ↓
[Step 1] Receive Email
  ↓
[Step 2] Security Check
  ↓
  ├─── IF Security Issues Detected:
  │      ↓
  │    [Branch A1] Log Security Incident
  │      ↓
  │    [Branch A2] Quarantine Email
  │      ↓
  │    [Branch A3] Send Security Alert
  │      ↓
  │    [Merge Point]
  │
  └─── IF No Security Issues:
         ↓
       [Branch B1] Validate Sender
         ↓
       [Branch B2] Extract Email Content
         ↓
       [Branch B3] Classify Email Type
         ↓
       [Branch B4] Process Content
         ↓
       [Branch B5] Update Database
         ↓
       [Merge Point]
  ↓
[Step 3] Send Confirmation/Response
  ↓
END

What I've Tried:
Using Workflow.branch() - but the documentation and examples only show single-step branches (just a then: async () => {} function)

Creating sub-workflows - but this creates a poor UX in Mastra Studio as I can't clearly see the results of sub-workflows when building/debugging

Questions:
Is there a way to define multiple sequential steps within a branch before merging back to the main flow?

Should I be nesting all the logic inside the branch's then function, or is there a cleaner pattern?

Are there any examples of complex branching workflows with multiple steps per branch?

Any guidance or examples would be really helpful! Coming from N8N where this is visually straightforward, so looking for the Mastra equivalent pattern.

Email Processing Workflow:

START
  ↓
[Step 1] Receive Email
  ↓
[Step 2] Security Check
  ↓
  ├─── IF Security Issues Detected:
  │      ↓
  │    [Branch A1] Log Security Incident
  │      ↓
  │    [Branch A2] Quarantine Email
  │      ↓
  │    [Branch A3] Send Security Alert
  │      ↓
  │    [Merge Point]
  │
  └─── IF No Security Issues:
         ↓
       [Branch B1] Validate Sender
         ↓
       [Branch B2] Extract Email Content
         ↓
       [Branch B3] Classify Email Type
         ↓
       [Branch B4] Process Content
         ↓
       [Branch B5] Update Database
         ↓
       [Merge Point]
  ↓
[Step 3] Send Confirmation/Response
  ↓
END

Email Processing Workflow:

START
  ↓
[Step 1] Receive Email
  ↓
[Step 2] Security Check
  ↓
  ├─── IF Security Issues Detected:
  │      ↓
  │    [Branch A1] Log Security Incident
  │      ↓
  │    [Branch A2] Quarantine Email
  │      ↓
  │    [Branch A3] Send Security Alert
  │      ↓
  │    [Merge Point]
  │
  └─── IF No Security Issues:
         ↓
       [Branch B1] Validate Sender
         ↓
       [Branch B2] Extract Email Content
         ↓
       [Branch B3] Classify Email Type
         ↓
       [Branch B4] Process Content
         ↓
       [Branch B5] Update Database
         ↓
       [Merge Point]
  ↓
[Step 3] Send Confirmation/Response
  ↓
END

How to handle multi-step branches

Similar Threads

How to handle multi-step branches

Similar Threads

Similar Threads

Similar Threads