Start a paused campaign (two steps)
launch_campaignActivate a paused campaign, in two calls. Without confirm_token it only runs a preflight and changes nothing: the account's limits, the note and follow-ups, the plan's campaign limit, the activation checks, approval, whether the desktop app and a LinkedIn account are linked, and whether the campaign has anyone in it. When every check passes it returns a plain-language summary, every person waiting with the exact connection note they will get and its approval state, and a single-use confirm_token (valid 10 minutes, tied to this account, this campaign and its exact state, including each person's note). For a campaign whose notes ZenMode's AI writes with review off, it also returns unreviewed_ai_warning, a line the person must see on its own before saying yes. With that confirm_token it re-checks everything and activates the campaign. A token that is missing, expired, used, for another campaign, or from before the campaign changed is refused. Activating contacts nobody at that moment: ZenMode's engine works through the campaign's people later, inside the account's daily and weekly limits and business hours, only while the ZenMode desktop app is open. Nothing happens on LinkedIn at the moment you call this. ZenMode's campaign engine works through each campaign later, inside your daily and weekly limits, business hours and pacing.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| campaign_id | Yes | The campaign id, from create_campaign or list_campaigns. | |
| confirm_token | No | The confirm_token from the preflight. Leave out to run the preflight. | |
| idempotency_key | No | Optional. A unique string you make up for this exact change (8 to 128 letters, digits, - _ . :). If the call is repeated with the same key and the same arguments within 24 hours, nothing happens twice and the first result is returned again. Use a fresh key for every new change. |