Add a step
Adds an email to a sequence at position (1-based; omit to append). On an active sequence, people waiting for the step now at that place get the new step first; people already past it skip it, and people who finished never get an appended step.
Authorizations
API key in the format: Bearer {api_token}
Headers
Makes this write safe to retry: a repeat with the same key replays the first response instead of creating a second resource. Scoped to the account, remembered for 24 hours; reusing a key with a different payload is an error.
255Path Parameters
The sequence's prefixed id (e.g. seq_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 created step
sequence_step Wait after the previous step's send (after enrolling, for the first step).

