Zoho CRM: README

Remove Related Records by IDs.

Tool ID: zoho_crm_related_records_delink_related_records

Run this action

This action has conditional or dynamic input fields that cannot be represented by a reliable static example. Inspect the live contract before executing it:

deepline tools get zoho_crm_related_records_delink_related_records --json

Example response

The SDK exposes this shape at result.toolResponse.raw. Values below are representative.

{
  "data": {
    "data": [
      {
        "code": "SUCCESS",
        "status": "success"
      }
    ]
  }
}

Use deepline tools get zoho_crm_related_records_delink_related_records --json for the latest machine-readable contract.

Input reference

Removes relationships between a parent record and multiple records in a specified related list, identified by their IDs in the query parameter. This operation deletes only the relationship links, not the actual records themselves. The target records remain intact in their respective modules.

Name	Type	Required	Default	Details
`payload.parentRecordModule`	`string`	Yes	—	The module name of the parent record (e.g., Contacts, Leads, Deals, Accounts, Services__s, Price_Books) Maximum length: 100. Pattern: `^[A-Za-z_][A-Za-z0-9_]*$`.
`payload.parentRecord`	`string`	Yes	—	The unique identifier of the parent record. Must be a valid numeric record ID. Maximum length: 20. Pattern: `^[0-9]+$`.
`payload.relatedList`	`string`	Yes	—	The name of the related list (module) containing the records to retrieve or modify Maximum length: 100. Pattern: `^[A-Za-z_][A-Za-z0-9_]*$`.
`payload.ids`	`string`	Yes	—	Comma-separated list of record IDs to delink from the parent record. Each ID must be numeric. Maximum length: 2000. Pattern: `^[0-9]+(,[0-9]+)*$`.

Output reference

Standard tool result payload.

Name	Type	Required	Default	Details
`result.data`	`object`	Yes	—	Response structure for bulk operations (update, delete)
`result.data.data`	`array`	Yes	—	Array of operation results per record Maximum items: 100.
`result.data.data[].code`	`"SUCCESS" \| "INVALID_DATA" \| "DUPLICATE_DATA" \| "MANDATORY_NOT_FOUND"`	Yes	—	Result code for the operation Allowed: `SUCCESS`, `INVALID_DATA`, `DUPLICATE_DATA`, `MANDATORY_NOT_FOUND`.
`result.data.data[].details`	`object`	No	—	Operation details including affected record ID
`result.data.data[].details.id`	`string`	No	—	ID of the affected record Maximum length: 20. Pattern: `^[0-9]+$`.
`result.data.data[].details.api_name`	`string`	No	—	API name of the field that caused the error (if applicable). Maximum length: 100.
`result.data.data[].details.json_path`	`string`	No	—	JSONPath to the field in request payload (if applicable). Maximum length: 500.
`result.data.data[].details.param_name`	`string`	No	—	Parameter name that caused the error (if applicable). Maximum length: 100.
`result.data.data[].message`	`string`	No	—	Human-readable result message Maximum length: 500.
`result.data.data[].status`	`"success" \| "error"`	Yes	—	Operation status Allowed: `success`, `error`.
`result.meta`	`object`	No	—	Additional response metadata (status, paging).

Deepline cost

Pricing model: fixed (per call).
Estimated Deepline credits: 0 per pricing unit.
Provider-native pricing may still exist outside Deepline credit billing.

Getting Started

GTM is code

Features

Deepline SDK beta

Integrations

API Reference

Run this action

Example response

Input reference

Output reference

Deepline cost

​Run this action

​Example response

​Input reference

​Output reference

​Deepline cost

​Related documentation

Run this action

Example response

Input reference

Output reference

Deepline cost

Related documentation