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

# Lemlist: List Saved Searches

> List Saved Searches. Lemlist List Saved Searches reference includes SDK V2 and CLI requests, input constraints, response fields, and Deepline cost.

List Saved Searches.

<Info>
  Tool ID: `lemlist_list_saved_searches`
</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(
  'lemlist_list_saved_searches',
  {
    "mode": "leads"
  },
);

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

### CLI

```bash theme={null}
deepline tools execute lemlist_list_saved_searches --input '{
  "mode": "leads"
}' --json
```

## Example response

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

```json theme={null}
{
  "data": {
    "data": [
      {
        "_id": "_123",
        "name": "Example",
        "mode": "leads"
      }
    ]
  }
}
```

Use `deepline tools get lemlist_list_saved_searches --json` for the latest machine-readable contract.

## Input reference

Lists the People Database saved searches of your team, sorted by name. Saved searches are team-shared: every member sees the same list.

| Name | Type | Required | Default | Details |
| - | - | - | - | - |
| `payload.mode` | `"leads" \| "companies"` | No | — | Restrict the list to saved searches of one search mode. Saved searches created before modes existed are returned for both modes. Omit to return every saved search of the team. Allowed: `leads`, `companies`. |

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

  ### Input JSON Schema

  ```json theme={null}
  {
    "type": "object",
    "description": "Lists the People Database saved searches of your team, sorted by name. Saved searches are team-shared: every member sees the same list.",
    "properties": {
      "mode": {
        "type": "string",
        "description": "Restrict the list to saved searches of one search mode. Saved searches created before modes existed are returned for both modes. Omit to return every saved search of the team.",
        "enum": [
          "leads",
          "companies"
        ]
      }
    },
    "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` | No | — | The team's saved searches, sorted by name |
| `result.data.data[]._id` | `string` | No | — | Unique saved search identifier |
| `result.data.data[].name` | `string` | No | — | Display name. Unique within your team. |
| `result.data.data[].mode` | `"leads" \| "companies"` | No | — | Search mode the filters target. Always set: saved searches created before modes existed read as `leads`. Allowed: `leads`, `companies`. |
| `result.data.data[].filters` | `array` | No | — | People Database filters of the saved search. Same shape as the search endpoints accept, so they can be sent back as is to [Search People Database](/docs/api-reference/endpoints/people-database/search-people-database) or [Search Companies Database](/docs/api-reference/endpoints/people-database/search-companies-database). |
| `result.data.data[].filters[].filterId` | `string` | Yes | — | People Database filter identifier. Use [Get Database Filters](/docs/api-reference/endpoints/people-database/get-database-filters) to discover the valid ids. |
| `result.data.data[].filters[].in` | `array` | No | — | Values to include |
| `result.data.data[].filters[].out` | `array` | No | — | Values to exclude |
| `result.data.data[].filters[].exactMatch` | `boolean` | No | — | Exact-match toggle, for the text filters that support it |
| `result.data.data[].createdAt` | `string` | No | — | Date the saved search was created Format: `date-time`. |
| `result.data.data[].lastResultsCount` | `number` | No | — | Number of results the saved search returned the last time it was saved or run |
| `result.data.data[].lastResultsCountUpdatedAt` | `string` | No | — | Date `lastResultsCount` was last computed Format: `date-time`. |
| `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": {
          "data": {
            "type": "array",
            "description": "The team's saved searches, sorted by name",
            "items": {
              "type": "object",
              "description": "A People Database saved search: a named set of People Database filters saved by your team. It appears in the \"Saved searches\" menu of the People Database.",
              "properties": {
                "_id": {
                  "type": "string",
                  "description": "Unique saved search identifier"
                },
                "name": {
                  "type": "string",
                  "description": "Display name. Unique within your team."
                },
                "mode": {
                  "type": "string",
                  "description": "Search mode the filters target. Always set: saved searches created before modes existed read as `leads`.",
                  "enum": [
                    "leads",
                    "companies"
                  ]
                },
                "filters": {
                  "type": "array",
                  "description": "People Database filters of the saved search. Same shape as the search endpoints accept, so they can be sent back as is to [Search People Database](/api-reference/endpoints/people-database/search-people-database) or [Search Companies Database](/api-reference/endpoints/people-database/search-companies-database).",
                  "items": {
                    "type": "object",
                    "description": "One People Database filter, as stored in a persona or a saved search. `in` includes matching values, `out` excludes them. There is no `type` property: it is derived from `filterId` server-side.",
                    "properties": {
                      "filterId": {
                        "type": "string",
                        "description": "People Database filter identifier. Use [Get Database Filters](/api-reference/endpoints/people-database/get-database-filters) to discover the valid ids."
                      },
                      "in": {
                        "type": "array",
                        "description": "Values to include",
                        "items": {
                          "type": "string"
                        }
                      },
                      "out": {
                        "type": "array",
                        "description": "Values to exclude",
                        "items": {
                          "type": "string"
                        }
                      },
                      "exactMatch": {
                        "type": "boolean",
                        "description": "Exact-match toggle, for the text filters that support it"
                      }
                    },
                    "required": [
                      "filterId"
                    ],
                    "additionalProperties": false
                  }
                },
                "createdAt": {
                  "type": "string",
                  "description": "Date the saved search was created",
                  "format": "date-time"
                },
                "lastResultsCount": {
                  "type": "number",
                  "description": "Number of results the saved search returned the last time it was saved or run"
                },
                "lastResultsCountUpdatedAt": {
                  "type": "string",
                  "description": "Date `lastResultsCount` was last computed",
                  "format": "date-time"
                }
              },
              "additionalProperties": false
            }
          }
        },
        "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

* [Lemlist provider guide](/docs/providers/lemlist/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)


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