{
"sequenceId": "seq_jacL5GNH3YpNnuNQ2",
"index": 0,
"key": "customLeadInfo",
"name": "Founders and CEOs",
"customField": "variables.jobTitle",
"customOperator": "contains",
"customValues": [
"CEO",
"Founder"
]
}{
"error": "Nothing to update",
"code": "SEQUENCE_BRANCH_NO_UPDATE"
}The authentication you supplied is incorrectroute is available starting emailPro plan{
"error": "Condition branches are not enabled for this team",
"code": "SEQUENCE_BRANCH_BETA_REQUIRED"
}{
"error": "No branch with this sequenceId on this step",
"code": "SEQUENCE_BRANCH_NOT_FOUND"
}{
"error": "You cannot add, remove or reorder branches once leads have entered the campaign",
"code": "SEQUENCE_BRANCH_CAMPAIGN_RUNNING"
}Update Condition Branch
Renames a branch and/or changes what it tests.
{
"sequenceId": "seq_jacL5GNH3YpNnuNQ2",
"index": 0,
"key": "customLeadInfo",
"name": "Founders and CEOs",
"customField": "variables.jobTitle",
"customOperator": "contains",
"customValues": [
"CEO",
"Founder"
]
}{
"error": "Nothing to update",
"code": "SEQUENCE_BRANCH_NO_UPDATE"
}The authentication you supplied is incorrectroute is available starting emailPro plan{
"error": "Condition branches are not enabled for this team",
"code": "SEQUENCE_BRANCH_BETA_REQUIRED"
}{
"error": "No branch with this sequenceId on this step",
"code": "SEQUENCE_BRANCH_NOT_FOUND"
}{
"error": "You cannot add, remove or reorder branches once leads have entered the campaign",
"code": "SEQUENCE_BRANCH_CAMPAIGN_RUNNING"
}SEQUENCE_BRANCH_NO_UPDATE.
Renaming
name is the branch’s display name. An empty string clears it, and lemlist goes back to labelling
the branch by its rank (“Branch 1”, “Branch 2”, …). The Else branch cannot be renamed:
SEQUENCE_BRANCH_IS_FALLBACK.
Changing what the branch tests
Send the same parametersPOST /sequences/{sequenceId}/steps takes
for a condition — customField, customOperator, customValue, scoreComparator,
scoreThreshold, emailStatusFilter, callStatusFilter. conditionKey is refused: every branch of
a step shares the step’s condition, and changing it is a change to the step, not to one branch.
On a customLeadInfo step, changing customField changes it on every branch — a step tests one
field, and each branch keeps its own operator and values.
The two halves are gated differently
Once leads have entered the campaign:| Body | Result |
|---|---|
{ "name": "Founders" } | applied — a rename never re-routes a lead |
{ "customValue": "CTO" } | 409 — re-routing live leads would strand those already sent down the old value |
{ "name": "Founders", "customValue": "CTO" } | 409, and the rename does not land either |
hasScore, aircallDone), a body
carrying only delay changes how long the condition waits, not what it waits for, and is applied.
Adding any other selector field to that body locks it again.Authorizations
Path Parameters
Body
customLeadInfo only - the field to test. A bare name reads as a lead variable (jobTitle becomes variables.jobTitle); prefix with fields. to test a contact field. A company field is written company.<field> - company.name, or company.sector for a company custom field named Sector - and companyName or variables.companyName is stored as company.name. Every branch of a step tests the same field, so changing it here changes it on all of them.
Response
The branch as it now stands.
One branch of a condition step. Addressed by sequenceId - the sub-sequence its leads walk - never by position. The fields describing what the branch tests depend on the step's condition; the ones that do not apply are absent.
customLeadInfo only - the tested field, normalized: a lead variable reads back as variables.<name>, a contact field as fields.<name>, a company field as company.<field> (e.g. company.name), or as variables.company<Field> (e.g. variables.companyName) on a step that already tested it that way, which tests the same value. Every branch of the step tests the same field.
Was this page helpful?