Procore Integration Architecture
Read-only, one-way. Be able to draw it on a whiteboard.
The 60-second explanation
Jet.Build pulls data from Procore in one direction, read-only. Your customer keeps using Procore exactly as they do today. We pull Procore data into Jet.Build so they can layer our reporting, dashboards, and portfolio-level views on top.
We never write back. We never modify Procore data. Their Procore environment stays untouched.
This eliminates the #1 GC objection: "I don't want to fight my subs over moving off Procore." They don't have to. Subs keep working in Procore. Jet.Build is the layer the owner, PM, or executive uses on top.
What syncs
- Projects (metadata, status, dates)
- Drawings (current set, version history)
- RFIs (status, dates, assigned, response)
- Submittals (status, approval chain)
- Daily logs
- Photos
- Documents (folder structure, current revision)
- Financials where customer-permitted (contracts, change orders, pay apps)
What does NOT sync
- Tasks / to-dos
- Internal Procore notes and comments
- User permissions (we manage our own)
- Customer-defined custom fields (case-by-case)
- Anything Procore doesn't expose via API
Authentication & security
- OAuth 2.0 connection at the customer's Procore company level
- Jet.Build never sees Procore passwords
- Customer can revoke access any time from their Procore admin panel
- Data in transit: TLS 1.2+
- Data at rest: encrypted