Zoho CRM: README

Retrieve the status of a mass update job.

Tool ID: zoho_crm_mass_update_get_mass_update_status

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

Example response

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

{
  "data": {
    "data": [
      {
        "Status": "COMPLETED",
        "Failed_Count": 123,
        "Updated_Count": 123,
        "Not_Updated_Count": 123,
        "Total_Count": 123
      }
    ]
  }
}

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

Input reference

Retrieves the current status and progress metrics of an asynchronous mass update job initiated via POST /crm/v8/{module}/actions/mass_update. Returns record counts and current job state.

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.job_id`	`string`	Yes	—	Job identifier for the asynchronous mass update operation initiated via POST. Used to retrieve operation status and result counts. Format: `int64`. Pattern: `^[0-9]+$`.

Output reference

Standard tool result payload.

Name	Type	Required	Default	Details
`result.data`	`object`	Yes	—	Successfully retrieved the mass update job status, including current state and record processing counts.
`result.data.data`	`array`	Yes	—	Successfully retrieved the mass update job status, including current state and record processing counts. Maximum items: 1.
`result.data.data[].Status`	`"COMPLETED" \| "SCHEDULED" \| "QUEUED" \| "RUNNING" \| "SUSPENDED" \| "FAILED"`	Yes	—	Current state of the mass update job Allowed: `COMPLETED`, `SCHEDULED`, `QUEUED`, `RUNNING`, `SUSPENDED`, `FAILED`.
`result.data.data[].Failed_Count`	`integer`	Yes	—	Number of records that failed to update due to validation or other errors Format: `int32`.
`result.data.data[].Updated_Count`	`integer`	Yes	—	Number of records successfully updated Format: `int32`.
`result.data.data[].Not_Updated_Count`	`integer`	Yes	—	Number of records pending update or skipped Format: `int32`.
`result.data.data[].Total_Count`	`integer`	Yes	—	Total number of records submitted for mass update Format: `int32`.
`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