The Zoho Desk card on Integrations connects the selected company's service records. It is independent of the Zoho CRM connection: authorizing one does not authorize the other.
Watch the lesson
Connect and map
- Authorize Zoho Desk in the correct account region.
- Verify the returned organization.
- Select the permitted Nviti Helpdesk and remote department.
- Load and review valid remote status and priority choices, then save their mappings.
- Authorize the additional write scopes if you need to create or update remote tickets.
- Link a reviewed existing ticket or preview a supported import/create operation.
Check required fields on both sides. An imported ticket still obeys native required custom fields. Provider layouts requiring unsupported create fields can block creation rather than being guessed. A remote Desk contact ID does not automatically identify a local Customer or grant marketing consent.
What is exchanged
The supported ticket projection is subject, plain-text description, status and priority. Incoming Desk HTML becomes plain text. Comments, replies, attachments, custom fields, assignment, SLA state, customer identity and deletions are not mirrored by this connector.
Use the displayed per-ticket preview before a manual pull or push. Creating a new remote ticket requires explicit remote-contact mapping through the reviewed creation flow; automatic mapped-ticket updates do not guess that contact.
Choose one field authority
Desk ticket synchronization uses a single authority for the synchronized fields: Zoho Desk or Nviti. The same fields are not enabled for simultaneous incoming and outgoing automatic updates. Select the source of truth deliberately; this is different from CRM Contacts' supported conflict-aware two-direction flow.
Desk does not provide a verified atomic conditional update in this implementation. An external edit between the review and outgoing update can be overwritten. Review ownership with your team before choosing Nviti as the field writer.
Uncertain outcomes
Do not repeat an uncertain create. The operation journal blocks blind retries, including after reconnect. Reconcile using the exact remote ticket ID and matching contact/field evidence. Disconnecting keeps these identity and uncertainty records so reconnect does not create duplicates.
Enable individual-record notifications only after mappings and authority are verified; see Record updates. Provider webhook registration depends on Zoho edition and available webhook capacity. A registered connection is not proof that a real notification has been delivered.