update_campaign_workflow
Update message content on existing steps in a draft or paused campaign. Prefer one-based message_order, which counts only message-bearing steps and automatically skips invite/follow steps: message_order 1, 2, 3 targets the first, second, and third messages even when raw workflow step 1 is an invite. step_order remains available only when an exact raw workflow order is already known. Provide exactly one selector plus the exact message_template for every item. In message_template use only {FirstName}, {LastName}, and {Company} personalization variables. This is a two-phase confirmed action: first call without confirmation_token returns a confirmation card; approved execution applies the exact stored workflow_messages through the campaign service. It never launches or sends. Always include campaign_name and app_name for a human-readable preview. Over MCP: call this tool once, without confirmation_token. It runs right away and returns the result.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"campaign_id": "<campaign_id>",
"campaign_name": "<campaign_name>",
"app_name": "<app_name>",
"workflow_messages": "<workflow_messages>"
},
"name": "update_campaign_workflow"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| app_name | Yes | App name used in the confirmation preview | |
| campaign_id | Yes | Campaign id from a prior list_campaigns result (UUID format, e.g. 550e8400-e29b-41d4-a716-446655440000) | |
| campaign_name | Yes | Campaign name used in the confirmation preview | |
| workflow_messages | Yes | Exact message content to persist; prefer message_order 1..N for ordinary campaign copy | |
| confirmation_token | No | Phase-2 token (omit on phase-1) |