Add a step to a campaign
add_campaign_stepUse this when the user wants another step in a campaign's sequence: a message on one channel, a LinkedIn profile visit or like, or a condition or A/B split that branches the sequence. Place it with sequenceNumber, in the main sequence or in a condition's lane. A manual step sends its subject and body as written, with {Variable} tokens filled in for each person; an AI step writes each message itself. On a running campaign, the step's messages go out to each person who reaches it. Once leads have moved through a branched sequence its shape cannot change. Writing an AI step can take a minute. Free. Calling again adds a second step.
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": {
"campaignId": "<campaignId>",
"channel": "<channel>",
"sequenceNumber": "<sequenceNumber>",
"daysBetween": "<daysBetween>"
},
"name": "add_campaign_step"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| cc | No | Up to 10 addresses copied on every email of the step. | |
| body | No | A `manual` step's message, up to 20,000 characters; the campaign's variable tokens, such as `{Contact First Name}`, are filled in for each lead. On a `linkedin_connection` step, the invitation note, up to 200 characters. Not on visits, likes and conditions. | |
| type | No | `manual` (the default) sends `subject` and `body` as written; `ai_generated` writes each message for each lead from a topic it writes itself; `ai_reply` drafts a reply from `topic` that waits for your approval. A condition is always `manual`. | |
| topic | No | What the step should say, up to 500 characters. Needed by `ai_reply`; `ai_generated` writes its own. | |
| channel | Yes | `email`, `linkedin_connection` (an invitation), `linkedin_message` (to a connection), `linkedin_visit` (a profile visit), `linkedin_like` (a like on a recent post), `inmail`, or `condition`: a branch that waits for `conditionType` and sends each lead down its `yes` or `no` lane, or for an `ab_split`, down variant `a` or `b` at once. A `linkedin_connection` step cannot follow a `linkedin_message` step. | |
| subject | No | A `manual` step's subject line, up to 500 characters. Not on visits, likes and conditions. | |
| branchKey | No | The lane of `parentStepId`: `yes` or `no` under a condition, `a` or `b` under an A/B split. | |
| splitArms | No | `ab_split` only: both variants, `a` then `b`, each `{ key, label?, weight }`. 50 each when left out. | |
| campaignId | Yes | The campaign's id. | |
| daysBetween | Yes | Days to wait after the step before (or after the start, for the first step), 0 to 90. On a condition, how long it waits for its signal, 1 to 30 days; an `ab_split` waits for nothing: send 0. | |
| parentStepId | No | The condition whose lane the step goes in, with `branchKey`. Left out, the step goes in the main sequence. | |
| conditionType | No | Conditions only: `invite_accepted` waits for the invitation of the nearest `linkedin_connection` step before it, `clicked_link` for a click in the nearest email before it, and `ab_split` splits leads between variants `a` and `b` by `splitArms`. Conditions can be added only before the campaign starts. | |
| sequenceNumber | Yes | The step's place, from 0, in the main sequence or in the lane `parentStepId` and `branchKey` name. Send the length of the sequence or lane to add at its end; a taken place answers `409` `step_position_taken`. |