Inbound Routing
Normalize external form and webhook submissions before they become Leenops records.
Inbound routing is the admin area for turning external submissions into clean Leenops records. Use it when a website form, partner form, or webhook sends fields that need to be mapped before they reach CRM, Support, Procurement, or another destination.
Mapping Workflow
Open Settings -> Inbound -> Field Mapping to review the mapping steps:
- Match incoming fields to Leenops fields.
- Normalize values such as email, phone, company name, priority, or requested service.
- Check for duplicates before a new record is created.
- Route the submission to the right destination and keep unmapped values for audit.
The page includes a live preview so administrators can see how sample submissions will be transformed before saving changes.
What Users Can Do
- Keep existing external forms while sending cleaner records into Leenops.
- Preserve source details for later troubleshooting.
- Reduce duplicate contacts, companies, tickets, or requests.
- Route submissions with the same operational rules used by the target module.
Related
- Support Tickets - customer-request queues created from email, portal, widget, API, or inbound flows.
- CRM Custom Fields - custom fields that can receive mapped inbound values.
- Automations - actions that can continue after a record is created.