Understand the ServiceTitan Integration

This article explains how the ServiceTitan integration works, including the data flow, attribution logic, and technical implementation details.

Integration Architecture

The ServiceTitan integration operates through custom Zapier workflows that connect ServiceTitan and WhatConverts bidirectionally. Unlike direct API integrations, this Zapier-based approach requires you to configure separate automated workflows (called Zaps) for each type of data you want to sync between the platforms.

Each Zapier workflow monitors one platform for specific events, processes the data through multiple steps, including filters, searches, custom code, and sometimes AI analysis. Then creates corresponding records in the destination platform with the relevant information.

Data Flow Options

The ServiceTitan integration supports two data flow directions:

From ServiceTitan to WhatConverts

• New appointments trigger workflows that create leads in WhatConverts with booking details and customer information
• New invoices trigger workflows that create leads in WhatConverts with transaction values and revenue data
• These workflows typically involve 8-11 steps, including filters, searches, code processing, and AI analysis

From WhatConverts to ServiceTitan

• New leads trigger workflows that create customer records in ServiceTitan
• This workflow involves 3 steps, including duplicate prevention through customer search
• Helps maintain an up-to-date customer database in ServiceTitan with leads from marketing efforts

ServiceTitan to WhatConverts Workflow Structure

The appointments and invoices workflows follow a similar multi-step structure:

• Trigger: A new appointment or invoice is created in ServiceTitan
• Filters: The workflow checks whether the appointment or invoice meets specific criteria (such as having a positive total value or a valid job ID)
• Data Retrieval: Multiple ServiceTitan search steps retrieve related information, including customer details, contact information, job data, and job type information
• Data Processing: Custom JavaScript code and AI analysis format, and organize the retrieved data into the structure needed for WhatConverts
• Lead Creation: The final step sends the formatted data to WhatConverts, creating a new lead record with all relevant appointment or invoice details

WhatConverts to ServiceTitan Workflow Structure

The lead-to-customer workflow follows a simpler structure focused on duplicate prevention:

• Trigger: A new lead is created in WhatConverts
• Search: The workflow searches ServiceTitan for existing customers matching the lead's contact information
• Customer Creation: If no matching customer exists, the workflow creates a new customer record in ServiceTitan with the lead information. If a match is found, the workflow stops to prevent duplicates.

Attribution Logic

The ServiceTitan integration does not include inherent marketing attribution data when sending appointments and invoices to WhatConverts. Attribution depends entirely on whether WhatConverts has previously tracked a marketing interaction with that customer.

WhatConverts matches incoming ServiceTitan leads to existing tracked leads based on contact information (phone number or email address). If WhatConverts finds a previously tracked lead with matching contact details, the ServiceTitan lead inherits the first-click attribution from that original marketing touchpoint. This allows you to connect completed appointments and invoices back to the marketing source that originally generated the customer inquiry.

If no matching previously tracked lead exists in WhatConverts, the ServiceTitan lead will appear with direct attribution, indicating that WhatConverts does not have information about how that customer originally discovered your business.

Separate Workflows for Different Data Types

You must create and maintain separate Zapier workflows for each data type because each requires different trigger events, data retrieval steps, and formatting logic. The appointments workflow focuses on booking dates and service types, the invoices workflow emphasizes transaction values and revenue data, and the lead-to-customer workflow focuses on duplicate prevention and customer creation. This separation ensures that each workflow can properly process and format its specific data type for accurate record creation.

Custom Fields and Job Type Identification

For ServiceTitan to WhatConverts Workflows

The integration includes an AI-powered step that analyzes job type data to identify the most recently booked service. This ensures that leads in WhatConverts reflect the latest customer interaction rather than outdated or incorrect job information.

For WhatConverts to ServiceTitan Workflows

If you want to send custom data from WhatConverts to ServiceTitan custom fields, you need to:

1. Create the custom field in ServiceTitan first.
2. Edit the custom field and copy the field ID from the URL.
3. In your Zapier workflow, use a key-value pair where the key is the custom field ID and the value is the mapped field from WhatConverts.

Integration Limitations

The ServiceTitan integration has several important limitations to consider:

• Manual Workflow Setup: Unlike some plug-and-play integrations, the ServiceTitan integration requires you to manually configure each Zapier workflow with multiple steps and sometimes custom code.
• Separate Workflows Required: You must create and maintain distinct Zapier workflows for appointments, invoices, and lead-to-customer sync. Each workflow requires separate configuration and maintenance.
• Zapier Account Required: This integration relies on Zapier as the middleware platform, meaning you need an active Zapier account, and your workflows count against any applicable Zapier usage limits.
• No Native Attribution for ServiceTitan Data: When sending appointments and invoices from ServiceTitan to WhatConverts, leads created through this integration do not include attribution data unless WhatConverts has previously tracked a marketing interaction with that customer's contact information.
• Limited Custom Field Support: When sending leads from WhatConverts to ServiceTitan, you can only map to custom fields that already exist in ServiceTitan, and you must manually obtain field IDs from ServiceTitan URLs.

Related Topics

• What is the ServiceTitan Integration?
• Connect WhatConverts to ServiceTitan
• Send Appointments from ServiceTitan to WhatConverts
• Send Transactions and Sales Value from ServiceTitan to WhatConverts
• Send Lead Data from WhatConverts to ServiceTitan