ServiceTitan Integration — Data Scope
Effective October 26, 2026
This page defines exactly what R.U.A.C.H.™ reads from and writes to a Customer's ServiceTitan account when the Customer connects the integration. The scope is intentionally narrow: register installed equipment and put the proof back on the job.
Workflow supported
- Every 4 hours (or on demand via "Sync now"), read Completed jobs tagged "Equipment Not Registered".
- For each job, read the customer name, service-location address and installed equipment (model + serial).
- Register each unit with the correct manufacturer and retrieve the certificate — this happens in R.U.A.C.H., not in ServiceTitan.
- Attach the certificate PDF to the job and replace the tag "Equipment Not Registered" with "Equipment Registered".
Data we READ
| ServiceTitan API | Fields used | Purpose |
|---|---|---|
| Job Planning & Management — Jobs | id, jobNumber, customerId, locationId, completedOn, tags | Find completed installs that still need registration |
| CRM — Customers | name | Homeowner name for the registration |
| CRM — Locations | street, unit, city, state, zip | Installation address for the registration |
| Equipment Systems — Installed Equipment | model, serialNumber (by location) | Units to register |
| Settings — Tag Types | id, name | Resolve the two tag names above |
Data we WRITE
| ServiceTitan API | Action | Boundary |
|---|---|---|
| Forms — Job Attachments | Add one PDF per manufacturer certificate | Add only; we never modify or delete existing attachments |
| Jobs — Tags | Remove "Equipment Not Registered"; add "Equipment Registered" | Only these two tags; no other tags are touched |
Explicitly out of scope
We do not read or write invoices, payments, pricebook, estimates, memberships, payroll, technicians, dispatch/capacity, marketing, phone/call data, or any customer contact details beyond name and service address. We never delete or overwrite ServiceTitan records.
Load profile
One scheduled sync per Customer every 4 hours; paged reads of at most 50 jobs per sync; requests are spaced and back off automatically on HTTP 429/5xx honouring Retry-After. Write-backs occur once per registered job (one attachment per certificate plus two tag operations).
Credentials
The Customer supplies their ServiceTitan Tenant ID and Application Key inside R.U.A.C.H.; the key is encrypted at rest and can be removed instantly with "Disconnect". R.U.A.C.H.'s own Client ID/Secret are held as platform secrets and never exposed to Customers or browsers.