Lemlist: Update Saved Search

Update Saved Search.

Tool ID: lemlist_update_saved_search

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.

import { Deepline } from 'deepline';

const deepline = await Deepline.connect();
const result = await deepline.tools.execute(
  'lemlist_update_saved_search',
  {
    "savedSearchId": "saved_search_123"
  },
);

console.log(result.toolResponse.raw);

CLI

deepline tools execute lemlist_update_saved_search --input '{
  "savedSearchId": "saved_search_123"
}' --json

Example response

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

{
  "data": {
    "data": {
      "_id": "_123",
      "name": "Example",
      "mode": "leads"
    }
  }
}

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

Input reference

Renames a saved search and/or replaces its filters. At least one of name and filters is required. filters replace the saved filters entirely: they are not merged. mode is only read together with filters and defaults to the current mode of the saved search. Filters come from Get Database Filters called with usage=ui: a filter not usable in the People Database UI is refused with FILTER_UNAVAILABLE_FOR_USAGE, and the error message names the refused filters, comma-separated. Filters incompatible with the mode or with your team’s plan are dropped silently; if none remain, the request answers 400. The filters and the name are applied as two separate writes: if the rename is refused because the name is already taken (409), the new filters are already saved.

Name	Type	Required	Default	Details
`payload.savedSearchId`	`string`	Yes	—	Id of the saved search Minimum length: 1.
`payload.name`	`string`	No	—	Display name, 1 to 200 characters after trimming. Unique within your team. Minimum length: 1. Maximum length: 200.
`payload.filters`	`array`	No	—	New filters, replacing the saved ones entirely. 1 to 10 filters of shape `{ filterId, in?, out?, exactMatch? }` (no other key: an unknown key such as `type` answers `API_INVALID_FILTERS`), at most 1000 values per `in` / `out` and 1000 characters per value. Minimum items: 1. Maximum items: 10.
`payload.mode`	`"leads" \| "companies"`	No	—	Search mode of the new `filters`. Only read with `filters`; defaults to the current mode of the saved search. Allowed: `leads`, `companies`.

Output reference

Standard tool result payload.

Name	Type	Required	Default	Details
`result.data`	`object`	Yes	—	Provider response payload.
`result.data.data`	`object`	No	—	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.
`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 or Search Companies Database.
`result.data.data.filters[].filterId`	`string`	Yes	—	People Database filter identifier. Use 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).

Deepline cost

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

Get started

Build and automate

Common workflows

Data and integrations

Reference

Lemlist: Update Saved Search

Run this action

CLI

Example response

Input reference

Output reference

Deepline cost

​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