Zoho: Get Merge Job Status
Zoho findAndMerge.getMergeJobStatus: arguments, response, policy and SDK examples.
← Find and merge operations · Get started
Operation zoho.getmergejobstatus
Provider route: GET /crm/v8/{module}/{masterRecordId}/actions/merge. Alter supplies the connection’s credentials and routing.
Call through Alter
Section titled “Call through Alter”Install @alter-ai/sdk @alter-ai/zoho with npm, or alter-sdk-zoho with pip. Supply your connected customer’s grant ID and the arguments described below.
import { App } from "@alter-ai/sdk";import { ZohoIntegration } from "@alter-ai/zoho";
async function execute(input: Parameters<ZohoIntegration["findAndMerge"]["getMergeJobStatus"]>[0]) { const app = new App({ apiKey: process.env.ALTER_API_KEY! }); try { const provider = new ZohoIntegration(app, { grantId: process.env.PROVIDER_GRANT_ID! }); const call = await provider.findAndMerge.getMergeJobStatus(input); const result = await call.wait(); return result.bodyJson(); } finally { await app.close(); }}import osfrom alter_sdk import Appfrom alter_sdk_zoho import ZohoIntegration
async def execute(arguments): async with App(api_key=os.environ["ALTER_API_KEY"]) as app: provider = ZohoIntegration(app, {"grant_id": os.environ["PROVIDER_GRANT_ID"]}) call = await provider.find_and_merge.get_merge_job_status(arguments) result = await call.wait() return result.body_json()| Field | Type | Presence | Description and constraints |
|---|---|---|---|
$ | object | Root | Additional keys: not allowed |
path | object | Required within parent | Additional keys: not allowed |
path.masterRecordId | string | Required within parent | Master record identifier (int64 as string) Maximum length: 50 Pattern: ^[0-9]+$ |
path.module | string | Required within parent | Valid CRM module name One of: Accounts, Contacts, Leads, Deals, Cases, Campaigns |
query | object | Optional | Additional keys: not allowed |
query.job_id | string | Optional | Unique identifier for merge job Maximum length: 50 Pattern: ^[0-9]+$ |
Response
Section titled “Response”Response media type: application/json. The table describes the pinned successful response. Referenced models link to their complete fields.
| Field | Type | Presence | Description and constraints |
|---|---|---|---|
$ | JSON | Root | |
$ (anyOf 1) | object | Alternative | Represents the response body containing the list of merge job status records for the specified master record. Additional keys: not allowed |
$ (anyOf 1).merge | array | Required within parent | Contains the list of merge job status objects returned for the specified master record. Maximum items: 100 |
$ (anyOf 1).merge[] | object | Each item | Each object represents an individual merge job record, including its unique identifier and current processing status. Additional keys: not allowed |
$ (anyOf 1).merge[].job_id | string | Required within parent | Represents the unique identifier of the merge job. Maximum length: 50 Pattern: ^[0-9]+$ |
$ (anyOf 1).merge[].status | string | Required within parent | Represents the current processing status of the merge job. Possible values: SCHEDULED - The merge job is queued and waiting to be processed. running - The merge job is currently being processed. completed - The merge job has finished successfully. failed - The merge job encountered an error and did not complete. Known values: SCHEDULED, running, completed, failed |
$ (anyOf 2) | null | Alternative |
Policy, approvals and errors
Section titled “Policy, approvals and errors”SDK function policy ID: zoho.getmergejobstatus. Catalog operation: getMergeJobStatus. Rules can name either ID; function rules distinguish managed calls and conservatively cover raw calls sharing the route. Existing grant permissions and policy rules apply. wait() returns an immediate result or waits for a required approval; it never approves the request itself. Persist the approval ID to resume after a restart.
Provider errors retain their response; JSON decoding raises ProviderAPIError for provider failures. ManagedOperationError identifies contract/input/retention errors. See error handling and provider-specific behavior. Sensitive input may be refused before approval storage. A decoding error never resubmits a write.
No-content response statuses: [204]