Voice Backend Integration
Retell Outcome Routing and Notifications
Webhook normalization, CRM lookup, outcome routing, and a separate Slack notification example.
Sanitized evidence and reconstructed architecture
Workflow context
Voice events need backend handling after a conversation. The supplied n8n canvases show an outcome router and a focused notification workflow. Their exact relationship is not established.
My implementation role
Implementation of Retell event handling, CRM contact lookup, and notification workflows represented by the supplied n8n canvases.
Architecture and connected systems
- Retell webhook
- Extract and route
- Contact lookup
- Outcome selection
- API actions
Verified system behavior
- Normalize Retell event payloads
- Extract contact and outcome context
- Separate event types before downstream actions
- Route visible outcome categories to API actions
- Build structured notification fields for Slack
Technologies
Retell AI, n8n, GoHighLevel, Slack, APIs
Evidence note
The outcome router was captured Inactive. The notification canvas is presented as a separate example. The inventory screens and aggregate Retell analytics are excluded. The unidentified conversation graph is not assigned to this project or to the receptionist.
