Update Lead
lemlist.update_lead
ActionCRM & salesconnection required
Calls the lemlist API with the connection's credentials.
Update a lead's details inside one campaign.
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, 2 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_id The lead to update. | string | Yes | — | — | lea_fiDpiGV585wy3Oii2 |
fields The values to change, as lemlist names them: firstName, lastName, companyName, jobTitle and preferredContactMethod (email or linkedIn). | object | Yes | — | — | {"jobTitle":"Head of Growth"} |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"campaign_id": "cam_4HrZbi8xsez4QlrnL",
"fields": {
"jobTitle": "Head of Growth"
},
"lead_id": "lea_fiDpiGV585wy3Oii2"
}Output
One shape.
result
The provider's response object, as returned.
Extra keys beyond the ones listed can appear.
{}See Update 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.