Lemlist: List Personas

List Personas.

Tool ID: lemlist_list_personas

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_list_personas',
  {
    "mode": "leads"
  },
);

console.log(result.toolResponse.raw);

CLI

deepline tools execute lemlist_list_personas --input '{
  "mode": "leads"
}' --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_list_personas --json for the latest machine-readable contract.

Input reference

Lists the personas saved by your team. A persona is a named, reusable set of People Database filters; its id can then be referenced elsewhere in the API, for example through the persona filter of a Signal Agent. Personas are team-shared: every member sees the same list. Results are sorted by creation date, most recent first, and capped at 200. The auto-generated persona lemlist derives from your AI business context is never returned; only the personas your team created are. This endpoint is in closed beta and answers 403 unless the beta is enabled for your team.

Name	Type	Required	Default	Details
`payload.mode`	`"leads" \| "companies"`	No	—	Restrict the list to personas of one search mode. Omit to return every persona of the team. Allowed: `leads`, `companies`.

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 personas, most recently created first
`result.data.data[]._id`	`string`	No	—	Unique persona 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 Allowed: `leads`, `companies`.
`result.data.data[].filters`	`array`	No	—	People Database filters defining the persona
`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 persona was created Format: `date-time`.
`result.data.data[].updatedAt`	`string`	No	—	Date of the last modification 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: List Personas

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