Record updates mean processing the individual record that changed. They do not mean repeatedly downloading an entire organization. Manual migration and manual record exchange remain separate.
Watch the lesson
Activate deliberately
- Connect the intended Zoho organization through Zoho CRM or Zoho Desk.
- Choose Authorize event access and approve the additional notification/webhook-management scope.
- Verify record mappings and, for Desk, the department and single field authority.
- Select permitted incoming and/or outgoing record directions and choose Save record updates.
- Check registration state, CRM subscription expiry where shown and recent delivery receipts.
- Change one representative test record, inspect the corresponding record in the destination and review its receipt.
Use Pause record updates to stop the configured event processing. Pausing does not roll back prior imported or changed records. Reauthorization or mapping changes may require a fresh review before updates resume. Connection alone never enables all directions.
Supported event scope
| Source event | Result |
|---|---|
| Zoho CRM Contact created/edited | Read and process that exact Contact ID |
| Supported Nviti contact fields created/edited | Queue the permitted outgoing Contact operation after commit |
| Signed Zoho Desk ticket added/updated | Process the exact mapped ticket in the verified department |
| Existing mapped Nviti ticket changed | Queue an outgoing update only under the selected Desk field authority |
Other CRM modules and Desk comments, files, identity changes and deletions are outside this layer. A callback cannot choose another tenant or supply an arbitrary URL for Nviti to fetch. Authentication verifies the connection-specific CRM secret/channel or Desk signature and organization.
Understand receipts
The receiver journals accepted IDs and returns promptly. Redis workers process records in the background and recheck current plan, owner, role, company, mappings and direction. A received callback is not a completed destination update. Inspect pending, completed/no-change, blocked, conflict, uncertain or failure information as applicable to the displayed receipt.
Provider echoes are suppressed through source/baseline tracking rather than sent back endlessly. Recovery redispatches durable pending local receipts and renews due CRM notification subscriptions; it does not scan provider records. Temporary registration/renewal failure remains visible. If an update is missing, check authorization, direction, expiry, receipts and worker health before manually copying data.
Important operating boundaries
Default scheduled provider scans remain disabled in the recorded production configuration. Older recurring-policy controls are not a promise that full-list polling is active. Current record-event settings are the appropriate controls for immediate per-record integration.
The connection owner's selected company must still match the queued company. Switching that owner's workspace can block delivery until the correct company is selected and access is rechecked. Expired subscriptions, revoked roles and exhausted API/storage capacity can also block work. See CRM operations for operator diagnostics.