Zoho CRM: README

Mass Update API.

Tool ID: zoho_crm_mass_update_ids_update

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_mass_update_ids_update --json

Example response

The static output schema is not detailed enough to generate a reliable example. Use deepline tools get zoho_crm_mass_update_ids_update --json for the complete live contract.

Input reference

The request body must include ids, a list of record identifiers, and data, an array of objects mapping field API names to their new values.

Name	Type	Required	Default	Details
`payload.module`	`"Leads" \| "Accounts" \| "Contacts" \| "Deals" \| "Campaigns" \| "Tasks" \| "Calls" \| "Meetings" \| "Cases" \| "Solutions" \| "Products" \| "Vendors" \| "Price_Books" \| "Quotes" \| "Sales_Orders" \| "Purchase_Orders" \| "Invoices" \| "Custom"`	Yes	—	Specifies the CRM module for the mass update operation. Note: Module names are case-sensitive. Allowed: `Leads`, `Accounts`, `Contacts`, `Deals`, `Campaigns`, `Tasks`, `Calls`, `Meetings`, `Cases`, `Solutions`, `Products`, `Vendors`, `Price_Books`, `Quotes`, `Sales_Orders`, `Purchase_Orders`, `Invoices`, `Custom`.
`payload.data`	`array`	Yes	—	An array of objects mapping field API names to their new values. Maximum items: 1.
`payload.ids`	`array`	Yes	—	Record ids Maximum items: 500.

Output reference

Standard tool result payload.

Name	Type	Required	Default	Details
`result.data`	`object`	Yes	—	Schema for a successful mass update response
`result.data.data`	`array`	Yes	—	Array containing the response for each record Maximum items: 500.
`result.data.data[].code`	`"SUCCESS"`	Yes	—	Indicates the result of the operation with a response code Allowed: `SUCCESS`.
`result.data.data[].details`	`object`	Yes	—	Details of the record that was updated
`result.data.data[].details.id`	`string`	Yes	—	Record id Format: `int64`. Pattern: `^[0-9]+$`.
`result.data.data[].details.Modified_Time`	`string`	Yes	—	The date and time when the mass update operation was performed Format: `date-time`.
`result.data.data[].details.Modified_By`	`object`	Yes	—	The user who performed the mass update operation
`result.data.data[].details.Modified_By.id`	`string`	Yes	—	User id Format: `int64`. Pattern: `^[0-9]+$`.
`result.data.data[].details.Modified_By.name`	`string`	Yes	—	Name displayed for the user who made the modification Format: `string`.
`result.data.data[].details.Created_By`	`object`	Yes	—	The user who originally created the record
`result.data.data[].details.Created_By.id`	`string`	Yes	—	Numeric string identifier for the creating user Format: `int64`. Pattern: `^[0-9]+$`.
`result.data.data[].details.Created_By.name`	`string`	Yes	—	Name of the user who created the record Format: `string`.
`result.data.data[].details.Created_Time`	`string`	Yes	—	The date and time when the record was originally created Format: `date-time`.
`result.data.data[].message`	`string`	Yes	—	success message Format: `string`.
`result.data.data[].status`	`"success"`	Yes	—	Indicates the status of the operation Allowed: `success`.
`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