Update a step
Changes a step’s subject, body, preview text, delay or position. Content changes apply to every later send of the step. A new delay re-times everyone waiting for it from their last send, so a delay already passed sends on the next minute. Moving a step works like removing it and adding it at the new place: nobody gets a step twice.
Authorizations
API key in the format: Bearer {api_token}
Path Parameters
The sequence's prefixed id (e.g. seq_abc123).
The step's prefixed id (e.g. seqst_abc123).
Body
Takes the same variables as body.
Inbox preview line. Takes the same variables as body.
255Email body (HTML or plain text). Variables, filled per recipient: {{customer.first_name}}, {{customer.last_name}}, {{customer.email}}, {{business.name}}, {{product.name}}, {{product.url}}, {{order.product_names}}, {{tag.name}}, {{form.name}}, {{customer.fields.}}. product.* is the product whose purchase enrolled them (order.paid sequences only), tag.name the tag that enrolled them (tag_added), form.name the form a new lead came through (lead_created, empty for leads from elsewhere). customer.fields.<key> reads <key> from the customer's metadata when the email is sent; the key takes letters, digits and underscores. A blank value renders as nothing, or as the default in {{ customer.first_name | default: "there" }}. Any other {{ }} is rejected.
Wait after the previous step's send (after enrolling, for the first step).
1-based place in the sequence. On create, omit to append; the step at that place and those after it move down one.
x >= 1Response
The updated step
sequence_step Wait after the previous step's send (after enrolling, for the first step).

