curviate campaign update

Change a Campaign from a Campaign file: objects (schedule, settings) merge by key, arrays and the Sequence replace whole, null clears. settings.priority (normal or prioritized) weighs the Campaign 1 or 1.5 in each Account's budgets, on every budget (every Campaign with work due still progresses, and no limit is passed); settings.new_enrollments_per_account_per_day and settings.assign even are retired (accepted and ignored until 2027-01-28, with a notice). 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. Needs Automate.

Usage

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

Examples

curviate campaign update mot_YOUR_CAMPAIGN_ID --file campaign.json --if-revision 3
curviate campaign update mot_YOUR_CAMPAIGN_ID --file - <<'EOF'
{
  "name": "Q4 webinar follow-up",
  "lead_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

ArgumentRequiredDescription
idyesCampaign id (mot_...).

Flags

FlagTypeRequiredDescription
--filestringyesThe Campaign file: a path, or - to read it from stdin. curviate campaign get output is accepted as is.
--if-revisionstringnoThe sequence_revision you read (curviate campaign 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, --team, --base-url, --timeout, --json, --fields, --preview, --verbose, --beta.

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