Lemlist: Get V2 Tasks Filters

List Task Filters.

Tool ID: lemlist_get_v2_tasks_filters

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_get_v2_tasks_filters',
  {
    "scope": "task",
    "search": "software companies hiring engineers"
  },
);

console.log(result.toolResponse.raw);

CLI

deepline tools execute lemlist_get_v2_tasks_filters --input '{
  "scope": "task",
  "search": "software companies hiring engineers"
}' --json

Example response

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

{
  "data": {
    "results": [
      {
        "field": "email",
        "label": "example",
        "scope": "task"
      }
    ],
    "total": 123
  }
}

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

Input reference

Lists every field addressable by advancedFilters on GET /v2/tasks, with its type, its allowed operators and the flat query parameter that addresses it, when there is one. The team’s custom fields are included.

Name	Type	Required	Default	Details
`payload.scope`	`"task" \| "contact" \| "company"`	No	—	Restricts the response to one section. Allowed: `task`, `contact`, `company`.
`payload.search`	`string`	No	—	Keeps the fields whose id or label contains this text.

Output reference

Standard tool result payload.

Name	Type	Required	Default	Details
`result.data`	`object`	Yes	—	Response of `GET /v2/tasks/filters`.
`result.data.results`	`array`	No	—	—
`result.data.results[].field`	`string`	No	—	Field id, as used in an `advancedFilters` condition
`result.data.results[].label`	`string`	No	—	Human-readable name
`result.data.results[].scope`	`"task" \| "contact" \| "company"`	No	—	Section the field belongs to Allowed: `task`, `contact`, `company`.
`result.data.results[].type`	`"text" \| "number" \| "date" \| "enum" \| "relation" \| "tags" \| "boolean"`	No	—	Data type, which decides the allowed operators Allowed: `text`, `number`, `date`, `enum`, `relation`, `tags`, `boolean`.
`result.data.results[].custom`	`boolean`	No	—	True for a custom field of the team
`result.data.results[].operators`	`array`	No	—	Operators allowed on this field
`result.data.results[].queryParam`	`string \| null`	No	—	Flat query parameter addressing this field; `null` means `advancedFilters` only
`result.data.results[].values`	`array \| null`	No	—	Reserved — always `null` today
`result.data.total`	`integer`	No	—	—
`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: Get V2 Tasks Filters

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