Gong: Add Digital Interaction

Record a digital interaction, such as a web visit or content engagement, against a person in Gong.

Tool ID: gong_add_digital_interaction

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.

import { Deepline } from 'deepline';

const deepline = await Deepline.connect();
const result = await deepline.tools.execute(
  'gong_add_digital_interaction',
  {
    "eventId": "event_123",
    "timestamp": "2026-01-15T12:00:00Z",
    "eventType": "example",
    "content": {
      "contentTitle": "example"
    }
  },
);

console.log(result.toolResponse.raw);

CLI

deepline tools execute gong_add_digital_interaction --input '{
  "eventId": "event_123",
  "timestamp": "2026-01-15T12:00:00Z",
  "eventType": "example",
  "content": {
    "contentTitle": "example"
  }
}' --json

Example response

The SDK returns this shape at result.toolResponse.raw. The example values illustrate the response.

{
  "data": {
    "requestId": "request_123"
  }
}

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

Input reference

Digital interaction metadata

Name	Type	Required	Default	Details
`payload.eventId`	`string`	Yes	—	The provider’s unique identifier for the event used for deduplication
`payload.timestamp`	`string`	Yes	—	The date and time of the event in ISO 8601 format Format: `date-time`.
`payload.eventType`	`string`	Yes	—	The type of the event, explaining the content and action performed. Values may be partner-aligned, for example, “link clicked”, “page viewed”
`payload.sourceSystemName`	`string`	No	—	When integrating via IPaaS, the name of the technology partner the customer set up a Gong integration with via an IPaaS. When integrating directly with Gong: the name of the company setting up the integration with Gong
`payload.sessionId`	`string`	No	—	The identifier for the session, useful for tying related events together
`payload.device`	`"MOBILE" \| "PC"`	No	—	The device used during the event Allowed: `MOBILE`, `PC`.
`payload.content`	`object`	Yes	—	The content the person looked at
`payload.person`	`object`	No	—	The person who did the event. Must be null if a tracking ID is sent instead.
`payload.customFields`	`array`	No	—	Include additional custom data about the event
`payload.trackingId`	`string`	No	—	The ID used for tracking the person who did the event. Must be null if a person is sent instead.

This input schema is too large for an inline display. Read the complete live contract with deepline describe gong_add_digital_interaction --json.

Output reference

Standard tool result payload.

Name	Type	Required	Default	Details
`result.data`	`object`	Yes	—	Provider response payload.
`result.data.requestId`	`string`	No	—	A Gong request reference Id, generated for this request. Can be used for troubleshooting purposes.
`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.

​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