Zoho CRM: Record Update Records

Update the fields of several Zoho CRM records in a module at once.

Tool ID: zoho_crm_record_update_records

Run this action

Use the TypeScript SDK for one call. Use ctx.tools.execute(...) inside a Play for durable calls, scheduled calls, or CSV processing.

import { Deepline } from 'deepline';

const deepline = await Deepline.connect();
const result = await deepline.tools.execute(
  'zoho_crm_record_update_records',
  {
    "module": "example",
    "data": [
      {
        "id": "id_123",
        "$append_values": "example"
      }
    ]
  },
);

console.log(result.toolResponse.raw);

CLI

deepline tools execute zoho_crm_record_update_records --input '{
  "module": "example",
  "data": [
    {
      "id": "id_123",
      "$append_values": "example"
    }
  ]
}' --json

Example response

The static output schema lacks the details for a reliable example. Use deepline describe zoho_crm_record_update_records --json for the complete live contract.

Input reference

Input schema for create, update, or upsert record requests.

Name	Type	Required	Default	Details
`payload.module`	`string`	Yes	—	Specifies the module name Maximum length: 100.
`payload.data`	`array`	Yes	—	Request body containing one or more records to be created or updated. Maximum items: 100.
`payload.apply_feature_execution`	`array`	No	—	List of features that should be executed on demand during record processing. Maximum items: 100.
`payload.skip_feature_execution`	`array`	No	—	List of features that should be skipped during record processing. Maximum items: 100.
`payload.trigger`	`array`	No	—	List of automation triggers to invoke during the record operation. Maximum items: 100.

Output reference

Standard tool result payload.

Name	Type	Required	Default	Details
`result.data`	`object`	Yes	—	Standard success response schema for single or bulk record operations.
`result.data.data`	`array`	Yes	—	List of successfully processed records with detailed metadata. Maximum items: 100.
`result.data.data[].code`	`"SUCCESS"`	Yes	—	Machine-readable code indicating a successful operation. Allowed: `SUCCESS`.
`result.data.data[].message`	`string`	Yes	—	Human-readable success message describing the operation outcome. Maximum length: 1024.
`result.data.data[].status`	`"success"`	Yes	—	Overall execution status of the operation. Allowed: `success`.
`result.data.data[].details`	`object`	Yes	—	Detailed metadata about the processed record.
`result.data.data[].details.id`	`string`	Yes	—	Unique identifier of the record. Format: `int64`.
`result.data.data[].details.Modified_Time`	`string`	Yes	—	Timestamp indicating when the record was last modified. Format: `date-time`.
`result.data.data[].details.Created_Time`	`string`	Yes	—	Timestamp indicating when the record was created. Format: `date-time`.
`result.data.data[].details.Created_By`	`object`	Yes	—	User who originally created the record.
`result.data.data[].details.Created_By.name`	`string`	Yes	—	Display name of the creating user. Maximum length: 100.
`result.data.data[].details.Created_By.id`	`string`	Yes	—	Unique identifier of the creating user. Format: `int64`.
`result.data.data[].details.Modified_By`	`object`	Yes	—	User who last modified the record.
`result.data.data[].details.Modified_By.name`	`string`	Yes	—	Display name of the modifying user. Maximum length: 100.
`result.data.data[].details.Modified_By.id`	`string`	Yes	—	Unique identifier of the modifying user. Format: `int64`.
`result.data.data[].details.$approval_state`	`string`	Yes	—	Approval state of the record in the approval workflow. Maximum length: 1024.
`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.

​Run this action

​CLI

​Example response

​Input reference

​Output reference

​Deepline cost

​Related documentation

Run this action

CLI

Example response

Input reference

Output reference

Deepline cost

Related documentation