Add Unsubscribe
lemlist.add_unsubscribe
ActionCRM & salesconnection required
Calls the lemlist API with the connection's credentials.
Add an address, or a whole domain, to the team's unsubscribe list.
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
1 field, 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 |
|---|---|---|---|---|---|
email The address to unsubscribe, or a domain to block entirely. | string | Yes | — | — | john.doe@example.com |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"email": "john.doe@example.com"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
id The id of the unsubscribe record lemlist created. | string | — |
value The address or domain that is now unsubscribed. | string | — |
unsubscribed True once lemlist accepted the entry. | boolean | — |
{
"id": "",
"unsubscribed": false,
"value": ""
}See Add Unsubscribe 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.