ServiceTitan
Planned: book and dispatch jobs, check the schedule and close out work in ServiceTitan by text. Requires ServiceTitan approval.
Not available yet. This page describes what's planned for ServiceTitan. Ask in your thread and we'll text you when it's ready.
Status: planned — not available to connect in Tack yet. These steps prepare the integration; creating vendor credentials does not enable it in the app.
Planned workflows
Section titled “Planned workflows”Planned for ServiceTitan:
| You text | What would happen in ServiceTitan |
|---|---|
| “Book the Hendersons Tues 2pm, no cooling” | Creates the job and books the appointment |
| “What’s on today’s schedule?” | Lists today’s appointments and assigned techs |
| “Job done at Henderson, replaced capacitor” | Adds the summary and completes the job |
These are intended workflows, not a guarantee that every operation is exposed by the vendor. Each must pass the API and permission checks below before release.
Before you start
Section titled “Before you start”Assign a customer tenant administrator and a developer with ServiceTitan developer access. Verify the customer’s API entitlement with ServiceTitan; do not assume a plan name guarantees it.
Developer setup — once
Section titled “Developer setup — once”- Register through the ServiceTitan developer program and use the assigned integration environment. Third-party developers must not build their app inside a customer’s environment. Developer FAQ.
- In My Apps → Register New App, supply the app details and select only the API scopes needed by the planned actions.
- Choose the developer-managed client-credentials option if the developer will manage tenant credentials. Keep the app key and environment configuration in server-side secret storage.
Customer setup — repeat for each tenant
Section titled “Customer setup — repeat for each tenant”- Record the tenant ID and whether it is integration/test or production.
- The tenant admin opens Integrations → API Application Access → Connect New App, finds the registered app and approves its access.
- If the tenant is not available to the developer, resolve tenant access through the developer portal before continuing.
- After the tenant enables the app, generate its client ID and secret. Credentials are unique to the tenant and environment; store that binding with the connection.
- Obtain an access token using the documented client-credentials flow and use the matching environment and app key for API calls.
Follow ServiceTitan’s client ID and secret guide for the registration and tenant handoff.
Verify write access
Section titled “Verify write access”Select one test customer/job and an operation that the approved scopes actually support. Read it, perform an agreed reversible update and read it back. Record tenant ID, endpoint and result. Repeat authorization for production; successful integration-environment credentials do not establish production access.
Disconnect and troubleshoot
Section titled “Disconnect and troubleshoot”Have the tenant admin disable/remove the app’s access in API Application Access, then retire its stored credentials. Confirm a subsequent request is denied. For failures, check tenant/environment alignment, app enablement, token expiration, app key and endpoint scope separately. Any new scope needs the vendor’s approval/update process before retesting.
Who completes the work?
Section titled “Who completes the work?”An agent/developer can implement the connector, field mappings and automated checks. A customer administrator must authorize account access and permissions; the vendor must approve any restricted partner access. A business operator verifies the test records before production use. Follow the shared setup and release checklist for credential handling, approval gates and launch checks.
Setup guidance reviewed October 23, 2026. Vendor menus and entitlements can change; unresolved details are called out above.