> ## 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: Lis Data Events

> List the recent events recorded for an Intercom user, or a summary of their event counts. Includes inputs, outputs, SDK V2 examples, and Deepline cost.

List the recent events recorded for an Intercom user, or a summary of their event counts.

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

## 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_lis_data_events',
  {
    "filter": {
      "user_id": "user_123"
    },
    "type": "example"
  },
);

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

### CLI

```bash theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
deepline tools execute intercom_lis_data_events --input '{
  "filter": {
    "user_id": "user_123"
  },
  "type": "example"
}' --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": {
    "type": "event.summary",
    "email": "jane.doe@example.com",
    "intercom_user_id": "intercom_user_123"
  }
}
```

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

## Input reference

\> 🚧 > > Please note that you can only 'list' events that are less than 90 days old. Event counts and summaries will still include your events older than 90 days but you cannot 'list' these events individually if they are older than 90 days The events belonging to a customer can be listed by sending a GET request to `https://api.intercom.io/events` with a user or lead identifier along with a `type` parameter. The identifier parameter can be one of `user_id`, `email` or `intercom_user_id`. The `type` parameter value must be `user`. - `https://api.intercom.io/events?type=user&user_id={user_id}` - `https://api.intercom.io/events?type=user&email={email}` - `https://api.intercom.io/events?type=user&intercom_user_id={id}` (this call can be used to list leads) The `email` parameter value should be [url encoded](http://en.wikipedia.org/wiki/Percent-encoding) when sending. You can optionally See the live schema below for the complete notes.

| Name | Type | Required | Default | Details |
| - | - | - | - | - |
| `payload.filter` | `object` | Yes | — | — |
| `payload.type` | `string` | Yes | — | The value must be user |
| `payload.summary` | `boolean` | No | — | summary flag |

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

  ### Input JSON Schema

  ```json theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
  {
    "type": "object",
    "description": "> 🚧 > > Please note that you can only 'list' events that are less than 90 days old. Event counts and summaries will still include your events older than 90 days but you cannot 'list' these events individually if they are older than 90 days The events belonging to a customer can be listed by sending a GET request to `https://api.intercom.io/events` with a user or lead identifier along with a `type` parameter. The identifier parameter can be one of `user_id`, `email` or `intercom_user_id`. The `type` parameter value must be `user`. - `https://api.intercom.io/events?type=user&user_id={user_id}` - `https://api.intercom.io/events?type=user&email={email}` - `https://api.intercom.io/events?type=user&intercom_user_id={id}` (this call can be used to list leads) The `email` parameter value should be [url encoded](http://en.wikipedia.org/wiki/Percent-encoding) when sending. You can optionally define the result page size as well with the `per_page` parameter.",
    "properties": {
      "filter": {
        "type": "object",
        "anyOf": [
          {
            "properties": {
              "user_id": {
                "type": "string"
              }
            },
            "required": [
              "user_id"
            ],
            "additionalProperties": false
          },
          {
            "properties": {
              "intercom_user_id": {
                "type": "string"
              }
            },
            "required": [
              "intercom_user_id"
            ],
            "additionalProperties": false
          },
          {
            "properties": {
              "email": {
                "type": "string"
              }
            },
            "required": [
              "email"
            ],
            "additionalProperties": false
          }
        ]
      },
      "type": {
        "type": "string",
        "description": "The value must be user"
      },
      "summary": {
        "type": "boolean",
        "description": "summary flag"
      }
    },
    "required": [
      "filter",
      "type"
    ],
    "additionalProperties": false
  }
  ```
</details>

## Output reference

Standard tool result payload.

| Name | Type | Required | Default | Details |
| - | - | - | - | - |
| `result.data` | `object` | Yes | — | This will return a summary of data events for the App. |
| `result.data.type` | `"event.summary"` | No | — | The type of the object Allowed: `event.summary`. |
| `result.data.email` | `string` | No | — | The email address of the user |
| `result.data.intercom_user_id` | `string` | No | — | The Intercom user ID of the user |
| `result.data.user_id` | `string` | No | — | The user ID of the user |
| `result.data.events` | `array` | No | — | A summary of data events |
| `result.data.events[].name` | `string` | No | — | The name of the event |
| `result.data.events[].first` | `string` | No | — | The first time the event was sent |
| `result.data.events[].last` | `string` | No | — | The last time the event was sent |
| `result.data.events[].count` | `integer` | No | — | The number of times the event was sent |
| `result.data.events[].description` | `string` | No | — | The description of the event |
| `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": "This will return a summary of data events for the App.",
        "properties": {
          "type": {
            "type": "string",
            "description": "The type of the object",
            "enum": [
              "event.summary"
            ]
          },
          "email": {
            "type": "string",
            "description": "The email address of the user"
          },
          "intercom_user_id": {
            "type": "string",
            "description": "The Intercom user ID of the user"
          },
          "user_id": {
            "type": "string",
            "description": "The user ID of the user"
          },
          "events": {
            "type": "array",
            "description": "A summary of data events",
            "items": {
              "type": [
                "object",
                "null"
              ],
              "description": "This will return a summary of a data event for the App.",
              "properties": {
                "name": {
                  "type": "string",
                  "description": "The name of the event"
                },
                "first": {
                  "type": "string",
                  "description": "The first time the event was sent"
                },
                "last": {
                  "type": "string",
                  "description": "The last time the event was sent"
                },
                "count": {
                  "type": "integer",
                  "description": "The number of times the event was sent"
                },
                "description": {
                  "type": "string",
                  "description": "The description of the event"
                }
              },
              "additionalProperties": false
            }
          }
        },
        "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.