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.
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.
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.
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.
Jobs carry the customer, location, business unit and campaign. Invoices carry the job. HubSpot can report revenue by campaign, not just leads by campaign.
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.
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.
Seven ServiceTitan API areas matter to HubSpot. Five carry the integration, one enriches it, and one is a scope decision.
The customer record, its contact methods and every service location, plus bookings and leads.
Every job, its type, business unit, status, appointments and the campaign it was booked under.
Estimates presented on a job, sold or unsold, grouped into opportunities with follow-up statuses (Open, Unreachable, Contacted, Won, Dismissed).
Invoices, payments and balances for each job and customer.
Customer memberships with status (Active, Suspended, Expired, Canceled), type, dates and recurring service visits.
ServiceTitan campaigns with name, category, source, medium and tracking numbers. Calls and jobs are attributed to them.
ServiceTitan can send customer marketing and notifications, and HubSpot can too. Decide which system sends each message type before any sync runs.
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.
Jobs, schedules, estimates, invoices and memberships are created and changed in ServiceTitan. HubSpot mirrors them and never edits them.
Campaigns, nurture, review requests and estimate follow-up run in HubSpot, using ServiceTitan data as triggers.
The campaign on a booking, job and invoice is carried into HubSpot unchanged, so revenue reports match ServiceTitan.
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.
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.
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.
List ServiceTitan campaigns and categories and pair each with a HubSpot campaign or source. Decide which ServiceTitan campaign HubSpot bookings use by default.
Create the Service Location, Job and Membership custom objects, the estimate pipeline, properties, association labels and property groups in a HubSpot sandbox.
Build the incremental reader, identity matching, campaign map, rollups, booking bridge, idempotent writes and an error replay queue. Test against the integration environment.
Load customers, locations and memberships, plus an agreed window of jobs, estimates and invoices, then compute rollups once so reports start complete.
Build follow-up, renewal and review workflows with sends paused, run two weeks in parallel, then switch on.
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 field | HubSpot property | Object | Direction | Notes |
|---|---|---|---|---|
| CRM · customers & locations | ||||
| Customer ID | st_customer_id | Contact / Company | ST → HS | Primary key. Unique. |
| Customer type (residential / commercial) | st_customer_type | Contact / Company | ST → HS | Residential → contact; commercial → company. |
| Customer name | firstname, lastname / name | Contact / Company | ST → HS | ServiceTitan is the source. |
| Contact email | Contact | ↔ Both | Match key. HubSpot fills blanks only. | |
| Contact phone | phone, mobilephone | Contact | ↔ Both | Normalize to E.164. Match key #2. |
| Location ID | st_location_id | Service Location | ST → HS | One record per service address. |
| Location address | address fields | Service Location | ST → HS | Associated to the customer. |
| Jobs & appointments | ||||
| Job ID / job number | st_job_id | Job | ST → HS | Primary key for the Job object. |
| Job type | st_job_type | Job | ST → HS | Drives follow-up and review workflows. |
| Business unit | st_business_unit | Job | ST → HS | HVAC, plumbing, electrical, etc. |
| Job status | st_job_status | Job | ST → HS | Scheduled, completed, canceled. |
| Campaign on the job | st_campaign_id | Job | ST → HS | Attribution key. |
| Appointment start | st_next_appointment | Contact | ST → HS | Next scheduled visit on the customer. |
| Completed date | st_last_service_date | Contact | ST → HS | Latest completed job. |
| Estimates & invoices | ||||
| Estimate | Deal (Estimates pipeline) | Deal | ST → HS | One deal per estimate, associated to the job. |
| Estimate total | amount | Deal | ST → HS | Subtotal as ServiceTitan reports it. |
| Sold / unsold / dismissed | dealstage | Deal | ST → HS | Sold → closed won; dismissed → closed lost. |
| Follow-up status | st_followup_status | Deal | ST → HS | Open, Unreachable, Contacted, Won, Dismissed. |
| Sold date | closedate | Deal | ST → HS | |
| Invoice total | st_lifetime_revenue | Contact / Company | ST → HS | Sum of invoices, computed in the integration layer. |
| Latest invoice date | st_last_invoice_date | Contact / Company | ST → HS | |
| Invoice balance | st_open_balance | Contact / Company | ST → HS | Optional. Confirm with finance. |
| Memberships & campaigns | ||||
| Membership | Membership | Custom object | ST → HS | Associated to customer and location. |
| Membership type | st_membership_type | Membership | ST → HS | |
| Membership status | st_membership_status | Membership | ST → HS | Active, Suspended, Expired, Canceled. |
| Membership end date | st_membership_end | Membership | ST → HS | Drives renewal workflows. |
| Campaign name and category | st_campaign_name, st_campaign_category | Contact | ST → HS | First and latest campaign on the customer. |
| HubSpot lead | Booking with campaign | Booking | HS → ST | Created through the CRM bookings API; confirm booking setup in discovery. |
ServiceTitan apps are registered in its developer portal and approved per tenant. Values ServiceTitan does not publish are marked for confirmation.
| Topic | ServiceTitan | HubSpot |
|---|---|---|
| Access model | App 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. |
| Authentication | OAuth 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. |
| Interfaces | v2 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 detection | Export 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 limits | 60 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. |
| Environments | Integration environment for build and test (a clone of production for existing customers) and production. | HubSpot sandbox for build; production portal at launch. |
| Sensitive data | Customer 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. |
Severity reflects impact on the SOW, not technical difficulty alone.
ServiceTitan sends appointment notices and can run marketing; HubSpot runs campaigns. Without a sender-of-record decision, customers get duplicates.
Homeowners and commercial accounts need different HubSpot shapes. Agree the rules, including multi-location commercial customers, before the build.
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.
New ServiceTitan campaigns appear over time. The integration flags any unmapped campaign so attribution reports stay complete.
Sending HubSpot leads into ServiceTitan as bookings needs configuration on the tenant. Confirm the booking path and default campaign in discovery.
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.
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.
HubSpot reports show booked jobs and invoiced revenue by campaign and channel, not just leads, so spend moves to what produces work.
Expiring memberships trigger renewal campaigns, and customers without a membership after a repair get a membership offer.
A completed job triggers a review request from HubSpot, timed by job type and business unit.
Service history by location and business unit drives tune-up, maintenance and replacement campaigns to the right households.
Commercial customers become companies with their locations, jobs and revenue, so account managers see the whole relationship.
The integration follows one customer through the service cycle. ServiceTitan runs the work; HubSpot runs the marketing and follow-up around it.
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 name | Label | Object | Type | Source / logic |
|---|---|---|---|---|
| st_customer_id | ServiceTitan Customer ID | Contact / Company | Single-line text | CRM customer key; unique |
| st_customer_type | Customer Type | Contact / Company | Dropdown | Residential or commercial |
| st_location_id | ServiceTitan Location ID | Service Location | Single-line text | CRM location key; unique |
| st_job_id | ServiceTitan Job ID | Job | Single-line text | Job key; unique |
| st_business_unit | Business Unit | Job | Dropdown | Job business unit |
| st_campaign_id | ServiceTitan Campaign ID | Job | Single-line text | Campaign on the job |
| st_followup_status | Estimate Follow-up Status | Deal | Dropdown | Open, Unreachable, Contacted, Won, Dismissed |
| st_lifetime_revenue | Lifetime Revenue | Contact / Company | Number (currency) | Sum of invoice totals |
| st_last_service_date | Last Service Date | Contact | Date | Latest completed job |
| st_next_appointment | Next Appointment | Contact | Date | Next scheduled appointment |
| st_membership_status | Membership Status | Membership | Dropdown | Active, Suspended, Expired, Canceled |
| st_membership_end | Membership End Date | Membership | Date | Drives renewal workflows |
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.
Based on public documentation. Each item marked for confirmation is verified against the client's ServiceTitan tenant during discovery.
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.
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.
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.
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.
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.