CLI command
tinbox create-campaign
Create a COMPLETE email campaign (newsletter) draft in one call: audience (and optional segment), subject, body, sender identity (from/reply-to), a PROPOSED send time, and a short rationale for your choices. The draft lands in the campaign builder for human review — it never sends or schedules itself. Use list_audiences / list_segments first to resolve ids by name, and get_send_readiness('broadcast') before creating.
Generated from tool: create_campaignUsage
sh
tinbox create-campaign --audienceId <audienceId> --segmentId <segmentId> --title <title> --subject <subject> --content <content> --fromName <fromName> --fromEmail <fromEmail> --replyTo <replyTo> --previewText <previewText> --proposedSendAt <proposedSendAt> --rationale <rationale>Flags
| Name | Type | Required | Default | Description |
|---|---|---|---|---|
--audienceId | string | yes | — | The audience to send to (resolve by name via list_audiences). |
--segmentId | string | yes | — | Optional saved/static segment within the audience (resolve by name via list_segments). |
--title | string | yes | — | Internal title for the campaign. |
--subject | string | yes | — | Email subject line. |
--content | string | yes | — | Email body content (markdown or HTML). |
--fromName | string | yes | — | Sender name (defaults to audience setting). |
--fromEmail | string | yes | — | Sender email (defaults to audience setting). |
--replyTo | string | yes | — | Reply-to address (defaults to audience setting). |
--previewText | string | yes | — | Inbox preview text (the line under the subject). |
--proposedSendAt | string | yes | — | PROPOSED send time (Unix ms). Stored on the draft only — a human must approve and schedule before anything sends. |
--rationale | string | yes | — | One short paragraph on the choices made (which audience/segment and why, the proposed schedule and why). Shown to the reviewer in the builder's proposed-by banner. |