curviate motion update

Change a Motion from a Motion file: objects (schedule, settings) merge by key, arrays and the Sequence replace whole, null clears. After start, a structural Sequence change makes a new version; running Enrollments keep theirs. With --if-revision the save is refused when someone saved the Sequence since.

Usage

curviate motion update <id> --file <file> [flags]

Examples

curviate motion update mot_YOUR_MOTION_ID --file motion.json --if-revision 3
curviate motion update mot_YOUR_MOTION_ID --file - <<'EOF'
{
  "name": "Q4 webinar follow-up",
  "contact_list_ids": ["cl_YOUR_LIST_ID"],
  "account_ids": ["acc_YOUR_ACCOUNT_ID"],
  "sequence": {
    "on_reply": "end",
    "steps": [
      { "id": "invite", "do": "invite.send", "with": { "note": null }, "next": "end" }
    ]
  }
}
EOF

Arguments

Argument	Required	Description
`id`	yes	Motion id (mot_...).

Flags

Flag	Type	Required	Description
`--file`	string	yes	The Motion file: a path, or - to read it from stdin. `curviate motion get` output is accepted as is.
`--if-revision`	string	no	The sequence_revision you read (`curviate motion get`). The save is refused with SEQUENCE_CONFLICT when the stored Sequence moved past it. Omitted: the last save wins.

Also accepts these global flags: --api-key, --profile, --account, --base-url, --timeout, --json, --fields, --preview, --verbose, --beta.

Exit codes: the exit code table. More commands: Motion.