ServiceTitan to Smartsheet Sync: 1,500 Zapier Tasks a Day Down to a Few per Hour
ServiceTitan to Smartsheet sync built in Zapier for a 50-person plumbing and HVAC contractor: from a projected 1,500 tasks a day to 1 to 3 per run. See how.
TL;DR: A plumbing, heating, and cooling contractor of about 50 people ran its office off Smartsheet dashboards fed by ServiceTitan exports several times a day. We replaced the exports with a ServiceTitan to Smartsheet sync built in Zapier for jobs, tasks, appointments, and invoices. The first straightforward design was projected at about 1,500 Zapier tasks a day. The rebuilt version, using bulk updates and Zapier Tables as a lookup layer, updates jobs every hour during business hours for 1 to 3 tasks per run.
Pipe wrenches, the everyday tools behind a ServiceTitan to Smartsheet sync for a plumbing and HVAC contractor. Photo by Matt Artz on Unsplash
The situation
The company is a residential and commercial plumbing, heating, and cooling contractor with roughly 50 employees.
ServiceTitan is the system of record. It holds jobs, appointments, technician tasks, job tags, and invoices, and the company pays a significant annual sum for it. Day-to-day management, though, happens in Smartsheet. The operations lead built a set of Smartsheet sheets and a dashboard that runs on screens throughout the office, so everyone can see what needs attention without opening ServiceTitan's reports. At any time there are roughly 400 active jobs and invoices in play.
The problem: the dashboard was only as fresh as the last export
ServiceTitan's built-in dashboards weren't actionable enough: date ranges were awkward, it was hard to see when a crew was last on a job, and follow-ups slipped. So the team built its own view in Smartsheet: jobs that haven't been re-dispatched since the last visit, completed jobs tagged as ready to bill but not yet invoiced, and appointments nobody has been assigned to.
That view depended on someone pulling reports out of ServiceTitan, filtering them, and pushing them into Smartsheet. On the first call, the operations lead described the job as running external reports, filtering them down, and doing a lot of manual work. To keep the dashboard current, those exports had to run multiple times a day.
The unassigned-jobs board shows why freshness mattered. As the operations lead put it: "People can't go home at the end of the day leaving jobs unassigned for the next day." A board that's a few hours stale doesn't support that rule.
What they'd already tried
The team was already using Smartsheet's own import add-on. It still needed someone to run the ServiceTitan exports first (the files landed in a Google Sheet, and the add-on pulled from there), and it only covered three sheets. Expanding it to cover everything was quoted in the five figures.
ServiceTitan's Zapier integration looked like the obvious alternative, but it has triggers for new jobs and no triggers for updates. Status changes, rescheduled appointments, and closed tasks, which are most of what the dashboard tracks, weren't covered. Its API is also fragmented: one piece of information can take several calls to assemble.
Cost was the other constraint from day one. The operations lead was clear that the answer had to be "something that's sustainable," not another tool with a five-figure annual price tag.
What we built: a ServiceTitan to Smartsheet sync
A Connex consultant built a one-way sync from ServiceTitan into Smartsheet in Zapier, across about 40 ZoomFlow sessions between spring 2025 and early 2026. It keeps four Smartsheet sheets current: jobs, tasks, appointments, and invoices.
Version one worked, but the task math didn't
The first build used ServiceTitan's API from inside Zapier to pull every job modified since the last run (each run stores its own timestamp, so nothing is fetched twice) and then created or updated the matching Smartsheet row. It worked. But after a week of real data, the consultant ran the numbers with the client: checking for job updates every hour would cost about 1,500 Zapier tasks a day, or roughly 45,000 a month. The operations lead's response was direct: "I already can't expand on this, because we're kind of maxed out where it is right now."
The rebuild: bulk updates and a lookup layer
Rather than trimming fields until the dashboard was useless, the consultant changed how the sync spends tasks:
Bulk updates instead of one row at a time. Changed jobs are collected and written to Smartsheet in bulk, so a run costs a handful of tasks no matter how many jobs changed.
Zapier Tables as a lookup layer. A set of paired tables stores each ServiceTitan job ID next to its Smartsheet row ID. Lookups happen there instead of through repeated, task-costly searches. At the time, the Tables plan came in around $13 to $20 a month (Zapier has since folded Tables into its standard plans; check current pricing). The operations lead's verdict: "That's nothing."
Business-hours scheduling. Jobs update hourly from 8 a.m. to 6 p.m. Nothing runs overnight or over the weekend, when nobody is watching the board.
Update only what changes. Invoice data (status, batch number, balance) refreshes twice a day and only matters when the status or batch changes. Job tags and static IDs like job type and campaign are translated to readable names through lookup tables rather than extra API calls.
Edge cases the sync had to handle
Smartsheet's search lag. Newly created rows weren't findable through Smartsheet's API for 10 to 15 minutes, and the first suggested workaround didn't fix it. The sync now checks Smartsheet first and falls back to the paired table, so a job created seconds before an update run still gets matched.
Duplicates and missing IDs. A "created by automation" column marks every row the sync creates, and job IDs and job numbers link invoices and tasks back to their jobs.
Unusual status paths. Jobs that move from Completed back to Hold, or that belong to an inactive customer, failed silently at first. Each got its own handling rather than being ignored.
Sheet size over time. Monthly archiving moves old records out so the working sheets stay fast and inside Smartsheet's limits.
The operations lead decided which columns came over, which flows went first, and where the cost ceiling sat. Nothing is written back to ServiceTitan.
The results
Live jobs data for 1 to 3 Zapier tasks per hourly update. That's the figure the consultant reported when the rebuilt jobs flow went live. The same hourly cadence on the first design was projected at about 1,500 tasks a day.
Derived from those two figures: 11 hourly runs between 8 a.m. and 6 p.m. at no more than 3 tasks each is at most about 33 tasks a day for the jobs flow, roughly 98% fewer than the ~1,500 projected for version one. Estimated, based on the consultant's reported per-run task counts and the client's business-hours schedule; tasks, appointments, and invoices run as separate flows on the same bulk pattern.
No more manual exports. With the jobs and tasks flows live, the operations lead was ready to shut off the import add-on and the multiple daily export runs it depended on.
A board the office can act on. Unassigned appointments, jobs not yet re-dispatched, and completed work waiting on an invoice show up on the office screens within about an hour during business hours, not after the next export.
A cost the business can live with. Beyond the Zapier plan itself, the lookup layer added a Zapier Tables plan of about $13 to $20 a month at the time, compared with the five-figure quote to expand the import add-on.
In the client's words
The operations lead's priorities set the shape of the project from the first call: "I just want to make sure it's something that's sustainable." Midway through, when the first version proved too expensive to run, he put it plainly: "I have to have a threshold that I'm not going to cross." The rebuild was designed around that threshold, and every later flow followed the same pattern.
FAQ
Does ServiceTitan's Zapier integration handle job updates?
Not on its own. It offers triggers for new records but not for updates. This sync uses ServiceTitan's API from inside Zapier, asking for records modified since the last run, so status changes, reschedules, and closed tasks still come across.
Won't a real-time ServiceTitan sync burn through Zapier tasks?
It can: about 1,500 tasks a day here, updating one row at a time. Bulk updates, a Zapier Tables lookup layer, and business-hours scheduling brought the jobs flow to 1 to 3 tasks per run.
How fast was the first measurable win?
The project kicked off in late March 2025. Test records were syncing into the job and task sheets about a month later, and the cost-optimized jobs flow went live in mid-June, about 11 weeks in.
What access did it need?
Logins for ServiceTitan, Smartsheet, and Zapier, plus API access in ServiceTitan. The sync reads from ServiceTitan only and writes to Smartsheet.
Stuck on a sync that works but costs too much to run?
If your field-service data lives in one system and your team works in another, we can help you connect them without a runaway monthly bill. Book a call with Connex.
A Google Ads agency for home-services firms swapped fragile Zapier lookups for Make + Airtable lead-to-revenue matching across four CRMs. See how it works.
County payroll automation with BambooHR and Windmill: how one Idaho county generates its three pension reporting files every payroll run. See the workflow.
Restaurant automation for a nine-location group: AI review replies, one daily sales report, and an OpenTable rollout. See what to automate first and why.