# ServiceTitan + Krokul CRM

Yes. Krokul CRM integrates with ServiceTitan. A commercial deal won in Krokul opens the customer, the service location and the first job in ServiceTitan. Estimates that technicians sell on site come back to Krokul as deals, and every ServiceTitan invoice and payment lands on the client company, so the sales team sees contract value and receivables in one place.

**Status:** Via API and webhooks. **Automation platforms:** Zapier, Make.

## What your team gets

### A signed contract becomes a job

A facility manager signs a maintenance agreement, and the deal moves to won. Krokul searches ServiceTitan for the client company, creates the Customer and the Location for the site address when they are missing, and books the first Job in the business unit set for that pipeline. The ServiceTitan job ID is stored on the deal as an external key, so later events find the deal without guessing.

### Technician estimates reach the account manager

During a visit a technician writes an Estimate for a replacement unit. The New Estimate trigger creates a deal in Krokul for the same client company with the estimate total and a link to the job. When the Updated Estimate trigger reports the estimate as sold, the deal moves to won. Open estimates get a follow-up call.

### Invoices and payments close the loop

Each New Invoice from ServiceTitan becomes an invoice document on the deal with the job number and the amount due. A New Payment records a payment in Krokul against that invoice. Once payments cover the total, Krokul fires invoice.paid, and overdue invoices show up in the debtor list and in the DSO report for the client company.

### Customers stay matched

A customer added by the call center in ServiceTitan arrives in Krokul as a client company with its contact, and a client company created in Krokul gets its Customer in ServiceTitan. Both sides keep the other ID, so a renamed customer updates instead of duplicating.

## What moves between ServiceTitan and Krokul

| ServiceTitan | Krokul | Direction | When |
|---|---|---|---|
| Customer, Customer Contact | Client company, contact | Krokul ↔ ServiceTitan | A client company or customer is created or updated |
| Location | Site address of the client company | Krokul → ServiceTitan | A deal with a new site is won |
| Job or Booking | Won deal | Krokul → ServiceTitan | A deal is won in a service pipeline |
| Estimate (New Estimate, Updated Estimate) | Deal with the estimate total, stage won when sold | ServiceTitan → Krokul | A technician writes or sells an estimate |
| Updated Job | Deal stage, task for the account manager | ServiceTitan → Krokul | A job is completed or canceled |
| Invoice | Invoice document on the deal | ServiceTitan → Krokul | An invoice is created |
| Payment | Payment on the deal | ServiceTitan → Krokul | A payment is posted |
| Customer Note | Comment from the deal | Krokul → ServiceTitan | A manager adds a note for the field team |

## How to connect today

### Krokul app in Zapier or Make

1. Connect the Krokul app with a Krokul API key. Connect ServiceTitan with the Client ID, Client Secret and Tenant ID that a ServiceTitan admin generates under API Application Access.
2. Start from the Krokul trigger Deal Won and use the ServiceTitan actions Create Customer, Create Location and Create Job, or Create a Job in Make.
3. Add a second flow from the ServiceTitan triggers New Invoice and New Payment to the Krokul actions Create Document and Create Payment.
4. Add a third flow from New Estimate to the Krokul action Create Deal, with the job number as an external key.

### Custom flow through the Krokul API and webhooks

1. Register an app in the ServiceTitan developer portal to get the ST-App-Key, choose the API scopes, and have the tenant admin connect it and generate the client secret.
2. Subscribe a Krokul webhook to card.won with a pipelineUuid filter, verify x-crm-signature, read the deal with card/api-read and create the customer, location and job in ServiceTitan.
3. Request a client_credentials token before each batch, poll ServiceTitan for new estimates, invoices and payments by modified date, and resolve each record with externalRef/api-resolve.
4. Write results with card/api-create, document/api-create and payment/api-create, then store the ServiceTitan IDs with externalRef/api-upsert.

**Triggers:** New Customer; New Location; New Booking; New Job; Updated Job; New Appointment; New Estimate; Updated Estimate; New Invoice; New Payment; New Project; New Purchase Order; Watch Jobs.

**Actions:** Create Customer; Update Customer; Create Customer Contact; Create Customer Note; Create Location; Create Booking; Create Job; Update Job; Create Project; Create Task; Apply Tag to Customer; Search Customers; Search Invoices; Search Estimates; Create a Job Note; Upload an Attachment; Make an API Call.

### For integrators

ServiceTitan issues short-lived bearer tokens through the client credentials grant, and every call also carries the ST-App-Key header of the registered app. An Integration environment with a copy of tenant data serves for testing before production. Krokul offers a public REST API with scoped keys, signed webhooks with a delivery log and redelivery, external keys for ServiceTitan customer, job and invoice IDs, and a sandbox company.

[API documentation](https://app.krokul.com/api/v1/docs)

## Questions and answers

### Does Krokul integrate with ServiceTitan?

Yes. Krokul integrates with ServiceTitan through the Krokul app in Zapier and Make and through the Krokul API and webhooks together with the ServiceTitan API.

### Which ServiceTitan accounts can connect?

ServiceTitan tenants with API access, which ServiceTitan includes in the Works and Legacy packages. A tenant admin connects the app and generates its client secret.

### Does Krokul schedule technicians?

No. Dispatch and technician schedules stay in ServiceTitan. Krokul sends the job request with the customer, location and deal details, and ServiceTitan books it.

### How do field estimates reach the sales pipeline?

Each new ServiceTitan estimate opens a deal in Krokul for the same client company, and the deal moves to won when the estimate is sold.

## Limits

Dispatch, technician schedules, the pricebook and work on the job stay in ServiceTitan. ServiceTitan opens its API to tenants on the Works or Legacy package, and a tenant admin connects each app under API Application Access.

## Related services

- [Jobber](https://krokul.com/en/integrations/jobber/index.md)
- [Housecall Pro](https://krokul.com/en/integrations/housecall-pro/index.md)
- [QuickBooks Online](https://krokul.com/en/integrations/quickbooks-online/index.md)
- [DocuSign](https://krokul.com/en/integrations/docusign/index.md)
- [Stripe](https://krokul.com/en/integrations/stripe/index.md)
- [PandaDoc](https://krokul.com/en/integrations/pandadoc/index.md)

[Field service](https://krokul.com/en/integrations/category/field-service/index.md)

ServiceTitan is a trademark of ServiceTitan, Inc. Krokul is not affiliated with ServiceTitan.

Updated: 2026-10-15

---

App: https://app.krokul.com/ · API: https://app.krokul.com/api/v1/docs