Router

​

What Does the Router Node Do?

• Route urgent tickets to your escalation team
• Send billing questions to your finance department
• Direct general inquiries to your standard support queue

​

Real-World Workflow Examples

​

Lead Website Analyzer (Standard Routing)

1. Sheet Reader → Reads prospect websites from Google Sheet
2. Website Scraper → Scrapes each website to get content
3. Router (Standard Mode) → Uses text conditions to detect platforms
4. Actions → Routes qualified leads to Slack, others to Gmail rejection

Route 1: "Shopify Leads" (Qualified)
Conditions:
- website_content [Text] Contains "shopify"
- OR website_content [Text] Contains "myshopify.com"

Route 2: "Other Websites" (Rejected)  
Conditions: - website_content [Text] Does not Contain "shopify"

​

Support Request Triage (AI Routing)

1. Gmail Reader → Reads support emails from a specific label
2. Router (AI Mode) → Uses AI to understand intent and urgency
3. Actions → Routes to appropriate teams and systems

Route 1: "General Questions"
AI Condition: "standard support questions and general inquiries"
Action: Slack notification to general support

Route 2: "Billing Questions"  
AI Condition: "questions about payments, invoices, or account billing"
Action: Email finance team

Route 3: "Feature Request"
AI Condition: "Feature request or general improvement requested by the user"
Action: Create Linear ticket 

​

Key Differences

​

Common Elements

• Loop Mode: Processing multiple items individually
• Fallback Routes: Catching unmatched items
• Multiple Actions: Different routes trigger different responses

​

Node Inputs

​

Input to Evaluate

• ticket_description - to route based on the content of the issue

​

Routes

• Route 1: “Urgent”
• Route 2: “Billing Question”
• Route 3: “Technical Support”
• Route 4: “General Inquiry”

​

Optional Fields

​

Route With AI

• AI Mode (Default): Let AI decide if an email is a “complaint” vs “compliment” based on content
• Standard Mode: Use logical conditions like “if priority equals ‘high’ then route to urgent”

​

AI Model Selection

​

Node Outputs

​

How Outputs Work

• Inputs to Router: ticket_description, ticket_title, ticket_link, customer_email
• Input to Evaluate: ticket_description (this determines the routing)
• Routes: “Urgent”, “Billing Question”, “Technical Support”

​

Visual Representation

Router Node
├── Input: ticket_description (used for routing decision)
├── Input: ticket_title
├── Input: ticket_link
└── Input: customer_email

Routes:
├── Urgent Branch → [ticket_description, ticket_title, ticket_link, customer_email]
├── Billing Question Branch → [ticket_description, ticket_title, ticket_link, customer_email]
└── Technical Support Branch → [ticket_description, ticket_title, ticket_link, customer_email]

​

Connecting Outputs

Router
├── Urgent Branch → Slack Alert (immediate notification)
├── Billing Question Branch → Gmail Sender to Finance Team
└── Technical Support Branch → Jira Issue Writer

​

Important Notes

1. All Data Available: Every route has access to all input data, not just the evaluation input
2. Selective Activation: Only one route per item will be active and pass data through
3. Preserve Context: All related information stays together through the routing process

​

Routing Modes

​

AI Routing Mode (Recommended)

​

How It Works

1. Input Selection: Choose which input data the AI should evaluate
2. Route Definition: Create routes with descriptive names
3. AI Conditions: Describe when each route should be used (optional but recommended)
4. Model Selection: Choose an AI model for decision-making

​

Configuration Example

Route Name: "Customer Complaint"
Input to Evaluate: email_content
AI Condition: "when the email expresses dissatisfaction, frustration, or requests a refund"

Route Name: "Product Inquiry"  
Input to Evaluate: email_content
AI Condition: "when the email asks questions about features, pricing, or product information"

Route Name: "Technical Support"
Input to Evaluate: email_content  
AI Condition: "when the email reports bugs, technical issues, or requests help with setup"

​

Best Practices for AI Routing

1. Use Descriptive Route Names: Even without AI conditions, the AI can often infer routing logic from clear route names
   Copy

   Ask AI

   ✅ Good: "Positive Review", "Negative Review", "Neutral Review"
   ❌ Poor: "Route A", "Route B", "Route C"
   

2. Provide Clear AI Conditions: Give the AI enough information to make accurate decisions
   Copy

   Ask AI

   ✅ Good: "when the message expresses anger, frustration, or demands immediate action"
   ❌ Poor: "negative sentiment"
   

3. Choose the Right AI Model: Use more powerful models for complex routing decisions

​

Standard Routing Mode

​

How It Works

1. Route Definition: Create named routes for different paths
2. Condition Building: Set up logical conditions using the condition dropdown
3. Boolean Logic: Combine conditions with AND/OR operators within each route
4. Sequential Evaluation: Routes are evaluated in order from top to bottom - first match wins

​

Supported Condition Types

​

Understanding Route Evaluation Order

​

Loop Mode Processing

​

Loop Mode ON (Default for Lists)

Input: ["urgent ticket", "billing question", "general inquiry"]

Processing:
- Item 1: "urgent ticket" → Routes to Support Team
- Item 2: "billing question" → Routes to Finance Team  
- Item 3: "general inquiry" → Routes to General Team

Output: Items distributed across different routes

​

Notes

​

Input Validation

• Type Consistency: All inputs that you’re evaluating must be the same type (text or list)
• List Size Matching: All list inputs must have identical lengths

​

Credit Management

• Standard Routing: 0 credits (logic-based, no external APIs)
• AI Routing: Credits are charged based on the AI model being used:
  • Standard models: 2 credits
  • Advanced models: 20 credits
  • Expert models: 30 credits

​

Router vs If-Else Logic

​

Troubleshooting

​

Common Issues

1. “No route matched” Error
   • Solution: Add a fallback route that catches unmatched items
   • Prevention: Test with edge cases and unexpected values
2. “Input type mismatch” Error
   • Solution: Ensure all inputs are the same type (text or list)
   • Prevention: Use data type conversion nodes before the Router
   • More info on type mismatch available here.
3. “List size mismatch” Error
   • Solution: Ensure all list inputs have the same length
   • Prevention: Use Duplicate node to match list sizes
   • More info on list size mismatch available here.

​

Debugging Tips

1. Test with Simple Cases: Start with clear-cut examples
2. Monitor Run Logs: Check which routes are being selected
3. Use Descriptive Names: Makes debugging easier
4. Validate Inputs: Ensure input data is clean and expected format

​

Best Practices Summary

​

General Guidelines

1. Start Simple: Begin with 2-3 routes and add complexity as needed
2. Test Thoroughly: Validate routing decisions with sample data
3. Use Descriptive Names: Clear route names improve maintainability
4. Always Include a Fallback Route: Add a route with no conditions to catch unmatched items
5. Order Routes by Priority: Place most specific conditions first, general conditions last

​

AI Routing Specific

1. Choose Appropriate Models: Match model complexity to routing difficulty
2. Provide Context: Give AI enough information to make accurate decisions
3. Use Examples: Include examples in AI conditions when possible
4. Test Consistency: Verify AI makes consistent routing decisions

​

Standard Routing Specific

1. Order by Specificity: Most specific conditions first
2. Use Logical Grouping: Combine related conditions effectively
3. Validate Data Types: Ensure inputs match expected formats

​

Need Help?

• Community Forum: Get help from other users at forum.gumloop.com
• Example Workflows: Check out the Lead Analyzer and Support Triage workflows for inspiration