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.
Automation platformsZapierMake
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.
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.
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.
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.
| ServiceTitan | Direction | Krokul | When |
|---|---|---|---|
| Customer, Customer Contact | Krokul ↔ ServiceTitan | Client company, contact | A client company or customer is created or updated |
| Location | Krokul → ServiceTitan | Site address of the client company | A deal with a new site is won |
| Job or Booking | Krokul → ServiceTitan | Won deal | A deal is won in a service pipeline |
| Estimate (New Estimate, Updated Estimate) | ServiceTitan → Krokul | Deal with the estimate total, stage won when sold | A technician writes or sells an estimate |
| Updated Job | ServiceTitan → Krokul | Deal stage, task for the account manager | A job is completed or canceled |
| Invoice | ServiceTitan → Krokul | Invoice document on the deal | An invoice is created |
| Payment | ServiceTitan → Krokul | Payment on the deal | A payment is posted |
| Customer Note | Krokul → ServiceTitan | Comment from the deal | A manager adds a note for the field team |
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.
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.
No. Dispatch and technician schedules stay in ServiceTitan. Krokul sends the job request with the customer, location and deal details, and ServiceTitan books it.
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.
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.
Tell us which service you use and what should move between it and Krokul. We reply with the way to do it and when it will be ready.
Request received. We reply to your email.
ServiceTitan is a trademark of ServiceTitan, Inc. Krokul is not affiliated with ServiceTitan.
