Beam Help
Get help now

How-to · Zoho CRM

How to create related records in Zoho CRM

Link and create new records in related modules.

Beam Help — independent expert support for Zoho (not official Zoho support) — explains how to create and associate related records in Zoho CRM, covering both the UI approach and the API-based methods available for linking modules and multi-select lookup relationships.


Why this matters


Zoho CRM's power comes from connecting records across modules — linking a Contact to an Account, associating a Deal with Activities, or building many-to-many relationships between custom modules. Understanding the correct method for each relationship type saves hours of troubleshooting and prevents data integrity issues down the line. Whether you are working directly in the CRM interface or automating record creation via the REST API, the approach differs depending on the relationship type involved.


Step-by-step


Step 1. Understand the relationship type you need.


Before creating related records, identify whether you need a standard lookup (one-to-many), a multi-select lookup (many-to-many via a linking module), or a related list association. Each has a distinct API path and UI workflow. For many-to-many relationships, Zoho CRM uses a linking module to bridge the two sides of the relationship. [2]


Step 2. Create the primary record first.


Navigate to the relevant module in Zoho CRM (for example, Contacts or Accounts) and create or locate the parent record you want to associate others with. Every related record must reference a valid parent record ID, so confirm the parent exists before proceeding. [1]


Step 3. Use the Related List panel in the UI.


Open the parent record and scroll to the Related Lists section at the bottom of the record detail page. Each related module (for example, Deals, Activities, or Contacts) appears as a tab or panel. Click New or Create within the relevant related list panel to open a creation form that is pre-linked to the parent record. This is the fastest no-code path for one-off associations.


Step 4. For multi-select lookup relationships, choose your API method.


When working with multi-select lookup related lists via the REST API, there are two supported approaches: inserting records directly via the insert records API, or working through the linking module. The linking module approach is the recommended path for the newer many-to-many related list feature in Zoho CRM. [2]


Step 5. When automating with Zoho Flow, fetch the related record ID first.


If you are building an automated flow that creates a related record in Zoho CRM (or links CRM records to another Zoho app), you must retrieve the ID of the record you want to associate *before* the creation step. Each app maintains its own unique record IDs — an ID from one Zoho app cannot be used directly in another. Use a Fetch action in Zoho Flow to look up the record by email or name, then map the returned ID into the relationship field of your creation action. [4]


Step 6. Verify the record URL structure for direct navigation.


Once a related record is created, you can navigate to it directly using the CRM URL pattern:


https://crm.zoho.{dc}/crm/tab/{Module}/{RecordId}

Replace {dc} with your data centre suffix (for example, com, eu, or in), {Module} with the API name of the module (for example, Contacts), and {RecordId} with the numeric ID returned by the API. [1]


Step 7. For cross-product integrations, link at the account or contact level first.


When integrating Zoho CRM with other Zoho products (such as Zoho Desk or Zoho FSM), related records can only be created after the Account or Contact in the external product is linked to its CRM counterpart. Attempting to create a child record (such as a Work Order or Ticket) before that link exists will result in an error prompting you to complete the association first. [3]


Common pitfalls


  • Using the wrong ID across apps. A Contact ID in Zoho CRM is not the same numeric value as the Contact ID for the same person in Zoho Desk or Zoho Books. Always fetch the record within the target app to get the correct ID before creating a related record. [4]

  • Skipping the linking module for many-to-many relationships. For multi-select lookup related lists, attempting to associate records without going through the linking module may not work as expected. The linking module is the supported mechanism for the many-to-many relationship feature. [2]

  • Parent record not yet linked to the integration partner. In cross-product scenarios, if the CRM Account or Contact has not been pushed to or linked with the partner product, child record creation will fail. Resolve the account link first, then proceed to create related records. [3]

  • OAuth connection expiry in automated functions. If you are using custom functions or API calls with a named OAuth connection, an expired connection will return an UnAuthenticated Connection error. Reauthorise the connection from Setup > Developer Hub > Connections before retrying. [6]

What to check


  • Confirm the parent record ID is valid by navigating to it in the CRM UI using the standard URL pattern before running any API or automation that references it. [1]
  • Verify the relationship type (standard lookup vs. multi-select lookup vs. related list) in Setup > Modules to ensure you are using the correct API method for association. [2]
  • Test the fetch step in any Flow automation by running the flow with a known record and confirming the returned ID matches the record visible in the CRM UI before enabling the flow for production use. [4]

Sources cited

  1. [1] server.py: build_zoho_links
  2. [2] Associate records via the Multi-select lookup RELATED LIST via API
  3. [3] Zoho FSM | Integrating Zoho FSM with Zoho Desk
  4. [4] How to use Fetch actions in Zoho Flow
  5. [5] Syncing Zoho CRM events with Zoho Calendar
  6. [6] Kaizen 247 - Historical Deduplication using COQL API, Merge Records API and Functions
Create Related Records in Zoho CRM | Beam Help