ServiceTitan Zapier integration

Overview

Integrating ServiceTitan and Zapier enables you to connect your ServiceTitan data to third-party applications you use to operate your business. You can then automate mundane tasks, such as adding job events or information from ServiceTitan to your Google Calendar, maximizing daily efficiency for your teams. Zapier allows for no-code integration, which means you don't need heavy programming to use it.

Things to know

• Zapier functionality is not officially supported by ServiceTitan and is made available on an 'as is' basis and without warranty at users' own will and risk as contemplated by our Terms of Use. ServiceTitan will not be liable for any damages arising from your use of Zapier, for any resulting changes including deletions to your data, or for the failure of any feature or functionality. 

• A Client ID and Secret Key are required to use this integration. To obtain this information, see Generate Client ID & Secret Key.

• A trigger is an event that starts a Zap.

• When a trigger occurs, an action is performed to move the data and complete the Zap.

• Zapier monitors ServiceTitan for a trigger to begin an action.

How does the ServiceTitan–Zapier integration work

By implementing a connection between ServiceTitan and Zapier you can bring data generated by third-party applications into ServiceTitan and pass ServiceTitan data directly to your preferred applications through a Zap, generated by the Zapier web-based service. For example, a Zap can automatically create a new job booking in ServiceTitan when you receive a lead in your inbox, giving instant visibility to your team without having to leave the ServiceTitan application.

The Zapier application leverages our ServiceTitan API services, currently made up of data, giving you the ability to push data into ServiceTitan to create a task, job note, attachment, or book a job.

ServiceTitan–Zapier connection with third-party applications

Here are some example integrations with third-party applications you can use once you've set up the integration:

• Slack Alert: This specific Zap lets you see if there's a remaining balance on an invoice by sending a zap that sends an alert to the Slack application. For how to use this Zap, see Zapier app integration <> Slack Alert.

• Google Calendar: Add scheduled jobs from ServiceTitan to your Google Calendar through this Zap. After activated, this integration lets you view scheduled jobs in ServiceTitan in your Google Calendar application. For how to set up this Zap, see Zapier app integration <> Google Calendar.

Getting started

To use the ServiceTitan Zapier integration, you must be on the Works or Legacy package.

To get started, fill out the ServiceTitan Zapier registration form. A ServiceTitan representative will contact you after we receive your request and let you know the next steps. 

The person filling out the registration form must be a ServiceTitan administrator user. If a third-party individual is requesting access to this integration on behalf of your organization, we need a ServiceTitan administrator from your organization to verify this request.

You do not need an integration environment to connect to Zapier. You just need to generate a client ID and secret key to get access.

Create a Zap using ServiceTitan

Before creating your first Zap, you will need to create a Zapier account or sign into an existing account.

1. Open zapier.com.

2. Click Create Zap.

3. Search for and select ServiceTitan (3.0.X).

4. Choose Trigger or an Action, then click Continue.
   
   

5. Connect your ServiceTitan account.

6. To create a new account:

   1. Enter your Tenant ID, Client ID, and Client Secret.

   2. From the Environment to use dropdown, select the production environment.

7. Click Yes, Continue to ServiceTitan.
   

Generate Client ID and Client Secret

If you are connecting your ServiceTitan account to Zapier for the first time you will need your Client ID and Client Secret. You can generate your Client ID and Client Secret in your Go environment

1. Open go.servicetitan.com.

2. Click Settings > Integrations > API Application Access.

3. Click Connect New App.
   

4. Select Zapier 3.0.X>Connect
   

5. Review the scopes requested. Choose No restriction from the Booking Provider dropdown.
   

6. Click Allow Access.
   

7. Your Tenant ID and Client ID appear. In the Client Secret section, click Generate.
   

8. Your Client Secret appears. Copy the information for use when connecting on zapier.com.
   

API errors

This section describes what you can do if you encounter errors.

500 errors

These types of errors may be caused by one of the following situations:

• API call resulted in an error: This may occur when the system is sending data to ServiceTitan, such as booking or task management information, using a Zapier action.

• ServiceTitan API is down: This may occur when any ServiceTitan API endpoint is not available.

Note: This information is for the ServiceTitan–Zapier integration only. For errors that occur in the Zapier application, visit www.zapier.com/help.

Troubleshoot API errors

Use this workflow to help you troubleshoot errors that occur when using the ServiceTitan–Zapier integration.

Note: A valid ServiceTitan Client ID & Secret Key is required. Follow the steps in the sequence in which they appear.

Step 1: Interrogate and identify the cause

1. In Zapier, click Zaps.
   

2. Find the Zap causing the error and click the chevron.

3. Click Task History.

Step 2: Identify the step in the integration that has an error

Once you're in Task History, look into the details. In this example, the Booking creation step is where the error occurred.

You can view this in the details of the API call as you're looking at the step logs.

Step 3: Fix the error

Using the same example in Step 2, based on the logs found, you can see that the type of error was identified as UniqueConstra. This tells you that the Source ID of the call was not unique. In this Booking-related error, every booking must include a unique identifier as noted in the description field.

Once you correct this, you can turn on the Zap to replay which means the system will retry it with your newly added correction.