Procore Governed Connector Architecture

Overview

Separate identity, tenant routing, ingestion, hydration, reconciliation, mutation approval, and audit evidence. Procore webhooks improve freshness but REST remains the data source, so the architecture must tolerate duplicates, delays, missed notifications, and partial writes.

Prerequisites

• Source and destination ownership, data domains, classification, and residency constraints
• Freshness, completeness, recovery, and deletion objectives
• OAuth grant, DMSA permission map, environment matrix, and endpoint inventory

Instructions

Step 1: Draw trust boundaries

Identify token service, ingress, queue, workers, state store, outbound adapters, audit sink, and operator interface. Carry company and project context as immutable job attributes.

Step 2: Separate adapter contracts