Data Sync Overview
How data synchronization works across all JobsiteOn integrations, including sync directions, conflict resolution, and monitoring.
How data synchronization works across all JobsiteOn integrations, including sync directions, conflict resolution, and monitoring.
This guide provides a high-level overview of how data synchronization works across all JobsiteOn integrations. Understanding the sync architecture helps you predict behavior and troubleshoot issues.
Integrations use one of three sync patterns:
| Pattern | Description | Example |
|---|---|---|
| One-way push | JobsiteOn sends data to the integration | Invoices to QB |
| One-way pull | The integration sends data to JobsiteOn | Calendar events |
| Bi-directional | Data flows both ways | Contacts to QB |
Screenshot: A diagram showing three sync patterns with arrows: one-way push, one-way pull, and bi-directional between JobsiteOn and external systems.
When two systems sync, records are linked by a matching key:
Once linked, changes to either record propagate during the next sync cycle.
When the same record is changed in both systems between syncs:
Animation: A split-screen showing a contact edited in JobsiteOn at 2:00 PM and the same contact edited in QuickBooks at 2:30 PM, with the QuickBooks version winning.
| Integration | Push frequency | Pull frequency |
|---|---|---|
| QuickBooks | Real-time | Every 15 min |
| Calendar | Real-time | Every 15 min |
| Zapier | Real-time | N/A (triggers) |
| API/Webhooks | N/A | N/A (on-demand) |
Tip: Think of bi-directional sync as a conversation between two systems. Keep one system as the primary source of truth for each data type to avoid conflicts.
Note: Sync frequency can be adjusted in each integration's settings page. See the specific integration guide for details.
Did this answer your question?