Record linking in Zoho CRM lets you surface connected data across modules and external apps — this guide explains how to retrieve and work with those linking details using native features and API-level URL patterns.
Why this matters
When your CRM records are tied to contacts, deals, accounts, or even external systems like Zoho Desk or Zoho FSM, knowing *how* those links are structured helps you navigate quickly, build automations, and avoid broken cross-module references. Teams that manage field service, support tickets, or complex sales pipelines especially benefit from understanding exactly where linked record data lives and how to access it programmatically or through the UI. As independent expert support for Zoho (not official Zoho support), Beam Help sees this question come up frequently when clients are building integrations or customising record detail pages.
---
Step-by-step
Step 1. Understand the standard CRM record URL pattern before you start pulling linking details. Every Zoho CRM record follows the format https://crm.zoho.{dc}/crm/tab/{Module}/{RecordId} — where dc is your data centre (e.g., com, eu, in) and Module is the API name of the module (e.g., Contacts, Deals). If your organisation has a specific org ID, the URL can also take the form /crm/org{OrgId}/tab/{Module}/{RecordId}. Knowing this pattern lets you construct or verify direct links to any linked record. [2]
Step 2. When retrieving record data via the Zoho CRM API, check the response payload for the $se_module or module fields on each related record object — these tell you which module the linked record belongs to. The record's unique identifier is found in the id field, or inside a nested details object under details.id if the top-level id is absent. [4]
Step 3. To identify the display name of a linked record (useful for labelling links in dashboards or automations), look for these fields in order of priority within the record or its details sub-object: FullName, Name, Subject, DealName, or Account_Name. If none of those are populated, fall back to constructing a label like Record {RecordId}. [4]
Step 4. If you are working with records that are also linked to Zoho Desk, the linking details are stored in a dedicated section. On the associated record inside Zoho FSM (or CRM-adjacent modules), look for the Zoho Desk Info section in the left panel — this displays the direct link back to the originating Desk ticket, account, or contact. [1][6]
Step 5. To view or manage cross-system record links from the Zoho Desk side, open a Ticket, Account, or Contact record in Desk and navigate to the Zoho FSM tab. From there you can see which FSM records (Requests, Estimates, Work Orders, Service Appointments, Assets) are linked, click through to them, or use the link icon to attach an existing record. [1][7]
Step 6. For a purely in-CRM approach to viewing related record data without navigating away, use the Mirror Component on a record's detail page. This feature reflects live field values from a related record — for example, a contact's phone number or email displayed directly inside a deal record — so you can confirm linking is correct and the data is current without opening the linked record separately. [3]
Step 7. If you are building a connector or function that needs to invoke linked record data from a third-party service, set up a Connection in Zoho CRM's developer settings. After clicking Create and Connect, the resulting page shows the Link name, Service name, and Status, along with a ready-to-use code snippet for invoking the connection inside a Deluge function. The Connection value in that snippet corresponds to the Link name you assigned. [5]
---
Common pitfalls
- Missing module identifier: If the
$se_modulefield is empty in an API response, the system cannot construct a valid CRM record URL. Always verify that the module API name is present before attempting to build a direct link. [4] - Cross-system linking errors: When linking a Zoho Desk Contact to a Zoho FSM record, the Contact must already be associated with the correct FSM Company that corresponds to the Desk Account. Skipping this association step triggers an error and blocks record creation. [1][6]
- Unlinking order matters: If you need to unlink a Desk Account from Zoho FSM, you must first unlink all Contacts associated with that Account. Attempting to unlink the Account while Contacts are still attached will fail — check the Contacts tab on the record first. [7]
- Mirror Component availability: As of the latest announcements, the Mirror Component is available for JP, CA, SA, UAE, and AU data centres. If your org is on a different DC, this UI method for viewing linking details may not yet be accessible. [3]
---
What to check
- Confirm that the
ModuleAPI name andRecordIdin your constructed URL match an actual record in your CRM org — navigate tohttps://crm.zoho.{dc}/crm/tab/{Module}/{RecordId}directly to validate. [2][4] - After linking records across systems (e.g., Desk ↔ FSM), verify the Zoho Desk Info section appears in the left panel of the FSM record to confirm the link was saved correctly. [6]
- When using the Mirror Component, open the deal or parent record and confirm the reflected fields (such as contact email or phone) are showing current values, indicating the lookup relationship is intact. [3]