JobsiteOn

Data Sync Overview

How data synchronization works across all JobsiteOn integrations, including sync directions, conflict resolution, and monitoring.

Ethan Rivera
Written by Ethan RiveraUpdated 2 days ago2 min readBeginner

What this guide covers

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.

Sync directions

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.

How records are linked

When two systems sync, records are linked by a matching key:

  • Contacts -- matched by email address.
  • Invoices -- matched by invoice number.
  • Pricebook items -- matched by item name.

Once linked, changes to either record propagate during the next sync cycle.

Conflict resolution

When the same record is changed in both systems between syncs:

  1. The system compares timestamps.
  2. The most recent change wins.
  3. The overwritten version is logged in the sync log.

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.

Sync frequency

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)

Monitoring sync health

  • Sync log -- check per-integration sync logs for errors.
  • Email alerts -- enable error notifications in integration settings.
  • Dashboard -- the integrations page shows the last sync time and error count for each connection.

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?

Related Articles