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

# Close CRM: Close List Lead Statuses

> List Close CRM company lead status labels and ids, such as Potential or Qualified. Includes inputs, outputs, SDK V2 examples, and Deepline cost.

List Close CRM company lead status labels and ids, such as Potential or Qualified.

> [!NOTE]
>
> Tool ID: `close_list_lead_statuses`

## 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(
  'close_list_lead_statuses',
  {},
);

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

### CLI

```bash theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
deepline run close_list_lead_statuses --input '{}'
```

## 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": {
    "data": [
      {
        "color": "blue",
        "id": "id_123",
        "label": "example",
        "organization_id": "organization_123"
      }
    ],
    "has_more": true
  }
}
```

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

## Input reference

Read the available Close CRM lead statuses with their ids and labels, such as Potential or Qualified. These describe company records, not opportunity pipeline stages. Read-only.

This action requires no input fields.

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

  ### Input JSON Schema

  ```json theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
  {
    "type": "object",
    "description": "Read the available Close CRM lead statuses with their ids and labels, such as Potential or Qualified. These describe company records, not opportunity pipeline stages. Read-only.",
    "properties": {},
    "required": [],
    "additionalProperties": false
  }
  ```
</details>

## Output reference

Standard tool result payload.

| Name | Type | Required | Default | Details |
| - | - | - | - | - |
| `result.data` | `object` | Yes | — | Provider response payload. |
| `result.data.data` | `array` | Yes | — | — |
| `result.data.data[].color` | `"blue" \| "gray" \| "green" \| "magenta" \| "orange" \| "purple" \| "teal" \| "yellow"` | Yes | — | Allowed: `blue`, `gray`, `green`, `magenta`, `orange`, `purple`, `teal`, `yellow`. |
| `result.data.data[].id` | `string` | Yes | — | — |
| `result.data.data[].label` | `string` | Yes | — | — |
| `result.data.data[].organization_id` | `string` | Yes | — | — |
| `result.data.has_more` | `boolean` | Yes | — | — |
| `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": {
          "data": {
            "type": "array",
            "items": {
              "type": "object",
              "properties": {
                "color": {
                  "type": [
                    "string",
                    "null"
                  ],
                  "enum": [
                    "blue",
                    "gray",
                    "green",
                    "magenta",
                    "orange",
                    "purple",
                    "teal",
                    "yellow"
                  ]
                },
                "id": {
                  "type": "string"
                },
                "label": {
                  "type": "string"
                },
                "organization_id": {
                  "type": "string"
                }
              },
              "required": [
                "color",
                "id",
                "label",
                "organization_id"
              ],
              "additionalProperties": false
            }
          },
          "has_more": {
            "type": "boolean"
          }
        },
        "required": [
          "data",
          "has_more"
        ],
        "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

* [Connect integrations](https://deepline.com/docs/integrations.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.