6. Notification Component

CRM -> Third-Party

Scenario example: A salesperson updates data in the CRM. When the data successfully syncs to a third-party system, the system notifies the data creator in Chats. If the sync fails, and the failure reason (from the staging table’s status detail) contains the keywords “required field” or “required item”, the system pushes that failure to the salesperson to indicate that missing required information caused the failure and that they must complete the data.

You can configure it as shown below:

1. Notification condition logic: - When data sync fails, only notify if the error message contains the keywords “required field” or “required item”. - Also notify when CRM write-back fails or when a post-sync function execution fails. - Sync failure, CRM write-back failure, and post-sync function failure are combined with OR — if any one occurs, send a notification.

2. Notification channels Supports Chats, email, and SMS. Note: email and SMS require your organization to enable the corresponding service and ensure recipients have an email address or phone number set.

Email service: https://www.fxiaoke.com/XV/UI/manage#crmmanage/=/module-sysemail

SMS service: https://www.fxiaoke.com/XV/UI/manage#crmmanage/=/module-smsmanage

Recipient scope logic: For CRM -> ERP direction, you can choose employees and Departments, and you can also choose Creator, Owner, and Last Modifier — these map to the Creator, Owner, and Last Modifier on the Primary Object being synchronized in the current integration flow.

Third-Party -> CRM

Scenario example: A user creates a record in a third-party system. After synchronization completes, whether success or failure, the CRM team receives a notification in Chats.

Configure as shown below:

Recipient selection logic: Because notifications are delivered via CRM Chats, recipients must have corresponding CRM user accounts.

In addition to choosing employees and Departments, selectable data-related user fields come from personnel fields that are mapped between the integration flow’s Third-Party object user fields and the CRM object user fields.

Similarly, if you use email or SMS notifications, your organization must enable those services and recipients must have an email address or phone number configured.