Skip to main content

​
Define a LinkedIn draft

draft.json
The supported LinkedIn sequence has up to four steps. A connection request can appear only first, with a note at most 300 characters. Provider account restrictions can be lower. Email drafts accept name only; then use campaign setup to select their templates and senders.

​
Preview, create, verify

The first command performs local schema validation and produces a redacted preview. It makes no HTTP call and cannot verify current permissions, state or provider eligibility. The second creates the inactive draft. Replace 456 with the returned ID, confirm draft, and open its review_path on the configured app host.

​
Input rules

--file - reads a JSON object from stdin. The size limit is 256 KiB. Arrays as the root body, duplicate fields, unknown fields and nonfinite numbers are rejected. Never use a new idempotency key to escape an uncertain result; read back first. Draft preparation commands do not launch a campaign or send outreach. Review content, audience, sender settings and recommended account volumes in the app before any separate launch action. The CLI has a reviewed activation flow for eligible manual LinkedIn campaigns; see review and launch.