Integration Products | Campaign Creators

ServiceTitan HubSpot Integration | Campaign Creators

Written by Campaign Creators | Nov 17, 2026, 3:48:34 PM
Integration Assessment
Integration Assessment · Field Service

ServiceTitan × HubSpot

How a home or commercial services business can bring ServiceTitan customers, locations, jobs, estimates, invoices and memberships into HubSpot, follow up on unsold estimates, and tie every booked job and invoice back to the marketing campaign that produced it.

CRM · customers & locationsJobs & appointmentsSales & EstimatesAccounting · invoicesMembershipsOAuth 2.0 REST APIs (v2)
Platform ownerServiceTitan
Integration typeCustom, on ServiceTitan's v2 APIs
Primary directionServiceTitan → HubSpot
FeasibilityStrong fit
API accessOpen API
01 — Summary

Does ServiceTitan integrate with HubSpot?

ServiceTitan runs the operating side of a trades business: call booking, dispatch, jobs, estimates, invoicing and memberships. Every one of those records belongs to a customer and a service location.

API access
Open APIOpen with conditionsGated API

Public documentation. The client's own admin issues credentials, with no vendor approval needed.

Open API. The API is documented in ServiceTitan's developer portal. The app is created there, and a tenant admin connects it and approves its scopes.

Based on the vendor's public documentation. Access terms are confirmed with the vendor and the client in discovery.

ServiceTitan holds the revenue truth, and HubSpot turns it into marketing that knows what each customer bought, what they did not buy, and which campaign brought them in.

Campaign Creators assessment

ServiceTitan publishes v2 REST APIs through its developer portal, grouped by area (CRM, Job Planning and Management, Dispatch, Sales and Estimates, Accounting, Marketing, Memberships, Reporting and more), with OAuth 2.0 client credentials and a per-app key. Export endpoints support bulk and incremental reads. That makes a direct ServiceTitan-to-HubSpot integration buildable: customers, jobs, estimates, invoices and memberships land in HubSpot, and HubSpot leads can be handed to ServiceTitan as bookings with their campaign attached. The main design work is the HubSpot data model (residential and commercial customers, locations, jobs) and agreeing who sends customer email, since ServiceTitan can also send marketing.

Scorecard
Data richnessHigh
API accessTenant-approved
Public docsGood
Build complexityModerate

Ratings are CC judgments from ServiceTitan's developer portal and help center. API scopes, environments and limits are confirmed for the client's tenant during discovery.

Strength

Every dollar ties to a customer and a campaign

Jobs carry the customer, location, business unit and campaign. Invoices carry the job. HubSpot can report revenue by campaign, not just leads by campaign.

Plan for

Residential and commercial look different

A homeowner is one HubSpot contact. A commercial account is a company with many contacts and many service locations. The data model handles both before any sync runs.

Gate

Tenant admin approves the app

A ServiceTitan admin connects the app under API Application Access and allows the requested scopes. Make this a client-owned dependency with a date in the SOW.

02 — API modules

Which ServiceTitan APIs does the integration use?

Seven ServiceTitan API areas matter to HubSpot. Five carry the integration, one enriches it, and one is a scope decision.

Core

CRM

Customers, contacts, locations, bookings

The customer record, its contact methods and every service location, plus bookings and leads.

  • Residential customers become HubSpot contacts
  • Commercial customers become companies with contacts
  • Service locations become a custom object
Core

Job Planning & Management

Jobs, appointments, projects

Every job, its type, business unit, status, appointments and the campaign it was booked under.

  • Jobs become a HubSpot custom object
  • Completed jobs trigger review and follow-up
  • Campaign on the job drives attribution
Core

Sales & Estimates

Estimates and opportunities

Estimates presented on a job, sold or unsold, grouped into opportunities with follow-up statuses (Open, Unreachable, Contacted, Won, Dismissed).

  • Estimates become HubSpot deals
  • Sold closes won; dismissed closes lost
  • Unsold estimates feed HubSpot follow-up
Core

Accounting

Invoices and payments

Invoices, payments and balances for each job and customer.

  • Lifetime revenue and last invoice on the customer
  • Revenue by campaign in HubSpot reports
  • No card or bank data leaves ServiceTitan
Core

Memberships

Memberships, types, recurring services

Customer memberships with status (Active, Suspended, Expired, Canceled), type, dates and recurring service visits.

  • Memberships become a HubSpot custom object
  • Expiring memberships trigger renewal campaigns
  • Non-members are a sales list
Enrichment

Marketing

Campaigns and categories

ServiceTitan campaigns with name, category, source, medium and tracking numbers. Calls and jobs are attributed to them.

  • One mapping table: ServiceTitan campaign ↔ HubSpot campaign
  • HubSpot leads booked with the right campaign
  • Closed-loop revenue reporting
Scope decision

Who emails the customer

Scope decision

ServiceTitan can send customer marketing and notifications, and HubSpot can too. Decide which system sends each message type before any sync runs.

  • Recommended: ServiceTitan keeps appointment and job notices
  • HubSpot owns campaigns, nurture and follow-up
  • One opt-out honored in both systems
03 — Framework

How does the ServiceTitan HubSpot integration work?

A CC-built integration layer reads ServiceTitan's v2 APIs on a schedule, using export endpoints for bulk and incremental changes. It matches every record to the right HubSpot object, computes rollups, and writes in batches. HubSpot leads go back to ServiceTitan as bookings.

ServiceTitan
CRMcustomers, contacts, locations
Jobs & appointmentsjob, status, campaign, business unit
Estimates & invoicessold, unsold, dismissed; revenue
Memberships & campaignsstatus, renewals; campaign list
CC integration layer
Incremental readerexport endpoints, continuation tokens
Identity resolvercustomer ID · location ID · email · phone
Campaign mapServiceTitan campaign ↔ HubSpot campaign
Rollupsrevenue, jobs, membership status
HubSpot writer & booking bridgebatch upserts; leads → bookings
HubSpot
Contacts & companiesresidential and commercial customers
Service locations & jobs (custom objects)where and what was done
Dealsestimates in a sales pipeline
Memberships (custom object)status, type, expiry
Workflows & reportsfollow-up, renewals, revenue by campaign
ServiceTitan → HubSpot (primary flow)HubSpot → ServiceTitan (bookings with campaign, contact updates)
Principle

ServiceTitan owns operations

Jobs, schedules, estimates, invoices and memberships are created and changed in ServiceTitan. HubSpot mirrors them and never edits them.

Principle

HubSpot owns marketing and follow-up

Campaigns, nurture, review requests and estimate follow-up run in HubSpot, using ServiceTitan data as triggers.

Principle

Every record keeps its campaign

The campaign on a booking, job and invoice is carried into HubSpot unchanged, so revenue reports match ServiceTitan.

04 — Process

What does ServiceTitan HubSpot integration setup involve?

Each phase ends on a gate the client signs off before the next begins. ServiceTitan's integration environment is used for build and test before production.

1

Discovery & access

Register the app in ServiceTitan's developer portal, select the API scopes, and have a tenant admin connect it under API Application Access. Confirm business units, job types and campaigns in use.

Gate to next phaseApp connected in the integration environment
2

Data model decisions

Agree how residential and commercial customers map to contacts and companies, which records become custom objects, the estimate pipeline stages, and who sends each message type.

Gate to next phaseSigned data model and sender-of-record matrix
3

Campaign mapping

List ServiceTitan campaigns and categories and pair each with a HubSpot campaign or source. Decide which ServiceTitan campaign HubSpot bookings use by default.

Gate to next phaseSigned campaign mapping table
4

HubSpot data model

Create the Service Location, Job and Membership custom objects, the estimate pipeline, properties, association labels and property groups in a HubSpot sandbox.

Gate to next phaseSchema approved and created in sandbox
5

Build & test

Build the incremental reader, identity matching, campaign map, rollups, booking bridge, idempotent writes and an error replay queue. Test against the integration environment.

Gate to next phaseAll record types syncing cleanly in sandbox
6

Backfill

Load customers, locations and memberships, plus an agreed window of jobs, estimates and invoices, then compute rollups once so reports start complete.

Gate to next phaseHubSpot revenue and counts reconcile to ServiceTitan reports within an agreed tolerance
7

Workflows, parallel run & launch

Build follow-up, renewal and review workflows with sends paused, run two weeks in parallel, then switch on.

Gate to next phaseFive consecutive days with no unresolved sync errors
05 — Data mapping

What does the ServiceTitan HubSpot integration sync?

Field names describe ServiceTitan records as its help center and API areas present them. Exact field paths come from the v2 API reference and are confirmed in discovery.

ServiceTitan fieldHubSpot propertyObjectDirectionNotes
CRM · customers & locations
Customer IDst_customer_idContact / CompanyST → HSPrimary key. Unique.
Customer type (residential / commercial)st_customer_typeContact / CompanyST → HSResidential → contact; commercial → company.
Customer namefirstname, lastname / nameContact / CompanyST → HSServiceTitan is the source.
Contact emailemailContact↔ BothMatch key. HubSpot fills blanks only.
Contact phonephone, mobilephoneContact↔ BothNormalize to E.164. Match key #2.
Location IDst_location_idService LocationST → HSOne record per service address.
Location addressaddress fieldsService LocationST → HSAssociated to the customer.
Jobs & appointments
Job ID / job numberst_job_idJobST → HSPrimary key for the Job object.
Job typest_job_typeJobST → HSDrives follow-up and review workflows.
Business unitst_business_unitJobST → HSHVAC, plumbing, electrical, etc.
Job statusst_job_statusJobST → HSScheduled, completed, canceled.
Campaign on the jobst_campaign_idJobST → HSAttribution key.
Appointment startst_next_appointmentContactST → HSNext scheduled visit on the customer.
Completed datest_last_service_dateContactST → HSLatest completed job.
Estimates & invoices
EstimateDeal (Estimates pipeline)DealST → HSOne deal per estimate, associated to the job.
Estimate totalamountDealST → HSSubtotal as ServiceTitan reports it.
Sold / unsold / dismisseddealstageDealST → HSSold → closed won; dismissed → closed lost.
Follow-up statusst_followup_statusDealST → HSOpen, Unreachable, Contacted, Won, Dismissed.
Sold dateclosedateDealST → HS
Invoice totalst_lifetime_revenueContact / CompanyST → HSSum of invoices, computed in the integration layer.
Latest invoice datest_last_invoice_dateContact / CompanyST → HS
Invoice balancest_open_balanceContact / CompanyST → HSOptional. Confirm with finance.
Memberships & campaigns
MembershipMembershipCustom objectST → HSAssociated to customer and location.
Membership typest_membership_typeMembershipST → HS
Membership statusst_membership_statusMembershipST → HSActive, Suspended, Expired, Canceled.
Membership end datest_membership_endMembershipST → HSDrives renewal workflows.
Campaign name and categoryst_campaign_name, st_campaign_categoryContactST → HSFirst and latest campaign on the customer.
HubSpot leadBooking with campaignBookingHS → STCreated through the CRM bookings API; confirm booking setup in discovery.
06 — Auth & API

How are authentication and API limits handled?

ServiceTitan apps are registered in its developer portal and approved per tenant. Values ServiceTitan does not publish are marked for confirmation.

TopicServiceTitanHubSpot
Access modelApp created in the ServiceTitan developer portal with selected API scopes; a tenant admin connects it under Settings > Integrations > API Application Access.Self-serve in the client portal. Custom objects need an Enterprise hub.
AuthenticationOAuth 2.0 client credentials (client ID and secret) return an access token. Each API call sends the token and the app key, and every path names the tenant ID.Private app access token or OAuth 2.0 public app, scoped per object.
Interfacesv2 REST APIs by area: CRM, Job Planning and Management, Dispatch, Sales and Estimates, Accounting, Marketing, Memberships, Reporting.REST APIs: CRM objects, custom objects, associations, pipelines.
Change detectionExport endpoints return bulk and incremental changes with a continuation token. Confirm webhook options for the tenant in discovery.Writes are immediate; batch endpoints handle volume.
Rate limits60 calls per second per application per tenant for regular APIs; one run of the same report per minute per tenant for Reporting APIs.Per-10-second burst and daily limits by subscription tier.
EnvironmentsIntegration environment for build and test (a clone of production for existing customers) and production.HubSpot sandbox for build; production portal at launch.
Sensitive dataCustomer addresses, phone numbers and payment records. Payment details stay in ServiceTitan; only totals and dates sync.Field-level permissions by team; sensitive data properties on Enterprise.
07 — Issues & opportunities

What should you plan for, and what does the integration unlock?

Severity reflects impact on the SOW, not technical difficulty alone.

Challenges to plan for

Two systems can message the same customerHigh

ServiceTitan sends appointment notices and can run marketing; HubSpot runs campaigns. Without a sender-of-record decision, customers get duplicates.

Residential and commercial in one modelHigh

Homeowners and commercial accounts need different HubSpot shapes. Agree the rules, including multi-location commercial customers, before the build.

Volume of jobs and invoicesMedium

A busy shop creates thousands of jobs a month. Sync identified records and rollups, not every line item, so HubSpot stays fast and within API limits.

Campaign lists driftMedium

New ServiceTitan campaigns appear over time. The integration flags any unmapped campaign so attribution reports stay complete.

Booking setup for HubSpot leadsMedium

Sending HubSpot leads into ServiceTitan as bookings needs configuration on the tenant. Confirm the booking path and default campaign in discovery.

Report endpoint limitsLow

Reporting APIs allow one run of the same report per minute per tenant. The build reads source records and computes rollups instead of polling reports.

Opportunities in HubSpot

Unsold estimate follow-upHigh value

Every open estimate becomes a HubSpot deal with its value and age, so sequences and tasks work the biggest opportunities first, and a sale closes the deal automatically.

Revenue by campaignHigh value

HubSpot reports show booked jobs and invoiced revenue by campaign and channel, not just leads, so spend moves to what produces work.

Membership renewals and sign-upsHigh value

Expiring memberships trigger renewal campaigns, and customers without a membership after a repair get a membership offer.

Review requests after completed jobsMedium value

A completed job triggers a review request from HubSpot, timed by job type and business unit.

Seasonal and equipment-age campaignsMedium value

Service history by location and business unit drives tune-up, maintenance and replacement campaigns to the right households.

Commercial account managementMedium value

Commercial customers become companies with their locations, jobs and revenue, so account managers see the whole relationship.

Core customer journey

From first call to repeat customer.

The integration follows one customer through the service cycle. ServiceTitan runs the work; HubSpot runs the marketing and follow-up around it.

  1. HubSpot captures the lead and books it into ServiceTitan with its campaign attached.
  2. The job, appointments and estimates sync back; unsold estimates start HubSpot follow-up.
  3. Invoices update lifetime revenue and campaign attribution on the customer.
  4. Memberships, renewals and seasonal service keep the customer coming back.
08 — Property schema

Which HubSpot properties does the integration create?

All custom properties use the st_ prefix in a ServiceTitan property group. Rollups are calculated in the integration layer so every report agrees with ServiceTitan.

Internal nameLabelObjectTypeSource / logic
st_customer_idServiceTitan Customer IDContact / CompanySingle-line textCRM customer key; unique
st_customer_typeCustomer TypeContact / CompanyDropdownResidential or commercial
st_location_idServiceTitan Location IDService LocationSingle-line textCRM location key; unique
st_job_idServiceTitan Job IDJobSingle-line textJob key; unique
st_business_unitBusiness UnitJobDropdownJob business unit
st_campaign_idServiceTitan Campaign IDJobSingle-line textCampaign on the job
st_followup_statusEstimate Follow-up StatusDealDropdownOpen, Unreachable, Contacted, Won, Dismissed
st_lifetime_revenueLifetime RevenueContact / CompanyNumber (currency)Sum of invoice totals
st_last_service_dateLast Service DateContactDateLatest completed job
st_next_appointmentNext AppointmentContactDateNext scheduled appointment
st_membership_statusMembership StatusMembershipDropdownActive, Suspended, Expired, Canceled
st_membership_endMembership End DateMembershipDateDrives renewal workflows
09 — Scope builder

Interactive scope builder

Choose the ServiceTitan API areas and fields for this engagement and the direction each one syncs. Required fields are the keys the integration cannot run without. Copy the summary into the SOW or a reply to the client.

Scope summary

0Fields
0Inbound
0Write-back
ServiceTitan × HubSpot Integration Assessment · Designed by Campaign Creators, Elite HubSpot Solutions Partner

ServiceTitan HubSpot integration FAQ

Does ServiceTitan integrate with HubSpot?

Yes, through a custom build on ServiceTitan's v2 REST APIs, which use OAuth 2.0 client credentials and support bulk and incremental exports. The app is registered in ServiceTitan's developer portal, and a tenant admin connects it and approves its scopes.

What data syncs between ServiceTitan and HubSpot?

Residential customers become HubSpot contacts and commercial customers become companies, with service locations, jobs and memberships as custom objects. Estimates become deals, and invoice revenue rolls up to the customer for revenue-by-campaign reporting. HubSpot leads go back to ServiceTitan as bookings with their campaign attached.

Which system owns which data?

ServiceTitan owns operations: jobs, schedules, estimates, invoices and memberships are created and changed there, and HubSpot never edits them. HubSpot owns campaigns, nurture, review requests and estimate follow-up. The campaign on each booking, job and invoice is carried into HubSpot unchanged.

What does setting up the ServiceTitan HubSpot integration involve?

Seven phases, each closed by a client sign-off: discovery and access, data model decisions, campaign mapping, the HubSpot data model, build and test in ServiceTitan's integration environment, a backfill, and a two-week parallel run before follow-up, renewal and review workflows are switched on.

How long does the integration take and what does it cost?

Timeline and cost depend on the record types in scope, the mix of residential and commercial customers, the number of campaigns to map and the history to load. Campaign Creators confirms these in discovery and provides a fixed scope before the build starts.