ServiceTitan setup guide
Review credentials, connection steps and the first sync-rule workflow.
Connect two platforms, map your fields once, and let synkazo keep them in sync.
Connect ServiceTitan, verify credentials, review field mappings, and configure your first synkazo sync rule.
Still comparing options? Review the ServiceTitan and HubSpot integration page for supported directions, objects and setup requirements.
Set up the ServiceTitan source connection, verify it, and configure your first synkazo sync rule.
Install synkazo for HubSpot first, then choose ServiceTitan as the source platform for your project. The source platform and project sync mode are permanent choices for that project.
From Connections, choose ServiceTitan as the source if the project still asks you to pick one, and select Sync Mode (One Way or Two Way — this cannot be changed later).
On the Connections page, select Connect on the ServiceTitan card, then Manual Setup.
Enter the App Key, Client ID, Client Secret and Tenant ID.
Select Verify Credentials and continue once synkazo confirms the connection.
When you create a sync rule, synkazo loads the objects and fields available to the connected account. Current connector coverage includes:
The object selector in synkazo is authoritative for your account; availability can depend on connector access and your synkazo plan.
From Connections, select Next step: Create Sync Rule.
Choose the ServiceTitan source object and the HubSpot destination object.
Name the rule and choose the job behavior: New Records, Updated Records, or New & Updated.
Review the proposed field mapping, adjust anything that needs a decision, and choose one mapping as the match field.
Set a schedule for a one-way rule (two-way rules sync automatically), set Start As Active, and create the rule.
Select Start Sync, then Sync All to establish the first complete baseline, and confirm the result in Run History.
Check every value is copied without trailing spaces, and that the API application is active in the source platform. For ServiceTitan, the App Key, Client ID, Client Secret and Tenant ID must come from the same API application.
Open the activity log for that sync rule. Each skipped or failed record is listed with the reason — most often a required HubSpot property is missing from the mapping.
This means no match field was set, or the match field is empty on some records. Set a match field with a reliably-populated value, such as email or an ID field.
The app was uninstalled in HubSpot or its permissions changed. Click Reconnect in the dashboard — nothing is lost, and mappings are preserved.
Field types must be compatible. If synkazo flags a mismatch it will propose a conversion — accept it, or map to a different property with a matching type.
Continue evaluating
Review credentials, connection steps and the first sync-rule workflow.
Compare a maintained connector with Zapier-style workflows and other approaches.
See the documented problem, mapping approach and intended operational outcome.
Compare plan limits and prepare the questions needed for an accurate scope.