Salesloft: Data Control Right To Be Forgotten Create

Submit a right-to-be-forgotten request that deletes people from Salesloft and redacts their personal data.

Tool ID: salesloft_data_control_right_to_be_forgotten_create

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_data_control_right_to_be_forgotten_create',
  {
    "people_ids": [
      "people_123"
    ]
  },
);

console.log(result.toolResponse.raw);

CLI

deepline tools execute salesloft_data_control_right_to_be_forgotten_create --input '{
  "people_ids": [
    "people_123"
  ]
}' --json

Example response

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

{
  "data": {
    "team_id": 123,
    "request_type": "example",
    "user_guid": "user_123"
  }
}

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

Input reference

This endpoint supports soft deleting a Person from Salesloft based on their Salesloft Person ID and redacting all P.I.I. (Personally Identifiable Data) from the Person and related Activity records and notes. This includes hard deletion of call recordings related to that Person in Salesloft as well. Note: This endpoint does not redact or delete Person data from video recordings or video transcripts. To remove a Person from video recordings and video transcripts, submit a support request to support@salesloft.com. Include a statement that the request is a right to be forgotten request and the Salesloft Person ID(s) to be deleted. This endpoint requires the “data-control” scope for access.

Name	Type	Required	Default	Details
`payload.people_ids`	`array`	Yes	—	People IDs
`payload.team_id`	`integer`	No	—	Internal Use Only
`payload.schedule`	`object`	No	—	The date, time, and recurrence of a workflow’s execution. All of these values are optional. Without a schedule, workflows are executed immediately and only once. Example: `{ "schedule": { "time_of_day": { // this will execute at 5:31pm UTC "hour": 18, "minute": 31, }, "initial_date": "2023-06-26", // YYYY-MM-DD, execution(s) won't start until this date "recurrence": { // when this workflow is executed again "days": 7 // every 7 days } } }` If “time_of_day” or “initial_date” has already See the live schema for the complete constraint.
`payload.dry_run`	`boolean`	No	—	Whether or not to change data. Defaults to true.

Output reference

Standard tool result payload.

Name	Type	Required	Default	Details
`result.data`	`object`	Yes	—	Provider response payload.
`result.data.team_id`	`integer`	No	—	ID of the Request’s target team
`result.data.request_type`	`string`	No	—	Standardized type of the Request
`result.data.user_guid`	`string`	No	—	ID of the user who created the Request
`result.data.dry_run`	`boolean`	No	—	Whether or not to change data
`result.data.metadata`	`record`	No	—	Data that varies across Request types
`result.data.events`	`array`	No	—	Instances in which a Request has been executed
`result.data.id`	`integer`	No	—	ID of the Request
`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