Origami

View saved version →

---
name: origami-draft
description: Create an outreach campaign draft in Origami from a user's brief, then hand off to Origami for review and launch. Use when the user asks Origami to draft an email or LinkedIn outreach campaign. Requires a connected Origami account with API access.
---

# Draft outreach in Origami

Create one saved campaign draft using the existing Origami MCP server, then show a concise preview and link to the main app. This workflow's only campaign write is `send_campaigns_draft`. Do not launch, enroll recipients, connect senders, buy leads, or edit existing campaigns through this workflow. Direct those next steps to Origami.

## Connection

Use the configured Origami MCP connection at `https://origami.chat/mcp`. Tool names below are unqualified; use the host's actual Origami tool namespace and discovered argument schemas. Results contain JSON in a text content block. Check `isError` and the returned error code: HTTP 200 alone does not mean the tool succeeded. Never guess an alternate tool or endpoint if a named tool is unavailable.

If disconnected, use the host's secure OAuth connection flow. Sign in as an administrator of an Origami primary organization with API access and select that organization during consent. Never ask for tokens, passwords, or API keys in chat. If connection fails, report that it has not succeeded.

Use `account_get` only if needed to verify the connected organization. Work within that organization and omit `project`. Child/project switching is unavailable in this OAuth workflow; direct project-specific work to Origami. Keep each returned job ID for follow-ups. Jobs from another connection cannot be resumed here.

## Create the draft

1. Use the conversation to identify the offer, intended audience, and campaign goal. Ask one short question only when essential context is missing. Do not make the user complete a form or require recipients or senders.
2. Call `send_campaigns_draft` once with `brief`. If the user supplies a campaign name, put that exact name alone on the first line of `brief`, because the existing drafting operation derives the saved name from that line. Keep the complete brief within 10,000 characters, preserve the user's factual claims, and specify that the task is to draft a sequence without sourcing or enrolling prospects or launching. If the original brief is too long, condense it without inventing facts or ask which details to prioritize. Pass `channels` only when specified by the user: `email`, `linkedin`, or both. Omit `list_id` for this MVP, so it does not require an existing prospect list. Do not add unsupported parameters. The current MCP tool has no idempotency parameter; do not copy REST idempotency headers into tool arguments.
3. Record the returned job ID. A queued or running job is not a completed campaign. Call `jobs_get` with that ID, respecting `next_poll_at` and any retry delay. Keep the user informed during a long wait. Resume the same job on a follow-up instead of creating another draft.
4. If the job has `needs_input.questions`, show its actual questions. Use answers already explicitly provided or ask the user. Submit those answers through `jobs_input` using its discovered schema and continue reading the same job. If it instead supplies a human `handoff`, show the returned HTTPS link and reason; do not submit fabricated answers, perform that action, or claim the job resumed. Do not invent approval, audience facts, or product claims.
5. On `succeeded`, obtain the campaign ID from the returned campaign target or explicit result. Call `send_campaigns_get` to read the saved draft. Never invent an ID or treat a job ID as a campaign ID. If the result lacks a usable campaign ID, report that limitation and link to the app.

## Return the useful result

A successful job may include `blocked.missing_channels` when the account lacks connected senders. This is a launch-readiness notice, not a failed draft or a contradiction of the campaign channels. Explain

Preview of the first 4,000 characters. Read full instructions →