Make (Integromat) Support Ticket Routing Workflow for beauty

You are a senior automation engineer with extensive technical knowledge in fitness. You write clear, precise, and implementation-ready content.

Design a complete Support Ticket Routing automation workflow using Make (Integromat) for a beauty business.

**Target user:** solopreneurs
**Business goal:** launch a new product
**Integration complexity:** intermediate

## Workflow Overview
- Name: beauty Support Ticket Routing Automation
- Trigger: Define the exact event that starts this workflow
- Expected run frequency: Estimate how often this will execute
- End-to-end description of what the workflow accomplishes

## Trigger Node Configuration
- Trigger type (webhook, schedule, app event, manual)
- Exact trigger settings for Make (Integromat)
- Authentication requirements
- Sample payload structure showing the data that enters the workflow

## Processing Nodes (Step-by-Step)
For each node in the workflow provide:
1. Node type and name
2. Configuration parameters
3. Input data mapping from previous node
4. Transformation or logic applied
5. Output data structure
6. Error handling for this specific node

Design at least 5-7 processing nodes that form a realistic pipeline.

## Conditional Logic
- Define at least 2 IF/Switch conditions that route data differently
- Specify the branching paths and when each triggers
- Include a fallback/default path for unexpected data

## External Integrations
- List every third-party service this workflow connects to
- API endpoints or Make (Integromat) app nodes required
- Authentication method for each service (OAuth2, API key, webhook)
- Rate limiting considerations and retry logic

## Error Handling and Monitoring
- Global error handler configuration
- Notification setup for failed executions (Slack, email, SMS)
- Logging strategy for debugging
- Retry policy (max retries, backoff interval)

## Testing Checklist
- Sample test data to validate the workflow
- Edge cases to test (empty data, malformed input, API timeout)
- Expected output for each test scenario
- Performance benchmarks (execution time, memory usage)

- Use precise technical terminology appropriate for the audience
- Include code examples, configurations, or specifications where relevant
- Document assumptions, prerequisites, and dependencies
- Provide error handling and edge case considerations

Present as numbered steps. Each step should have: a clear action title, detailed instructions, expected outcome, and common pitfalls to avoid.