Integration Flow Synchronization Logic Documentation

Third-party → CRM

Third-party data is first stored in a staging database for temporary holding. The staging database serves as a buffer to handle bulk or duplicate data synchronization from third-party sources.

For each data pull from a third party, the system compares the retrieved data with the staging database records (all fields are compared). Only modified data triggers synchronization via the integration flow, while unchanged data does not initiate synchronization.

Retry Mechanism:

1. Staging Table Retry (Single or Batch)
   The system calls the single-record query API to re-fetch data from the third party for synchronization.

2. Staging Database Retry
   The system does not re-pull data from the third party but reprocesses the existing staging data through the integration flow.
   Applicable Scenarios:

   • Scenario 1: No data changes, but the integration flow has been adjusted, requiring re-synchronization.
   • Scenario 2: No data changes, but partial synchronization failed, requiring reprocessing of failed records.

Historical Data Synchronization (Staging Database Comparison):

1. Time-based or Custom Condition Sync
   Data queried from the third party is compared with the staging database. Modified data triggers the integration flow, while unchanged data is skipped.

2. ID-based or CRM Data Range Sync
   Data queried from the third party bypasses staging database comparison and directly triggers the integration flow.

picture coming soon:

CRM → Third-party

Retry Mechanism:

All retries re-query data from the CRM and trigger the integration flow for synchronization.