Pause or resume a campaign
campaign_set_statusPause a running campaign, or resume one that is paused. PAUSED halts sending immediately; pending steps stay queued and pick up where they left off when it resumes. ACTIVE starts real outreach again, so ASK THE USER before resuming — the campaign may have been paused for a reason they know and you do not. Nothing is destroyed either way, so your client will not prompt for you: the confirmation has to be one you asked for. Pausing needs no ceremony — it only stops sending, and is undone by resuming. Deliberately narrower than the status field it writes. It will not ARCHIVE or COMPLETE a campaign — those are web-app housekeeping — and it will not DELETE one, which is campaign_delete. It also refuses to resume anything that is not already PAUSED: updateCampaign writes the field blindly, so setting ACTIVE on a DRAFTED campaign would mark it live without a lead source, a saved flow, a sending account or materialised sequences, none of which this path checks. A campaign that has never run is started with campaign_launch, which validates all of that first.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| status | Yes | PAUSED halts sending. ACTIVE resumes a paused campaign, and is refused for any other current status. | |
| campaignId | Yes | Campaign id, from `campaign_list` or `campaign_create`. |