Docs›Integrations›Jobtread

JobTread

JobTread is CDB's construction management platform — used for project bids, contracts, change orders, and document management. Field reads JT data via the Phil agent.

What JobTread Does

  • Bid management — track proposals sent to GCs
  • Contracts — store signed agreements
  • Change orders — document scope changes
  • Project files — PDFs, drawings, photos
  • Vendor management — trade partner records

JobTread is the "official" record for contracted work. Field is the operational day-to-day platform.

How Phil Uses JobTread

Phil (the CFO/ops agent) is the bridge between JobTread and Field:

  • Queries JT via the JT API for job status, documents, and contacts
  • Cross-references JT jobs with Field jobs
  • Surfaces relevant JT info when David asks questions
  • Does not write to JT (it's treated as read-only by the agents)

Credentials

  • JobTread Grant Key: ~/.openclaw/workspace/secrets/jobtread-grant-key.txt
  • Phil uses this key to authenticate JT API requests

JT ↔ Field Job Mapping

Jobs exist in both systems with different IDs. The mapping is maintained informally (by name/address). A future improvement would be to store jobtread_job_id on Field jobs for cross-referencing.

Accessing JobTread

  • Web app: app.jobtread.com
  • Login: David's credentials (stored in 1Password)
  • Phil can retrieve specific JT data on request: "Phil, pull the contract for the Castro job"

What JT Does NOT Do

  • JT doesn't sync contacts to Google (Field does that)
  • JT doesn't send SMS (Twilio/Field does that)
  • JT doesn't track daily time entries (Crew does that)
  • JT doesn't handle bank transaction coding (Finta/Field does that)

Future Integration Ideas

  • Auto-create Field jobs from JT when a bid is won
  • Sync JT contacts to Field contacts table
  • Pull JT change orders into Field job detail pages