Skip to main content
PUT
/
v1
/
campaigns
/
{id}
/
steps
/
{stepId}
Update Step
curl --request PUT \
  --url https://app-api.walead.ai/api/v1/campaigns/{id}/steps/{stepId} \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: <api-key>' \
  --data '
{
  "delay": 123,
  "genericBody": "<string>"
}
'
{
  "success": true,
  "message": "<string>"
}

Overview

Updates the configuration of a step in your campaign sequence. You can modify the delay between steps and set a generic message template.

Updatable Fields

delay

The number of days to wait before executing this step after the previous one completes. Example: If step 1 is an invitation and step 2 is a message with delay: 3, the message will be sent 3 days after the invitation is accepted.

genericBody

A generic message template that can be used as a fallback or default for the step. This is particularly useful for:
  • Setting a base message that variants can build upon
  • Providing a default when all variants are disabled
  • Documenting the intended message purpose

Request Body

You can update one or both fields:
{
  "delay": 5,
  "genericBody": "Hi {{firstName}}, thanks for connecting!"
}

Variable Support

The genericBody field supports WaLead template variables:
  • Core variables: {{firstName}}, {{lastName}}, {{companyName}}, etc.
  • Custom variables: Any custom fields you’ve defined for your leads

Use Cases

  • Adjust timing between steps based on campaign performance
  • Set fallback messages for steps with multiple variants
  • Quickly modify delays without recreating the entire sequence

Authorizations

x-api-key
string
header
required

API key for authentication. Generate from your WaLead dashboard.

Path Parameters

id
string
required

Campaign ID

stepId
string
required

Step ID

Body

application/json

Step update data

delay
integer

Delay in days before executing this step

genericBody
string

Generic message template for the step

Response

Step updated successfully

success
boolean
message
string