Create campaign

Create a draft campaign from a simplified high-level sequence.

Create a draft campaign from the public steps format.

How to structure the request:

• Start steps with the first action that should happen.
• Keep adding the next action in the order it should run.
• Use condition when you want to branch on lead data.
• Use linkedin_connection when you want to branch on connection acceptance after sending a connection request.
• Put shared follow-up work after the branching step instead of duplicating the same steps inside both branches.

Before you send a request:

• Send an ordered steps array that describes the campaign flow from first action to last action.
• Use branch arrays on condition and linkedin_connection steps to describe branch-specific work.
• Place shared follow-up steps after a branching step when both live branches should continue together.
• waitForAcceptance.unit must be days and waitForAcceptance.value must be an integer greater than or equal to 1.
• Use GET /v1/tasks/owners first when your campaign includes task steps. If owners are returned, every task step must include ownerId.
• Validation errors use full paths like steps[0].onTrue[1].subject so nested input issues are easy to fix.

Supported condition.type values:

• has_linkedin_profile: onTrue runs when the lead has a LinkedIn profile.
• has_professional_email: onTrue runs when the lead has a professional email.
• is_already_connected: onTrue runs when the lead is already a LinkedIn connection.
• has_been_contacted: onTrue runs when the lead has already been contacted.

Branch fields:

• condition uses onTrue and onFalse.
• linkedin_connection uses onAccepted and onNotAccepted.
• Use [{ "type": "end" }] when a branch should stop explicitly.

For examples and a full step-by-step guide, see /api-reference/campaigns-guide in the docs site..

Required scope: CAMPAIGNS_WRITE

Rate limit: 30 requests per minute