> ## Documentation Index
> Fetch the complete documentation index at: https://deepline.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Zoho CRM: Find And Merge Get Merge Job Status

> Check the status of a Zoho CRM duplicate record merge job. Includes SDK V2 guidance, input constraints, response fields, and Deepline credit cost.

Check the status of a Zoho CRM duplicate record merge job.

> [!NOTE]
>
> Tool ID: `zoho_crm_find_and_merge_get_merge_job_status`

## Run this action

This action has conditional or dynamic inputs. A static example cannot describe these inputs reliably.

Read the live contract before you execute this action:

```bash theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
deepline describe zoho_crm_find_and_merge_get_merge_job_status --json
```

## Example response

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

## Input reference

Retrieves the status of merge jobs for finding and tracking record merge operations in Zoho CRM modules.

| Name | Type | Required | Default | Details |
| - | - | - | - | - |
| `payload.job_id` | `string` | No | — | Optional job ID to track specific merge operation status Maximum length: 50. Pattern: `^[0-9]+$`. |
| `payload.masterRecordId` | `string` | Yes | — | Unique identifier of the master record that will be retained after merge Maximum length: 50. Pattern: `^[0-9]+$`. |
| `payload.module` | `"Accounts" \| "Contacts" \| "Leads" \| "Deals" \| "Cases" \| "Campaigns"` | Yes | — | CRM module name for which records should be merged Allowed: `Accounts`, `Contacts`, `Leads`, `Deals`, `Cases`, `Campaigns`. |

<details>
  <summary>Show raw input schema</summary>

  ### Input JSON Schema

  ```json theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
  {
    "type": "object",
    "description": "Retrieves the status of merge jobs for finding and tracking record merge operations in Zoho CRM modules.",
    "properties": {
      "job_id": {
        "type": "string",
        "description": "Optional job ID to track specific merge operation status",
        "maxLength": 50,
        "pattern": "^[0-9]+$"
      },
      "masterRecordId": {
        "type": "string",
        "description": "Unique identifier of the master record that will be retained after merge",
        "maxLength": 50,
        "pattern": "^[0-9]+$"
      },
      "module": {
        "type": "string",
        "description": "CRM module name for which records should be merged",
        "enum": [
          "Accounts",
          "Contacts",
          "Leads",
          "Deals",
          "Cases",
          "Campaigns"
        ]
      }
    },
    "required": [
      "masterRecordId",
      "module"
    ],
    "additionalProperties": false
  }
  ```
</details>

## Output reference

Standard tool result payload.

| Name | Type | Required | Default | Details |
| - | - | - | - | - |
| `result.data` | `object` | Yes | — | Response containing merge job status information |
| `result.data.merge` | `array` | Yes | — | Array of merge job status records Maximum items: 100. |
| `result.data.merge[].job_id` | `string` | Yes | — | Unique identifier of the merge job Maximum length: 50. Pattern: `^[0-9]+$`. |
| `result.data.merge[].status` | `"SCHEDULED" \| "running" \| "completed" \| "failed"` | Yes | — | Current status of the merge job Allowed: `SCHEDULED`, `running`, `completed`, `failed`. |
| `result.meta` | `object` | No | — | Additional response metadata (status, paging). |

<details>
  <summary>Show raw output schema</summary>

  ### Output JSON Schema

  ```json theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
  {
    "type": "object",
    "description": "Standard tool result payload.",
    "properties": {
      "data": {
        "type": "object",
        "description": "Response containing merge job status information",
        "properties": {
          "merge": {
            "type": "array",
            "description": "Array of merge job status records",
            "maxItems": 100,
            "items": {
              "type": "object",
              "description": "Individual merge job status",
              "properties": {
                "job_id": {
                  "type": "string",
                  "description": "Unique identifier of the merge job",
                  "maxLength": 50,
                  "pattern": "^[0-9]+$"
                },
                "status": {
                  "type": "string",
                  "description": "Current status of the merge job",
                  "enum": [
                    "SCHEDULED",
                    "running",
                    "completed",
                    "failed"
                  ]
                }
              },
              "required": [
                "job_id",
                "status"
              ],
              "additionalProperties": false
            }
          }
        },
        "required": [
          "merge"
        ],
        "additionalProperties": false
      },
      "meta": {
        "type": "object",
        "description": "Additional response metadata (status, paging).",
        "additionalProperties": true
      }
    },
    "required": [
      "data"
    ],
    "additionalProperties": false
  }
  ```
</details>

## Deepline cost

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

## Related documentation

* [SDK V2 quickstart](https://deepline.com/docs/sdk-v2/quickstart.md)
* [SDK reference](https://deepline.com/docs/sdk-v2/sdk-reference.md)
* [Run tools across a CSV](https://deepline.com/docs/sdk-v2/batch-csv.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.