Salesloft: Call Data Records Index

List the records of all inbound and outbound Salesloft calls, filtered by person, rep, direction, status or date.

Tool ID: salesloft_call_data_records_index

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(
  'salesloft_call_data_records_index',
  {
    "ids": [
      "id_123"
    ],
    "call_uuids": [
      "call_123"
    ],
    "has_call": true
  },
);

console.log(result.toolResponse.raw);

CLI

deepline tools execute salesloft_call_data_records_index --input '{
  "ids": [
    "id_123"
  ],
  "call_uuids": [
    "call_123"
  ],
  "has_call": true
}' --json

Example response

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

{
  "data": [
    {
      "user": {},
      "updated_at": "2026-01-15T12:00:00Z",
      "to": "example"
    }
  ]
}

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

Input reference

Fetches multiple call data records. The records can be filtered, paged, and sorted according to the respective parameters. Call data records are records of all inbound and outbound calls through Salesloft. A call data record may be associated with a call, but does not have to be. Please note: Due to performance, the results will exclusively include records created within the past year.

Name	Type	Required	Default	Details
`payload.ids`	`array`	No	—	IDs of call data records to fetch. If a record can’t be found, that record won’t be returned and your request will be successful
`payload.call_uuids`	`array`	No	—	UUIDs of calls to fetch call data records for. If a record can’t be found, that record won’t be returned and your request will be successful
`payload.has_call`	`boolean`	No	—	Return only call data records which have or do not have a call logged for them
`payload.created_at`	`array`	No	—	Equality filters that are applied to the created_at field. A single filter can be used by itself or combined with other filters to create a range
`payload.updated_at`	`array`	No	—	Equality filters that are applied to the updated_at field. A single filter can be used by itself or combined with other filters to create a range
`payload.user_guid`	`array`	No	—	Filters list to only include guids
`payload.person_id`	`array`	No	—	Filters list by person_id. Multiple person ids can be applied
`payload.direction`	`string`	No	—	Filters by specified direction (inbound or outbound)
`payload.status`	`string`	No	—	Filters by specified status
`payload.sentiment`	`string`	No	—	Filters by specified sentiment
`payload.disposition`	`string`	No	—	Filters by specified disposition
`payload.recordings_only`	`boolean`	No	—	Filters based on the recording existence
`payload.group_id`	`integer`	No	—	Filters list by group id
`payload.sort_by`	`string`	No	—	Key to sort on, must be one of: created_at, updated_at. Defaults to created_at
`payload.sort_direction`	`string`	No	—	Direction to sort in, must be one of: ASC, DESC. Defaults to DESC
`payload.per_page`	`integer`	No	—	How many records to show per page in the range [1, 100]. Defaults to 25
`payload.page`	`integer`	No	—	The current page to fetch results from. Defaults to 1
`payload.include_paging_counts`	`boolean`	No	—	Whether to include total_pages and total_count in the metadata. Defaults to false
`payload.limit_paging_counts`	`boolean`	No	—	Specifies whether the max limit of 10k records should be applied to pagination counts. Affects the total_count and total_pages data
`payload.started_at`	`string`	No	—	Filter by call start time. Supports gt, gte, lt and lte. Combine with more filters to create a range

Output reference

Standard tool result payload.

Name	Type	Required	Default	Details
`result.data`	`array`	Yes	—	Provider response payload.
`result.data[].user`	`record`	No	—	User that made or received the call, if the call was to a user
`result.data[].updated_at`	`string`	No	—	Datetime of when the call was last updated Format: `date-time`.
`result.data[].to`	`string`	No	—	Phone number that received the call
`result.data[].status`	`string`	No	—	The outcome of the call. Can be one of: queued, initiated, ringing, in-progress, completed, busy, no-answer, canceled, failed
`result.data[].started_at`	`string`	No	—	Datetime of when the call started Format: `date-time`.
`result.data[].recording`	`record`	No	—	The recording for this this call data record, with a status
`result.data[].id`	`integer`	No	—	ID of CallDataRecord
`result.data[].from`	`string`	No	—	Phone number that placed the call
`result.data[].ended_at`	`string`	No	—	Datetime of when the call ended Format: `date-time`.
`result.data[].duration`	`integer`	No	—	Length of the call in seconds
`result.data[].direction`	`string`	No	—	Direction of the call. Can be one of: inbound, outbound
`result.data[].dialer_recording`	`record`	No	—	The dialer recording resource for the call recording
`result.data[].created_at`	`string`	No	—	Datetime of when the call was created Format: `date-time`.
`result.data[].called_person`	`record`	No	—	The person called
`result.data[].call_uuid`	`string`	No	—	UUID of the call. Legs of the same call will have the same call_uuid.
`result.data[].call_type`	`string`	No	—	Type of the call. Can be one of: call, bridge, collaboration. Though exact values may change over time
`result.data[].call`	`record`	No	—	Call that this record was logged to, if logged to a call
`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