Published at: 2025-10-30
6. Notification Component
CRM -> Third-party Systems
Use Case Example:
When sales reps operate data in CRM, the system notifies them via CRM Chats upon successful synchronization with third-party systems.
If synchronization fails due to missing mandatory fields (indicated by error messages containing keywords like “required fields” or “mandatory fields”), the system pushes failure reasons (status details from intermediate tables) to the sales reps, prompting them to supplement the data.
Configuration Example:
picture coming soon:
Notification Logic:
Notifications are triggered only when synchronization fails due to errors containing “required fields” or “mandatory fields.”
Notifications are also sent for exceptions during CRM write-back or post-sync function execution.
Notifications occur if any of the following exceptions arise (OR logic): sync status failure, CRM write-back exception, or post-sync function exception.
Notification Methods:
Supports Chats, email, and SMS.
Note: Email and SMS require prior service activation by the enterprise. Ensure recipients have configured email addresses/phone numbers.Recipient Selection Logic (CRM → ERP):
In addition to employees and departments, notifications can target:Creator, Owner, or Last Modified By of the Primary Object in the current integration flow.
picture coming soon:
Third-party Systems -> CRM
Use Case Example:
When sales reps create data in third-party systems, CRM personnel are notified via CRM Chats upon sync completion (regardless of success or failure).
Configuration Example:
picture coming soon:
Recipient Selection Logic:
- Recipients must have CRM accounts to receive Chats notifications.
- Beyond employees and departments, options include personnel fields mapped between:
- Third-party object’s personnel fields and CRM object’s personnel fields in the current integration flow.
Note: Email/SMS notifications require service activation and recipient contact details.