> ## 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.

# Intercom: Jobs Status

> Check the status of an Intercom background job by its ID. Includes SDK V2 guidance, input constraints, response fields, and Deepline credit cost.

Check the status of an Intercom background job by its ID.

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

## 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.

```ts theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
import { Deepline } from 'deepline';

const deepline = await Deepline.connect();
const result = await deepline.tools.execute(
  'intercom_jobs_status',
  {
    "job_id": "job_123"
  },
);

console.log(result.toolResponse.raw);
```

### CLI

```bash theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
deepline tools execute intercom_jobs_status --input '{
  "job_id": "job_123"
}' --json
```

## Example response

The SDK returns this shape at `result.toolResponse.raw`. The example values illustrate the response.

```json theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
{
  "data": {
    "id": "id_123"
  }
}
```

Use `deepline describe intercom_jobs_status --json` for the latest machine-readable contract.

## Input reference

Retrieve the status of job execution.

| Name | Type | Required | Default | Details |
| - | - | - | - | - |
| `payload.job_id` | `string` | Yes | — | The unique identifier for the job which is given by Intercom |

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

  ### Input JSON Schema

  ```json theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
  {
    "type": "object",
    "description": "Retrieve the status of job execution.",
    "properties": {
      "job_id": {
        "type": "string",
        "description": "The unique identifier for the job which is given by Intercom"
      }
    },
    "required": [
      "job_id"
    ],
    "additionalProperties": false
  }
  ```
</details>

## Output reference

Standard tool result payload.

| Name | Type | Required | Default | Details |
| - | - | - | - | - |
| `result.data` | `object` | Yes | — | Jobs are tasks that are processed asynchronously by the Intercom system after being enqueued via the API. This allows for efficient handling of operations that may take time to complete, such as data imports or exports. You can check the status of your jobs to monitor their progress and ensure they are completed successfully. |
| `result.data.type` | `"job"` | No | — | The type of the object Allowed: `job`. |
| `result.data.id` | `string` | Yes | — | The id of the job that's currently being processed or has completed. |
| `result.data.url` | `string` | No | — | API endpoint URL to check the job status. |
| `result.data.status` | `"pending" \| "success" \| "failed"` | No | — | The status of the job execution. Allowed: `pending`, `success`, `failed`. |
| `result.data.resource_type` | `string` | No | — | The type of resource created during job execution. |
| `result.data.resource_id` | `string \| null` | No | — | The id of the resource created during job execution (e.g. ticket id) |
| `result.data.resource_url` | `string \| null` | No | — | The url of the resource created during job exeuction. Use this url to fetch the resource. |
| `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": "Jobs are tasks that are processed asynchronously by the Intercom system after being enqueued via the API. This allows for efficient handling of operations that may take time to complete, such as data imports or exports. You can check the status of your jobs to monitor their progress and ensure they are completed successfully.",
        "properties": {
          "type": {
            "type": "string",
            "description": "The type of the object",
            "enum": [
              "job"
            ]
          },
          "id": {
            "type": "string",
            "description": "The id of the job that's currently being processed or has completed."
          },
          "url": {
            "type": "string",
            "description": "API endpoint URL to check the job status."
          },
          "status": {
            "type": "string",
            "description": "The status of the job execution.",
            "enum": [
              "pending",
              "success",
              "failed"
            ]
          },
          "resource_type": {
            "type": "string",
            "description": "The type of resource created during job execution."
          },
          "resource_id": {
            "type": [
              "string",
              "null"
            ],
            "description": "The id of the resource created during job execution (e.g. ticket id)"
          },
          "resource_url": {
            "type": [
              "string",
              "null"
            ],
            "description": "The url of the resource created during job exeuction. Use this url to fetch the resource."
          }
        },
        "required": [
          "id"
        ],
        "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

* [Intercom provider guide](https://deepline.com/docs/providers/intercom/guide.md)
* [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.