Automations
email_add_automation_steps
Append steps to the END of an automation or one of a branch's lanes (allowed while active — in-flight runs are unaffected and will flow into the new steps).
write email_add_automation_steps
Append steps to the END of an automation or one of a branch's lanes (allowed while active — in-flight runs are unaffected and will flow into the new steps). This is how 100-step evergreen sequences are authored incrementally. Pass parentStepId + laneKey (e.g. 'yes'/'no', a multi arm key, or 'else') to target a lane; omit both for the top level. To insert BETWEEN existing steps, pause first and use afterPosition (interpreted within the target lane).
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
automation | string | Yes | |
steps | any[] | Yes | |
afterPosition | integer | No | Insert after this position instead of appending (requires paused). |
parentStepId | string | No | A lane-owning branch step's id — target one of its lanes. |
laneKey | string | No | The lane within parentStepId: 'yes'/'no', an arm key, or 'else'. |
projectId | string | No | Target company (project id). Org-scoped tokens only; call email_list_projects first. |