> ## 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: Get Data Export

> Check the status of an Intercom conversation data export job. Includes SDK V2 guidance, input constraints, response fields, and Deepline credit cost.

Check the status of an Intercom conversation data export job.

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

## 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_get_data_export',
  {
    "job_identifier": "example_123"
  },
);

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

### CLI

```bash theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
deepline tools execute intercom_get_data_export --input '{
  "job_identifier": "example_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": {
    "job_identifier": "example_123",
    "status": "pending",
    "download_expires_at": "2026-01-15T12:00:00Z"
  }
}
```

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

## Input reference

You can view the status of your job by sending a `GET` request to the URL `https://api.intercom.io/export/content/data/&#123;job_identifier&#125;` - the `&#123;job_identifier&#125;` is the value returned in the response when you first created the export job. More on it can be seen in the Export Job Model. > 🚧 Jobs expire after two days > All jobs that have completed processing (and are thus available to download from the provided URL) will have an expiry limit of two days from when the export ob completed. After this, the data will no longer be available.

| Name | Type | Required | Default | Details |
| - | - | - | - | - |
| `payload.job_identifier` | `string` | Yes | — | job\_identifier |

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

  ### Input JSON Schema

  ```json theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
  {
    "type": "object",
    "description": "You can view the status of your job by sending a `GET` request to the URL `https://api.intercom.io/export/content/data/{job_identifier}` - the `{job_identifier}` is the value returned in the response when you first created the export job. More on it can be seen in the Export Job Model. > 🚧 Jobs expire after two days > All jobs that have completed processing (and are thus available to download from the provided URL) will have an expiry limit of two days from when the export ob completed. After this, the data will no longer be available.",
    "properties": {
      "job_identifier": {
        "type": "string",
        "description": "job_identifier"
      }
    },
    "required": [
      "job_identifier"
    ],
    "additionalProperties": false
  }
  ```
</details>

## Output reference

Standard tool result payload.

| Name | Type | Required | Default | Details |
| - | - | - | - | - |
| `result.data` | `object` | Yes | — | The data export API is used to export message delivery and engagement statistics for outbound content (Emails, Posts, Custom Bots, Surveys, Tours, Series, and more) sent in a given timeframe. The exported data includes who received each message, when they received it, and how they engaged with it (opens, clicks, replies, completions, dismissals, unsubscribes, and bounces). |
| `result.data.job_identifier` | `string` | No | — | The identifier for your job. |
| `result.data.status` | `"pending" \| "in_progress" \| "failed" \| "completed" \| "no_data" \| "canceled"` | No | — | The current state of your job. Allowed: `pending`, `in_progress`, `failed`, `completed`, `no_data`, `canceled`. |
| `result.data.download_expires_at` | `string` | No | — | The time after which you will not be able to access the data. |
| `result.data.download_url` | `string` | No | — | The location where you can download your data. |
| `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": "The data export API is used to export message delivery and engagement statistics for outbound content (Emails, Posts, Custom Bots, Surveys, Tours, Series, and more) sent in a given timeframe. The exported data includes who received each message, when they received it, and how they engaged with it (opens, clicks, replies, completions, dismissals, unsubscribes, and bounces).",
        "properties": {
          "job_identifier": {
            "type": "string",
            "description": "The identifier for your job."
          },
          "status": {
            "type": "string",
            "description": "The current state of your job.",
            "enum": [
              "pending",
              "in_progress",
              "failed",
              "completed",
              "no_data",
              "canceled"
            ]
          },
          "download_expires_at": {
            "type": "string",
            "description": "The time after which you will not be able to access the data."
          },
          "download_url": {
            "type": "string",
            "description": "The location where you can download your data."
          }
        },
        "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.