Intercom: Lis Data Events

List all data events.

Tool ID: intercom_lis_data_events

Run this action

Use the TypeScript SDK for a single call. Put ctx.tools.execute(...) inside a Play when the call should be durable, scheduled, or run across a CSV.

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

deepline tools execute intercom_lis_data_events --input '{
  "filter": {
    "user_id": "user_123"
  },
  "type": "example"
}' --json

Example response

The SDK exposes this shape at result.toolResponse.raw. Values below are representative.

{
  "data": {
    "type": "event.summary",
    "email": "jane.doe@example.com",
    "intercom_user_id": "intercom_user_123"
  }
}

Use deepline tools get 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 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

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

Deepline cost

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

Get started

Build and automate

Common workflows

Data and integrations

Reference

Intercom: Lis Data Events

Run this action

CLI

Example response

Input reference

Output reference

Deepline cost

​Run this action

​CLI

​Example response

​Input reference

​Output reference

​Deepline cost

​Related documentation

Run this action

CLI

Example response

Input reference

Output reference

Deepline cost

Related documentation