> ## Documentation Index
> Fetch the complete documentation index at: https://deepline.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Salesloft: Data Control Right To Be Forgotten Create

> Submit a right to be forgotten request. Includes SDK V2 guidance, input constraints, response fields, and Deepline credit cost.

Submit a right to be forgotten request.

<Info>
  Tool ID: `salesloft_data_control_right_to_be_forgotten_create`
</Info>

## Run this action

Use the TypeScript SDK for a single call. Put `ctx.tools.execute(...)` inside a Play when the call should be durable, scheduled, or run across a CSV.

```ts theme={null}
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

```bash theme={null}
deepline tools execute salesloft_data_control_right_to_be_forgotten_create --input '{
  "people_ids": [
    "people_123"
  ]
}' --json
```

## Example response

The SDK exposes this shape at `result.toolResponse.raw`. Values below are representative.

```json theme={null}
{
  "data": {
    "team_id": 123,
    "request_type": "example",
    "user_guid": "user_123"
  }
}
```

Use `deepline tools get 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](mailto: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: `&#123; "schedule": &#123; "time_of_day": &#123; // this will execute at 5:31pm UTC "hour": 18, "minute": 31, &#125;, "initial_date": "2023-06-26", // YYYY-MM-DD, execution(s) won't start until this date "recurrence": &#123; // when this workflow is executed again "days": 7 // every 7 days &#125; &#125; &#125;` 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.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |

<details>
  <summary>Show raw input schema</summary>

  ### Input JSON Schema

  ````json theme={null}
  {
    "type": "object",
    "description": "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.",
    "properties": {
      "people_ids": {
        "type": "array",
        "description": "People IDs",
        "items": {}
      },
      "team_id": {
        "type": "integer",
        "description": "Internal Use Only"
      },
      "schedule": {
        "type": "object",
        "description": "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 passed, the current date/time will be used for the first execution. Recurrence can also be set to a specific day of the month: ``` \"recurrence\": { \"day_of_month\": 1 // every first of the month \"day_of_month\": 31 // every last day of the month } ``` If the current month doesn't include the given day, it will roll back to the previous valid day. For example, \"day_of_month\" set to 31 in April will execute on the 30th; in February, the 28th."
      },
      "dry_run": {
        "type": "boolean",
        "description": "Whether or not to change data. Defaults to true."
      }
    },
    "required": [
      "people_ids"
    ],
    "additionalProperties": false
  }
  ````
</details>

## 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). |

<details>
  <summary>Show raw output schema</summary>

  ### Output JSON Schema

  ```json theme={null}
  {
    "type": "object",
    "description": "Standard tool result payload.",
    "properties": {
      "data": {
        "type": "object",
        "description": "Provider response payload.",
        "properties": {
          "team_id": {
            "type": "integer",
            "description": "ID of the Request's target team"
          },
          "request_type": {
            "type": "string",
            "description": "Standardized type of the Request"
          },
          "user_guid": {
            "type": "string",
            "description": "ID of the user who created the Request"
          },
          "dry_run": {
            "type": "boolean",
            "description": "Whether or not to change data"
          },
          "metadata": {
            "type": "object",
            "description": "Data that varies across Request types"
          },
          "events": {
            "type": "array",
            "description": "Instances in which a Request has been executed",
            "items": {
              "type": "object",
              "properties": {},
              "additionalProperties": true
            }
          },
          "id": {
            "type": "integer",
            "description": "ID of the Request"
          }
        },
        "additionalProperties": false
      },
      "meta": {
        "type": "object",
        "description": "Additional response metadata (status, paging).",
        "additionalProperties": true
      }
    },
    "required": [
      "data"
    ],
    "additionalProperties": false
  }
  ```
</details>

## Deepline cost

* Pricing model: `fixed` (per call).
* Estimated Deepline credits: `0` per pricing unit.
* Provider-native pricing may still exist outside Deepline credit billing.

## Related documentation

* [Salesloft provider guide](/docs/providers/salesloft/guide)
* [SDK V2 quickstart](/docs/sdk-v2/quickstart)
* [SDK reference](/docs/sdk-v2/sdk-reference)
* [Run tools across a CSV](/docs/sdk-v2/batch-csv)
