> ## 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 People Soft Deletion Create

> Soft delete several people from Salesloft by their person IDs, with an optional dry run. Includes inputs, outputs, SDK V2 examples, and Deepline cost.

Soft delete several people from Salesloft by their person IDs, with an optional dry run.

> [!NOTE]
>
> Tool ID: `salesloft_data_control_people_soft_deletion_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.

```ts theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
import { Deepline } from 'deepline';

const deepline = await Deepline.connect();
const result = await deepline.tools.execute(
  'salesloft_data_control_people_soft_deletion_create',
  {
    "people_ids": [
      "people_123"
    ]
  },
);

console.log(result.toolResponse.raw);
```

### CLI

```bash theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
deepline tools execute salesloft_data_control_people_soft_deletion_create --input '{
  "people_ids": [
    "people_123"
  ]
}' --json
```

## Example response

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

```json theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
{
  "data": {
    "team_id": 123,
    "request_type": "example",
    "user_guid": "user_123"
  }
}
```

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

## Input reference

This endpoint supports the ability to soft delete multiple People from Salesloft based on their Salesloft Person ID. This endpoint requires the "data-control" scope for access.

| Name | Type | Required | Default | Details |
| - | - | - | - | - |
| `payload.people_ids` | `array` | Yes | — | List of 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. |

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

  ### Input JSON Schema

  ````json theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
  {
    "type": "object",
    "description": "This endpoint supports the ability to soft delete multiple People from Salesloft based on their Salesloft Person ID. This endpoint requires the \"data-control\" scope for access.",
    "properties": {
      "people_ids": {
        "type": "array",
        "description": "List of 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={"languages":{"custom":["/languages/deepline-prompt.json"]}}
  {
    "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](https://deepline.com/docs/providers/salesloft/guide.md)
* [SDK V2 quickstart](https://deepline.com/docs/sdk-v2/quickstart.md)
* [SDK reference](https://deepline.com/docs/sdk-v2/sdk-reference.md)
* [Run tools across a CSV](https://deepline.com/docs/sdk-v2/batch-csv.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.