1. "Source System" Component

1.1 [Timer] Polling Frequency

When you choose to fetch third-party data on a schedule using the “Query” method, you must further configure the polling frequency for “Batch Query”.

Option A: Configure polling by selecting UI options. Use this for common simple scheduling scenarios:

1. Query every 10 minutes between 7:00 AM and 11:00 PM daily — configuration example:

Queries by hour follow the same logic (for example, every 2 hours).

Execution times: 7:00, 7:10, 7:20 … up to 22:50 every day.

1. Query once per day at 11:00 PM — configuration example:

1. Query once weekly on Monday at 11:00 PM — configuration example:

You may choose any day from Monday to Sunday; multi-select is supported.

1. Query once monthly on the 2nd at 11:00 PM — configuration example:

You may choose any date from 1 to 31; multi-select is supported.

Option B: If Option A cannot meet your needs and you require a more customized polling schedule, configure the schedule using a Cron expression.

Cron expression overview

A Cron expression is a space-separated string. The typical structure is: Seconds Minutes Hours Day-of-Month Month Day-of-Week Year.

Note: - Because the Integration Platform’s polling frequency must be between minute-level and year-level, you do not need to set Seconds or Year fields in the Cron expression. - Constraint validation: the Minutes field enumeration cannot contain more than 10 values.

Field descriptions

Each field normally uses numbers, but the following special characters are also supported:

(1) * — matches any value for the field. For example, * in the Hours field triggers every hour.

(2) ? — no specific value. Only valid for Day-of-Month and Day-of-Week. If you specify a concrete value for one of these fields, the other must be set to ?.

(3) - — range. For example, 5-20 in Hours means every hour from 05:00 through 20:00.

(4) / — step values. For example, 1/5 in Day-of-Month means every 5 days starting on day 1 (1st, 6th, 11th, …).

(5) , — list of values. For example, 5,20 in Hours means trigger at 05:00 and 20:00.

(6) L — last. Only valid in Day-of-Week and Day-of-Month. For example, 5L in Day-of-Week means the last Thursday of the month.

(7) W — nearest weekday (Mon–Fri). Only valid in Day-of-Month. The system triggers on the nearest weekday to the specified date. For example, 5W: if the 5th is Saturday → triggers on Friday the 4th; if the 5th is Sunday → triggers on Monday the 6th; if the 5th is a weekday → triggers on the 5th. W will not search across month boundaries.

(8) # — specifies the nth weekday of the month. Only valid for Day-of-Month. For example, 4#2 means the second Wednesday of the month.

Common expression examples

“59 11 * * 1,2” — Runs at 11:59 on Mondays and Tuesdays “0 10,14,16 * * ?” — Runs daily at 10:00, 14:00, and 16:00 “15 10 L * ?” — Runs at 10:15 on the last day of every month “15 10 ? * 6L” — Runs at 10:15 on the last Friday of every month “15 10 ? * 6#3” — Runs at 10:15 on the third Friday of every month

1.2 [Trigger Events] Mapping Logic Between Source System Triggers and Target System Actions

Single Object

CRM -> Third-party System

1. The CRM system automatically notifies the Integration Platform of object-level events such as create, update, and delete. Therefore, users do not need to configure event triggers here. If an integration flow for this object is enabled, the flow will execute synchronization.

2. For records created in CRM: - If the target system action has “Create” checked, the platform will issue a Create to the target system (subject to the synchronization data scope). - If “Create” is not checked, the target system receives no action.

3. For records updated in CRM, the platform does not always call the target system’s Update action; it depends on whether the Integration Platform’s mapping table (the “sync data” list on the integration flow details page) already contains an ID mapping between the source and target records. - If no mapping exists, the Integration Platform treats the target as not having the record and issues a Create (if Create is unchecked, no action). - If a mapping exists, the Integration Platform treats the target as having the record and issues an Update (if Update is unchecked, no action).

Configure actions appropriately according to the Integration Platform’s logic.

If you want to synchronize only records created after a specific time, filter by Created Time or another timestamp in the data scope, or ensure the mapping table contains ID mappings for historical records.

Third-party System -> CRM follows the same logic in reverse.

When deciding which API type to call, consider both the configured actions and the mapping-table data.

1.3 Push Actions

1. The push API supports real-time pushes.
2. You can select which fields from the target object should be returned; those fields will be included in the API response data parameter.

1.4 Source System: CRM Component

Configure whether importing CRM data triggers synchronization

Configuration path: Integration Flow → Edit → CRM as Source Component

Note: This setting is at the object level and applies uniformly to all flows for this object.

Which field changes trigger update sync

Configuration path: Integration Flow → Edit → CRM as Source Component

Default behavior: The system triggers synchronization when fields that are within the data scope and included in field mappings are edited.

Custom configuration: If the default behavior does not meet your needs, you can select specific fields; only changes to the selected fields will trigger synchronization.