What syncs
| ClockLap | Sent as | Notes |
|---|---|---|
| Projects | From each row’s Job # and job name or type | Re-uploads only change what changed |
| Clients | From the Customer column | Matched by name first |
| Sites (optional) | From the address (and latitude/longitude, when present) | – |
| Hours worked | CSV: Job ID, Job, Date, Employee, Employee ID, Clock in, Clock out, Hours, Location | Any period |
Column headers are recognised by name (Job #, Job ID, Customer Name, Job Type, Status, Location Address…). A file without a job number column is refused with a plain message.
How it works
- Export the Jobs reportIn ServiceTitan Reports, export jobs as CSV.
- Upload itPreview what would change, then bring the jobs in.
- Clock time to jobsProjects appear in the phone app’s picker.
- Download hoursHours per job for any period, from the connection page.
Jobs and customers
Jobs become projects and their customers become ClockLap clients.
What you need
- A ServiceTitan user who can export reports
Every run keeps a history: who and what was sent, per-line results, plain-language errors with a fix, and a redacted request log for admins. Webhooks fire on field_service.jobs_imported, field_service.hours_sent.
Questions
Why not a direct connection?
ServiceTitan’s API is open only to approved integration partners. ClockLap isn’t one, so it uses the CSV exports every account has.
Is the ServiceTitan connection included in the price?
Yes. Every connection is part of every ClockLap plan: $1 per staff member and $2 per manager or admin a month, with no add-ons.
Is ClockLap affiliated with ServiceTitan?
No. ClockLap connects to ServiceTitan using files it can import; it isn’t affiliated with or endorsed by ServiceTitan. The connection is in beta while we verify it with live accounts.