Lemlist: Patch Sequences Sequenceid Steps Stepid Ab Test

Edit variant B of the A/B test on a Lemlist sequence step: subject, message or CC.

Tool ID: lemlist_patch_sequences_sequenceid_steps_stepid_ab_test

Run this action

Use the TypeScript SDK for one call. Use ctx.tools.execute(...) inside a Play for durable calls, scheduled calls, or CSV processing.

import { Deepline } from 'deepline';

const deepline = await Deepline.connect();
const result = await deepline.tools.execute(
  'lemlist_patch_sequences_sequenceid_steps_stepid_ab_test',
  {
    "sequenceId": "sequence_123",
    "stepId": "step_123"
  },
);

console.log(result.toolResponse.raw);

CLI

deepline tools execute lemlist_patch_sequences_sequenceid_steps_stepid_ab_test --input '{
  "sequenceId": "sequence_123",
  "stepId": "step_123"
}' --json

Example response

The SDK returns this shape at result.toolResponse.raw. The example values illustrate the response.

{
  "data": {
    "stepId": "step_123",
    "abTest": true,
    "emailTemplateBId": "jane.doe@example.com"
  }
}

Use deepline describe lemlist_patch_sequences_sequenceid_steps_stepid_ab_test --json for the latest machine-readable contract.

Input reference

Edits variant B content/config of the A/B test on a step. Only the provided fields are updated. unknown fields are rejected. Allowed while the campaign is running. Requires the Email Pro plan.

Name	Type	Required	Default	Details
`payload.sequenceId`	`string`	Yes	—	The unique identifier of the sequence
`payload.stepId`	`string`	Yes	—	The unique identifier of the step
`payload.subject`	`string`	No	—	Variant B subject. An empty string removes it: variant B then replies in the thread of the previous email sent to the lead in this campaign, like variant A would.
`payload.message`	`string`	No	—	Variant B body (HTML). An empty string is rejected, except on LinkedIn invite steps where it means “invite without a note”
`payload.altMessage`	`string`	No	—	Variant B’s LinkedIn note, same meaning as the step-level `altMessage`: the premium invitation note on a `linkedinInvite` step, the out-of-network note on a `linkedinSend` one. On a `linkedinInvite` step, over 300 characters is rejected with `400`
`payload.altMessagePremium`	`string`	No	—	Variant B’s premium variant of the out-of-network note, on `linkedinSend` steps only: any other step type is rejected with `400`. Over 300 characters is rejected with `400` too
`payload.cc`	`array`	No	—	—
`payload.plainText`	`boolean`	No	—	—

Output reference

Standard tool result payload.

Name	Type	Required	Default	Details
`result.data`	`object`	Yes	—	Provider response payload.
`result.data.stepId`	`string`	No	—	—
`result.data.abTest`	`boolean \| "A" \| "B"`	No	—	—
`result.data.emailTemplateBId`	`string`	No	—	Email template ID of variant B
`result.data.subject`	`string`	No	—	Variant B subject
`result.data.message`	`string`	No	—	Variant B body (HTML)
`result.data.altMessage`	`string`	No	—	Variant B’s LinkedIn note, same meaning as the step-level `altMessage`: the premium invitation note on a `linkedinInvite` step, the out-of-network note on a `linkedinSend` one
`result.data.altMessagePremium`	`string`	No	—	Variant B’s premium variant of the out-of-network note, on `linkedinSend` steps only
`result.data.cc`	`array`	No	—	—
`result.data.plainText`	`boolean`	No	—	—
`result.meta`	`object`	No	—	Additional response metadata (status, paging).

Deepline cost

Pricing model: fixed (per call).
Estimated Deepline credits: 0 per pricing unit.
Provider-native pricing may still exist outside Deepline credit billing.

​Run this action

​CLI

​Example response

​Input reference

​Output reference

​Deepline cost

​Related documentation

Run this action

CLI

Example response

Input reference

Output reference

Deepline cost

Related documentation