Operate Sequenzy email campaigns

Sequenzy Email Marketing guides operation of an existing Sequenzy workspace through an installed CLI or configured MCP connection. It supports audience inspection, campaign drafts and review links, authorized scheduling, campaign state changes, and delivery reporting. The workflow concerns service operations that can affect real subscribers, rather than email copy strategy alone.

Work starts by verifying the intended account, workspace, role, and available scopes. CLI authentication can be inspected with:

sequenzy whoami
sequenzy account
sequenzy campaigns --help

Cached local identity is not proof of current server access. MCP uses the connected server's exposed account tool and current schema. A capability such as canSendLive indicates some delivery workflow is available, not universal permission to perform every send action. Role-restricted scopes remain binding.

Use it to inspect audiences or delivery statistics; prepare, update, schedule, pause, or cancel campaigns; or establish whether an installed integration supports a requested operation. For strategy and copy planning without account operations, the related email-sequence skill is the appropriate route.

An instruction to draft does not authorize scheduling or sending. Before a schedule is applied, authorization must cover the final audience, sender, content, send time, and explicit time zone. Missing material details are resolved using the actual draft or review URL. Plan quotas and paid tiers constrain available actions, and the workflow cannot activate a paid plan or exceed authorized usage.

Identify the requested outcome and resolve campaign, audience, and sender names to unambiguous IDs. Read existing campaign status before mutation, select the narrowest supported operation from current help or tool schemas, and inspect audience exclusions. Preserve unsubscribe and suppression state. An imported address, purchase, or signup is not blanket promotional consent, and suppressions must not be removed to make a campaign run.

Draft preparation checks sender and reply profiles, personalization fallbacks, and the integration's preview. Creation is established through the returned object and a read-back rather than intended inputs. Return a real url, previewUrl, or appUrls value; MCP dashboard-link tools can supply an existing app URL. Conditional content may require Sequenzy block JSON rather than raw HTML.

Campaign transitions remain distinct. Cancel stops an active or scheduled operation, while unschedule returns it to draft. Pause, resume, deletion, and other transitions depend on the current state and permissions. Cancellation is not silently substituted as a prerequisite for another action. Destructive changes require explicit approval for the exact resource before a confirmation-bypass flag is used. The pinned implementation has no general campaign send-now CLI command, so scheduling cannot be replaced with an invented immediate-send operation.

After mutation, report the actual status, ID, review URL, and effective schedule. A schedule response does not prove recipient delivery. Delivery reports inspect statistics or events for an explicit date range and distinguish accepted, delivered, bounced, opened, and clicked counts. Open and click counts can contain automation or privacy-related noise. A test command alone is also insufficient evidence because the pinned backend can return stubbed test success.

Timeouts and ambiguous writes require inspecting current state before retrying. Blind retries of sends, schedules, enrollments, or creation can duplicate effects. If the outcome remains uncertain, report that uncertainty and stop the operation.

The skill requires an existing authorized Sequenzy CLI or MCP integration. The remote MCP endpoint uses the user's OAuth authorization or API key; the bundle installs no connector and includes no credentials. Missing access goes through the host's secure authentication flow.

Actual commands vary by installed version, role, and scope, and CLI and MCP capabilities may differ. Unsupported actions can use a documented dashboard path rather than an undisclosed substitute. Network operations transmit relevant subscriber data, campaign content, and parameters to Sequenzy; sends also deliver content to recipients. Return only task-needed personal data, keep credentials private, and respect existing account permissions.