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

> List all data events. Intercom Intercom Lis Data Events 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_lis_data_events:{"filter":{},"type":"{{type}}"}' --json
```

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

## Input Schema

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

| Name          | Type     | Required | Default | Description                                            |
| ------------- | -------- | -------- | ------- | ------------------------------------------------------ |
| `result.data` | `object` | Yes      |         | This will return a summary of data events for the App. |
| `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": "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>

## Advanced: Direct CLI

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

```bash theme={null}
deepline tools execute intercom_lis_data_events --payload '{
  "filter": {},
  "type": "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`.