Lemlist: Put Watchlist Signals

Mark one or more Lemlist signals as handled or ignored.

Tool ID: lemlist_put_watchlist_signals

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.

import { Deepline } from 'deepline';

const deepline = await Deepline.connect();
const result = await deepline.tools.execute(
  'lemlist_put_watchlist_signals',
  {
    "signalIds": [
      "signal_123"
    ],
    "status": "handled"
  },
);

console.log(result.toolResponse.raw);

CLI

deepline tools execute lemlist_put_watchlist_signals --input '{
  "signalIds": [
    "signal_123"
  ],
  "status": "handled"
}' --json

Example response

The SDK returns this shape at result.toolResponse.raw. The example values illustrate the response.

{
  "data": {
    "data": {
      "updatedCount": 123,
      "requestedCount": 123
    }
  }
}

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

Input reference

Bulk-set the status of one or several signals to handled or ignored.

Name	Type	Required	Default	Details
`payload.signalIds`	`array`	Yes	—	Signal ids (wsi_xxx) to update, from List signals. Between 1 and 1000 per call. Minimum items: 1. Maximum items: 1000.
`payload.status`	`"handled" \| "ignored"`	Yes	—	Target status to set on every signal. Allowed: `handled`, `ignored`.
`payload.reason`	`string`	No	—	Optional note explaining the decision. Only meaningful when status is “ignored”.

Output reference

Standard tool result payload.

Name	Type	Required	Default	Details
`result.data`	`object`	Yes	—	Provider response payload.
`result.data.data`	`object`	No	—	—
`result.data.data.updatedCount`	`integer`	No	—	Number of signals whose status was updated. Can be lower than requestedCount: the write is team-scoped, so ids that were deleted or belong to another team are skipped.
`result.data.data.requestedCount`	`integer`	No	—	Number of signal ids sent in the request
`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.

​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