Delete or Unsubscribe Lead
lemlist.delete_lead
ActionCRM & salesconnection required
Calls the lemlist API with the connection's credentials.
Unsubscribe a lead from a campaign, or delete it outright.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- API key
- Providers
- lemlist
- Secret shape
- the API key, or {"api_key": "…"}
- Config it needs
- campaign_id
- Resolved by
- config.connection_id, else node.connection_id
Configuration
3 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
campaign_id The campaign to act on. Falls back to the connection's default campaign when blank. | string | No | — | — | cam_4HrZbi8xsez4QlrnL |
lead The lead to remove, named by lead id or by email address. | string | Yes | — | — | — |
action Unsubscribe keeps the lead on the campaign; remove deletes it. | string | No | unsubscribe | one of "unsubscribe", "remove" | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"action": "unsubscribe",
"campaign_id": "cam_4HrZbi8xsez4QlrnL"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
lead_id The id of the lead lemlist acted on. | string | — |
email The email address of that lead. | string | — |
campaign_id The campaign the call acted on. | string | — |
action Which of unsubscribe or remove was asked for. | string | — |
removed True only when the lead was deleted, not unsubscribed. | boolean | — |
{
"action": "",
"campaign_id": "",
"email": "",
"lead_id": "",
"removed": false
}See Delete or Unsubscribe Lead run in a workflow.
In a technical demo we add the lemlist connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.