> ## 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: Inputs, Cost & CLI Example

> Retrieve job status. Intercom Intercom Jobs Status docs include request fields, response shape, pricing notes, and Deepline CLI examples.

## Run in Enrichment Spreadsheet

<Info>
  Use this function as a column step in `deepline enrich`.
</Info>

```bash theme={null}
deepline enrich --input leads.csv --output leads.enriched.csv --with 'result=intercom_jobs_status:{"job_id":"{{job_id}}"}' --json
```

<Tip>
  Map payload values to spreadsheet columns with `{{column_name}}` placeholders.
</Tip>

## Input Schema

| Name             | Type     | Required | Default | Description                                                  |
| ---------------- | -------- | -------- | ------- | ------------------------------------------------------------ |
| `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={null}
  {
    "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 Schema

| Name          | Type     | Required | Default | Description                                                                                                                                                                                                                                                                                                                             |
| ------------- | -------- | -------- | ------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `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.meta` | `object` | No       |         | Additional response metadata (status, paging).                                                                                                                                                                                                                                                                                          |

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

  ### Output JSON Schema

  ```json theme={null}
  {
    "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>

## Advanced: Direct CLI

<Info>
  Use direct execution for single payload debugging.
</Info>

```bash theme={null}
deepline tools execute intercom_jobs_status --payload '{
  "job_id": "string"
}' --json
```

### CLI flags

| Flag                        | Description                                         |
| --------------------------- | --------------------------------------------------- |
| `--json`                    | Print machine-readable output.                      |
| `--wait`                    | Wait for terminal provider status when supported.   |
| `--debug`                   | Enable wait mode with additional status/log output. |
| `--wait-timeout SECONDS`    | Max seconds to wait in wait mode.                   |
| `--poll-interval SECONDS`   | Polling interval in seconds during wait mode.       |
| `--timeout SECONDS`         | Request timeout in seconds.                         |
| `--connect-timeout SECONDS` | Connection timeout in seconds.                      |

## Cost

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