Lemlist: Patch Watchlist

Update Signal Agent.

Tool ID: lemlist_patch_watchlist

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_patch_watchlist',
  {
    "watchListId": "watch_list_123"
  },
);

console.log(result.toolResponse.raw);

CLI

deepline tools execute lemlist_patch_watchlist --input '{
  "watchListId": "watch_list_123"
}' --json

Example response

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

{
  "data": {
    "data": {
      "_id": "_123",
      "name": "Example",
      "type": "companyIsHiring"
    }
  }
}

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

Input reference

Update Signal Agent

Name	Type	Required	Default	Details
`payload.watchListId`	`string`	Yes	—	Signal Agent id to update
`payload.name`	`string`	No	—	New display name
`payload.filters`	`array`	No	—	Replacement filters (validated against the agent’s signal type)
`payload.emoji`	`string`	No	—	New emoji
`payload.signalProcessingType`	`"manual" \| "create_opportunity" \| "push_to_campaign"`	No	—	New signal processing type Allowed: `manual`, `create_opportunity`, `push_to_campaign`.
`payload.personaId`	`string`	No	—	Persona (pdp_xxx) used to source contacts from the People Database. Only for a company Signal Agent with signalProcessingType = push_to_campaign whose signal type does not already ship its own contact. Optional; rejected on any other configuration.
`payload.activate`	`boolean`	No	—	Toggle the agent status. false deactivates (pauses) it immediately. true reactivates a paused agent (triggers billing and external watcher setup). A draft cannot be toggled this way. Omit to leave the status unchanged.

Output reference

Standard tool result payload.

Name	Type	Required	Default	Details
`result.data`	`object`	Yes	—	Provider response payload.
`result.data.data`	`object`	No	—	A Signal Agent (watch list) configuration.
`result.data.data._id`	`string`	No	—	Unique Signal Agent identifier
`result.data.data.name`	`string`	No	—	Display name
`result.data.data.type`	"companyIsHiring" \| "companyRaisedFunds" \| "recruitmentCampaign" \| "jobChange" \| "newHire" \| "companyEmployeeVisitedMyWebsite" \| "customSignals" \| "competitorConnections" \| "competitorReactions" \| "technologyChange" \| "linkedinPeopleProfile" \| "linkedinCompanyProfile" \| "mergersAcquisitions" \| "promotion" \| "linkedinKeywords" \| "republishedJobOffers" \| "externalSignalContact" \| "externalSignalCompany" \| "buyingIntent" \| "newProductLaunch" \| "companyAward" \| "newPartnership" \| "newOffice" \| "closingOffice" \| "costCutting" \| "outagesAndSecurityBreaches" \| "lawsuitsAndLegalIssues" \| "githubStargazer"	No	—	Signal type monitored by this Signal Agent Allowed: `companyIsHiring`, `companyRaisedFunds`, `recruitmentCampaign`, `jobChange`, `newHire`, `companyEmployeeVisitedMyWebsite`, `customSignals`, `competitorConnections`, `competitorReactions`, `technologyChange`, `linkedinPeopleProfile`, `linkedinCompanyProfile`, `mergersAcquisitions`, `promotion`, `linkedinKeywords`, `republishedJobOffers`, `externalSignalContact`, `externalSignalCompany`, `buyingIntent`, `newProductLaunch`, `companyAward`, See the live schema for the complete constraint.
`result.data.data.status`	`"active" \| "inactive" \| "draft" \| "insufficient_credits" \| "empty_crm_lists" \| "error" \| "delete"`	No	—	Lifecycle status Allowed: `active`, `inactive`, `draft`, `insufficient_credits`, `empty_crm_lists`, `error`, `delete`.
`result.data.data.entity`	`"contact" \| "company"`	No	—	Entity kind the agent tracks Allowed: `contact`, `company`.
`result.data.data.segmentType`	`"all" \| "list" \| "csv"`	No	—	How the monitored entities are sourced Allowed: `all`, `list`, `csv`.
`result.data.data.signalProcessingType`	`"manual" \| "create_opportunity" \| "push_to_campaign"`	No	—	How detected signals are processed Allowed: `manual`, `create_opportunity`, `push_to_campaign`.
`result.data.data.signalOpportunityTemplate`	`object`	No	—	Task/opportunity template applied to each signal when signalProcessingType is create_opportunity.
`result.data.data.signalOpportunityTemplate.ownerType`	`"contact_owner" \| "specific_owner"`	No	—	Who the created opportunity is assigned to Allowed: `contact_owner`, `specific_owner`.
`result.data.data.signalOpportunityTemplate.ownerId`	`string`	No	—	Owner user id, when ownerType is specific_owner
`result.data.data.signalOpportunityTemplate.type`	`"email" \| "phone" \| "linkedinSend" \| "whatsappMessage" \| "manual"`	No	—	Opportunity channel Allowed: `email`, `phone`, `linkedinSend`, `whatsappMessage`, `manual`.
`result.data.data.signalOpportunityTemplate.priority`	`0 \| 1 \| 2`	No	—	Opportunity priority Allowed: `0`, `1`, `2`.
`result.data.data.signalOpportunityTemplate.data`	`object`	No	—	—
`result.data.data.signalOpportunityTemplate.data.title`	`string`	No	—	Opportunity title
`result.data.data.signalOpportunityTemplate.data.subject`	`string`	No	—	Email subject (email channel)
`result.data.data.signalOpportunityTemplate.data.emailTemplateId`	`string`	No	—	Email template id
`result.data.data.signalOpportunityTemplate.data.message`	`string`	No	—	Message body
`result.data.data.filters`	`array`	No	—	Filters narrowing which entities/events are tracked
`result.data.data.filters[].filterId`	"title" \| "description" \| "location" \| "visitLocation" \| "website" \| "pagesTracked" \| "minVisitDuration" \| "minPageViewed" \| "internalTraffic" \| "linkedinUrls" \| "companyLinkedinUrls" \| "companyNames" \| "companyLocation" \| "companyIndustries" \| "companySizes" \| "maxIdentificationsPerDay" \| "excludedVisitorIps" \| "reactionTypes" \| "linkedinTopics" \| "bomboraTopics" \| "watcherWatchKey" \| "questions" \| "fundraisingMinAmount" \| "fundraisingMaxAmount" \| "fundraisingInvestmentTypes" \| "fundraisingInvestors" \| "technologies" \| "detectionMode" \| "maDealTypes" \| "maMinAmount" \| "persona" \| "customPersonaTitles" \| "externalSignalFieldMapping" \| "externalSignalCustomFieldMapping" \| "seniority" \| "crmListIds" \| "minJobCount" \| "timeframe" \| "githubRepoUrls"	Yes	—	Filter identifier Allowed: `title`, `description`, `location`, `visitLocation`, `website`, `pagesTracked`, `minVisitDuration`, `minPageViewed`, `internalTraffic`, `linkedinUrls`, `companyLinkedinUrls`, `companyNames`, `companyLocation`, `companyIndustries`, `companySizes`, `maxIdentificationsPerDay`, `excludedVisitorIps`, `reactionTypes`, `linkedinTopics`, `bomboraTopics`, `watcherWatchKey`, `questions`, `fundraisingMinAmount`, `fundraisingMaxAmount`, `fundraisingInvestmentTypes`, See the live schema for the complete constraint.
`result.data.data.filters[].in`	`array`	No	—	Values to include
`result.data.data.filters[].out`	`array`	No	—	Values to exclude
`result.data.data.emoji`	`string`	No	—	Emoji shown next to the agent name
`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: Patch Watchlist

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