Salesloft: Actions Index

List the in-progress Salesloft actions (steps due for a rep), filtered by cadence, step, person, type or due date.

Tool ID: salesloft_actions_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_actions_index',
  {
    "ids": [
      123
    ],
    "step_id": 123,
    "type": "example"
  },
);

console.log(result.toolResponse.raw);

CLI

deepline tools execute salesloft_actions_index --input '{
  "ids": [
    123
  ],
  "step_id": 123,
  "type": "example"
}' --json

Example response

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

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

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

Input reference

Fetches multiple action records. The records can be filtered, paged, and sorted according to the respective parameters. Only actions that are currently “in_progess” will be returned by this endpoint. If the requester is not an admin, this endpoint will only return actions belonging to the requester. If the request is an admin, this endpoint will return actions for the entire team. Additionaly, an admin may use the user_guid parameter to request actions that belong to specific users on the team.

Name	Type	Required	Default	Details
`payload.ids`	`array`	No	—	IDs of actions to fetch.
`payload.step_id`	`integer`	No	—	Fetch actions by step ID
`payload.type`	`string`	No	—	Filter actions by type
`payload.due_on`	`object`	No	—	Returns all matching records that are greater than the provided iso8601 timestamp. The comparison is done using microsecond precision.
`payload.user_guid`	`array`	No	—	Filters actions by the user’s guid. Multiple user guids can be applied. The user must be a team admin to filter other users’ actions
`payload.person_id`	`array`	No	—	Filters actions by person_id. Multiple person ids can be applied
`payload.cadence_id`	`array`	No	—	Filters actions by cadence_id. Multiple cadence ids can be applied
`payload.multitouch_group_id`	`array`	No	—	Filters actions by multitouch_group_id. Multiple multitouch group ids can be applied
`payload.updated_at`	`object`	No	—	Returns all matching records that are greater than the provided iso8601 timestamp. The comparison is done using microsecond precision.
`payload.sort_by`	`string`	No	—	Key to sort on, must be one of: created_at, updated_at. Defaults to updated_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

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 Action
`result.data[].due`	`boolean`	No	—	Whether this step is due
`result.data[].created_at`	`string`	No	—	Datetime of when the Action was created Format: `date-time`.
`result.data[].updated_at`	`string`	No	—	Datetime of when the Action was last updated Format: `date-time`.
`result.data[].type`	`string`	No	—	The type of this action. Valid types are: email, phone, other. New types may be added in the future.
`result.data[].status`	`string`	No	—	The current state of the person on the cadence. Possible values are: in_progress: this action has not been completed pending_activity: this action has been acted upon, but the action has not been completed. (i.e. the email is scheduled to send, but has not been delivered yet)
`result.data[].due_on`	`string`	No	—	When action is due Format: `date-time`.
`result.data[].multitouch_group_id`	`integer`	No	—	ID of the multitouch group
`result.data[].action_details`	`object`	No	—	The type specific action details
`result.data[].action_details.id`	`integer`	No	—	—
`result.data[].action_details._href`	`string`	No	—	—
`result.data[].user`	`object`	No	—	User assigned to action
`result.data[].user.id`	`integer`	No	—	—
`result.data[].user._href`	`string`	No	—	—
`result.data[].person`	`object`	No	—	The subject of an action
`result.data[].person.id`	`integer`	No	—	—
`result.data[].person._href`	`string`	No	—	—
`result.data[].cadence`	`object`	No	—	The cadence of an action
`result.data[].cadence.id`	`integer`	No	—	—
`result.data[].cadence._href`	`string`	No	—	—
`result.data[].step`	`object`	No	—	The step of an action
`result.data[].step.id`	`integer`	No	—	—
`result.data[].step._href`	`string`	No	—	—
`result.data[].task`	`object`	No	—	The task associated with an action
`result.data[].task.id`	`integer`	No	—	—
`result.data[].task._href`	`string`	No	—	—
`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