Coming Soon

Native ServiceTitan integration is not yet available. The page below describes how the integration would work. Build priority is driven by customer votes. Tell us your use case and we'll prioritize.

Vote for ServiceTitan →

INTEGRATION · PLANNED

PostKnock + ServiceTitan

ServiceTitan owns dispatch, invoicing, and the customer record. PostKnock owns the win-back postcard wave and the front-desk call queue ServiceTitan's email module can't replicate.

What ServiceTitan is

ServiceTitan is the dominant field-service platform for HVAC, plumbing, and electrical contractors over $1M in revenue. It runs dispatch, invoicing, technician routing, and customer history. Its API is mature and well-documented.

Why postcards on top of ServiceTitan

ServiceTitan's marketing module is built around email and Google Local Services Ads. It does not run the kind of high-touch, mileage-and-equipment-driven postcard cadences that win back inactive customers and book seasonal tune-ups. Postcards plus a coordinated callback are what most HVAC shops are sending in addition to ServiceTitan today. PostKnock makes that workflow native.

How a PostKnock + ServiceTitan integration would work

Contact sync

Pull-based via the ServiceTitan REST API. PostKnock would sync the Customer and Job objects nightly, scoped to customers whose last completed job is past your tune-up threshold. Equipment age (from Equipment object) drives mileage-style triggers. One-way for MVP. ServiceTitan stays the system of record.

Trigger types

Data fields mapped

ServiceTitan field PostKnock field
Customer IDExternal ID
Name / AddressFirst, Last, Mailing address
Last Job Datelast_service_date
Equipment List + AgeCustom fields: equipment_age, equipment_type
TagsSegment tags (preserved)
Lifetime ValueCustom field: ltv (used for VIP segments)

Status

Planned. Build prioritization is driven by customer demand. The more votes a connector gets, the sooner we ship it.

Vote. Tell us your use case

FAQ

Can I export from ServiceTitan manually today?

Yes. The Reports module exports customer lists as CSV with Last Job Date, equipment, and tags. PostKnock auto-maps the standard columns. A monthly export is the standard manual workflow today.

Will it sync two-way?

Phase 1 is one-way. Phase 2 plans to write a Customer Note back to ServiceTitan when a postcard wave fires, so dispatch can see it.

Cost?

No integration fee. Standard per-postcard pricing.

Does this conflict with ServiceTitan's Marketing Pro?

No. Marketing Pro covers email and Google ads. PostKnock is the physical-mail + outbound-call layer. Most shops run both.

How fast can I ship a wave today via CSV?

Most shops launch their first wave within 30 minutes of signing up: export CSV, upload, pick the HVAC playbook, customize, send.

Use PostKnock today, native sync later

Export your contact list from ServiceTitan as CSV, upload to PostKnock, and ship a postcard wave this week. When the native integration goes live, your account is already set up.

Start Free