Intercom: Create Data Event

Submit a data event.

Tool ID: intercom_create_data_event

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_create_data_event',
  {
    "event_name": "Example",
    "created_at": 123,
    "user_id": "user_123"
  },
);

console.log(result.toolResponse.raw);

CLI

deepline tools execute intercom_create_data_event --input '{
  "event_name": "Example",
  "created_at": 123,
  "user_id": "user_123"
}' --json

Example response

The static output schema is not detailed enough to generate a reliable example. Use deepline tools get intercom_create_data_event --json for the complete live contract.

Input reference

You will need an Access Token that has write permissions to send Events. Once you have a key you can submit events via POST to the Events resource, which is located at https://api.intercom.io/events, or you can send events using one of the client libraries. When working with the HTTP API directly a client should send the event with a Content-Type of application/json. When using the JavaScript API, adding the code to your app makes the Events API available. Once added, you can submit an event using the trackEvent method. This will associate the event with the Lead or currently logged-in user or logged-out visitor/lead and send it to Intercom. The final parameter is a map that can be used to send optional metadata about the event. With the Ruby client you pass a hash describing the event to See the live schema below for the complete notes.

Name	Type	Required	Default	Details
`payload.event_name`	`string`	No	—	The name of the event that occurred. This is presented to your App’s admins when filtering and creating segments - a good event name is typically a past tense ‘verb-noun’ combination, to improve readability, for example `updated-plan`.
`payload.created_at`	`integer`	No	—	The time the event occurred as a UTC Unix timestamp Format: `date-time`.
`payload.user_id`	`string`	No	—	Your identifier for the user.
`payload.id`	`string`	No	—	The unique identifier for the contact (lead or user) which is given by Intercom.
`payload.email`	`string`	No	—	An email address for your user. An email should only be used where your application uses email to uniquely identify users.
`payload.metadata`	`record`	No	—	Optional metadata about the event.

Output reference

Standard tool result payload.

Name	Type	Required	Default	Details
`result.data`	`unknown`	Yes	—	Provider response payload.
`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: Create Data Event

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