The Problem
A lead-gen agency serving roofing companies asked me to connect a client's GoHighLevel account to ServiceTitan and Siro, the same kind of integration I'd built for the agency before. ServiceTitan is where the client books jobs. Siro is where the sales reps' in-person conversations with those leads get recorded and analyzed. Once leads were flowing, one thing was off. The address on the ServiceTitan customer record was right, but the booking showed a different one. At first it wasn't clear whether GoHighLevel or ServiceTitan was causing it.
The Build
A GoHighLevel workflow sends each new lead to Zapier. Zapier sends it to ServiceTitan, where the customer and the job booking are created. From there, ServiceTitan's built-in Siro integration passes the job on. The cause of the wrong address was in GoHighLevel. The sub-account had several custom fields with the same name, and the booking was reading the wrong one. I pointed it at the right field and tested it end to end.
Screens
The Outcome
Leads from GoHighLevel land in ServiceTitan with the right address on both the customer record and the booking, and they carry on to Siro. It's still running for the agency's client.


