Update Campaign

lemlist.update_campaign
ActionCRM & salesconnection required

Calls the lemlist API with the connection's credentials.

Change a campaign's name or its stop and tracking settings.

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

2 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
campaign_id
The campaign to act on. Falls back to the connection's default campaign when blank.
stringNo——cam_4HrZbi8xsez4QlrnL
fields
The settings to change, as lemlist names them: name, stopOnEmailReplied, stopOnMeetingBooked, disableTrackOpen, autoReview, sendUserIds and the other documented campaign options.
objectYes——{"name":"Q4 outbound","stopOnEmailReplied":true}

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "campaign_id": "cam_4HrZbi8xsez4QlrnL",
  "fields": {
    "name": "Q4 outbound",
    "stopOnEmailReplied": true
  }
}

Output

One shape.

result

The provider's response object, as returned.

Extra keys beyond the ones listed can appear.

{}

See Update Campaign 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.