Salesloft: CRM Activity Fields Index

List the CRM activity fields Salesloft can fill when logging activities to your CRM.

Tool ID: salesloft_crm_activity_fields_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_crm_activity_fields_index',
  {
    "source": "example",
    "editable_source": "example",
    "sort_by": "example"
  },
);

console.log(result.toolResponse.raw);

CLI

deepline tools execute salesloft_crm_activity_fields_index --input '{
  "source": "example",
  "editable_source": "example",
  "sort_by": "example"
}' --json

Example response

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

{
  "data": [
    {
      "id": 123,
      "created_at": "2026-01-15T12:00:00Z",
      "updated_at": "2026-01-15T12:00:00Z"
    }
  ]
}

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

Input reference

Fetches multiple crm activity field records. The records can be filtered, paged, and sorted according to the respective parameters.

Name	Type	Required	Default	Details
`payload.source`	`string`	No	—	Return only records with this source
`payload.editable_source`	`string`	No	—	Return only records with this editable source
`payload.sort_by`	`string`	No	—	Key to sort on, must be one of: title, updated_at. Defaults to title
`payload.sort_direction`	`string`	No	—	Direction to sort in, must be one of: ASC, DESC. Defaults to ASC
`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

Output reference

Standard tool result payload.

Name	Type	Required	Default	Details
`result.data`	`array`	Yes	—	Provider response payload.
`result.data[].id`	`integer`	No	—	ID of CrmActivityField
`result.data[].created_at`	`string`	No	—	Datetime of when the CrmActivityField was created Format: `date-time`.
`result.data[].updated_at`	`string`	No	—	Datetime of when the CrmActivityField was last updated Format: `date-time`.
`result.data[].title`	`string`	No	—	A human friendly title for this field
`result.data[].salesforce_object_type`	`string`	No	—	The Salesforce object type that this field maps to. Valid object types are: Task. More object types may be added in the future.
`result.data[].crm_object_type`	`string`	No	—	The CRM object type that this field maps to. Valid object types are CRM dependent: Task, Phonecall, Email.
`result.data[].source`	`string`	No	—	SalesLoft object that this field is mapped for. Valid sources are: email, phone
`result.data[].field`	`string`	No	—	The CRM field name
`result.data[].field_type`	`string`	No	—	The type of this field in your CRM. Certain field types can only accept structured input.
`result.data[].value`	`string`	No	—	A value to always be written. This value does not need to be sent to other endpoints’ crm params, but must be the exact value if sent. Email source fields will always have a value present.
`result.data[].picklist_values`	`record`	No	—	Valid picklist values, if present for this field. The format is {label => value}. If present, only values in the picklist structure can be used as a crm param.
`result.data[].nillable`	`boolean`	No	—	Whether this field can be left empty in the CRM. False means the field is required.
`result.data[].createable`	`boolean`	No	—	Whether this field can be set during record creation.
`result.data[].defaulted_on_create`	`boolean`	No	—	Whether this field is automatically populated by the CRM on record creation.
`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