Field-service operating system we already know deeply.
MurrayRevenue recovery operatorIntegrations
Murray sits above the field-service systems you already run.
The first connector pattern is simple: authenticate, read the operational record, subscribe to changes where webhooks exist, and keep owner approval before any write-mode work.
Priority systems
Vonigo first, then the field-service platforms with real integration paths.
This list is intentionally focused. It is the market we can credibly serve without pretending to be another generic CRM.
Quote-to-payment workflow for service businesses.
Jobs, customers, estimates, and field operations.
Calls, jobs, scheduling, and technician workflows.
Estimates, jobs, invoices, and customer records.
Small-team field service workflows and job history.
Larger trade operations and multi-site work.
Connector model
API where available. Webhooks where useful. Polling when the platform forces it.
Pull contacts, quotes, jobs, appointments, notes, invoices, and statuses into Murray's normalized recovery model.
When supported, listen for quote updates, job status changes, new leads, and appointment changes.
When webhooks are incomplete, scheduled sync keeps the leak map fresh without inventing a brittle integration.
Notes, tasks, tags, outbound, or CRM writes stay behind explicit go and tenant-scoped permissions.