Zoho CRM's Mirror Component lets you surface fields from a related record directly on the page you're already viewing — no tab-switching required. Combined with the GraphQL API, you have both a UI-based and a developer-friendly path to retrieving a single related record's data.
Why this matters
In Zoho CRM, records rarely stand alone. A deal links to a contact; a case ties to an account. Historically, pulling up a linked contact's phone number or email while working inside a deal meant navigating away, finding the contact, and then returning — breaking your workflow. [1] Whether you're a sales rep who needs instant context or a developer querying related data programmatically, knowing the right retrieval method saves real time.
---
Step-by-step
Option A — Mirror Component (UI, no code)
Step 1. Understand what the Mirror Component does. It acts as a live window embedded in a record's detail page, reflecting fields from a related record in real time. For example, a sales rep working inside a deal can see the linked contact's current phone number or email address without ever leaving that deal record. [1]
Step 2. Confirm your data centre is supported. At the time of writing, the Mirror Component is available for the JP, CA, SA, UAE, and AU data centres. If your org sits on a different DC, check the Zoho CRM release notes page for the latest rollout status before proceeding. [1]
Step 3. Navigate to the record where you want the related data to appear — for instance, open a Deal record. The Mirror Component is added at the record detail page level, so you need to be in the correct module's record view. [1]
Step 4. Access the page layout or component customisation settings for that module. Add the Mirror Component to the layout, then configure which related module (e.g., Contacts) and which specific fields (e.g., phone, email) you want reflected. Once saved, those fields will display live data pulled from the linked record every time the page loads. [1]
Step 5. Verify the component is working by opening a record that has a populated lookup relationship. The mirrored fields should show the related record's current values without any manual refresh. [1]
---
Option B — GraphQL API (developer path)
Step 1. Confirm eligibility. Zoho CRM's GraphQL API is not available on trial editions of any CRM plan, so ensure your organisation is on a paid tier before building against it. [7]
Step 2. Understand the query structure. The GraphQL API exposes two root types: Meta (for module/user/role metadata) and Records (for actual module data). You will use the Records type to fetch fields from a related module. [7]
Step 3. Write a query that targets the specific module containing your related record. For example, to retrieve the AccountName from the Accounts module alongside a LastName from Leads in a single round-trip, structure your query under the Records root and specify only the fields you need inside _data. [7]
query {
Records {
Accounts {
_data {
Account_Name {
value
}
}
}
}
}Step 4. Filter the query to a single record by passing the relevant record ID as a filter parameter within the query. The GraphQL API supports filtering and pagination across all accessible modules, so you can scope the response to exactly one related record rather than pulling an entire list. [7]
Step 5. Parse the value field from the response object. Each field in the _data array returns a value key containing the actual data, making it straightforward to extract and display in your application or Zoho function. [7]
---
Common pitfalls
- Mirror Component DC availability. If your data centre is not yet in the supported list (JP, CA, SA, UAE, AU), the component option will not appear in your layout editor. Check the community release thread for expansion announcements rather than assuming it's a configuration error. [1]
- GraphQL on trial accounts. Attempting to call the GraphQL endpoint on a trial org will fail. Switch to the REST API as a fallback, or upgrade the account first. [7]
- Lookup field required for Mirror Component. The Mirror Component relies on an existing lookup relationship between modules. If no lookup field connects the two modules, there is nothing for the component to mirror — you must establish the relationship first. [1]
- Real-time vs. cached data. The Mirror Component reflects data in real time, meaning any stale values you see are likely a browser cache issue rather than a CRM sync problem. A hard refresh usually resolves this. [1]
---
What to check
- DC eligibility confirmed — verify your CRM data centre is in the supported list before spending time configuring the Mirror Component layout. [1]
- Lookup relationship exists — ensure a lookup field already links the two modules involved; without it, neither the Mirror Component nor a filtered GraphQL query will return the related record. [1]
- GraphQL edition check — if using the API path, confirm the org is on a paid CRM edition so the GraphQL endpoint is accessible. [7]
---
*Beam Help is an independent expert support resource for Zoho products and is not official Zoho support. Always cross-reference with the latest Zoho CRM documentation for your specific edition and data centre.*