Topolo Docs Topolo Platform
Open workspace

Create Mail draft

Save reviewed or proposed message content as an unsent draft.

Outcome

Save reviewed or proposed message content as an unsent draft.

Before you start

  • Verify the intended environment, credential and authorized organization context before discovery.
  • Discover Mail, the exact action and its messages:write permission. Pass the accessible workspace resource binding separately from action input.
  • Review the actual change, recipients, provider/AI costs and any irreversible effects before confirmation; fixture IDs authorize no live operation.

Discover the target

  • Run credential-scoped Mail discovery and topolo workspaces list topolo-mail; select an authorized canonical workspace.
  • Resolve mailbox IDs through mailboxes.collection.list in that workspace. Resolve message, draft, thread, folder and scheduled IDs through the related published reads; never reuse fixture IDs or another context.
topolo whoami --json
topolo apps get topolo-mail --json
topolo actions get app_topolo_mail.drafts.create --json
topolo workspaces list topolo-mail --json

Request

Create payload.json using the current input schema and discovered identifiers. Plan the unchanged request before execution.

topolo actions validate app_topolo_mail.drafts.create --data @payload.json --json
topolo actions plan app_topolo_mail.drafts.create --resource-type workspace --resource-id <discovered-workspace-id> --data @payload.json --confirm --json
topolo actions call app_topolo_mail.drafts.create --resource-type workspace --resource-id <discovered-workspace-id> --data @payload.json --confirm --json

For MCP, use topolo_get_action, topolo_validate_action and topolo_plan_action; execute with topolo_call_action with confirm:true only after approval. Pass resourceType workspace and the discovered resourceId separately from input. An absent service/action or non-executable plan blocks that operation.

Input fields

FieldRequiredMeaning
mailboxIdYesMailbox ID from mailboxes.collection.list in the selected workspace; it is distinct from the workspace resource ID.
originalMessageIdNoDiscovered original message ID for reply drafting or assistant thread lookup.
toYesNon-empty array of approved recipient email addresses. Saving a draft does not authorize sending to them.
ccNoOptional non-empty array of approved copied recipient email addresses.
bccNoOptional non-empty array of approved blind-copy recipient email addresses.
subjectYesReviewed message subject; non-empty for message/draft payloads, optional summary snapshot for snooze.
bodyTextNoUse this field for the plain-text draft body; this candidate handler forwards it to the draft writer.
bodyHtmlNoUse this field for the HTML draft body; this candidate handler forwards it to the draft writer.
textNoDeclared by the input schema but ignored by this candidate draft handler; it does not populate draft text. Use bodyText.
htmlNoDeclared by the input schema but ignored by this candidate draft handler; it does not populate draft HTML. Use bodyHtml.
attachmentsNoMailbox attachment objects passed to the mailbox tool. The action publishes no attachment-field schema or generic file upload descriptor; inspect the current contract before supplying files.

Effects

  • Saves a draft through the mailbox tool without sending email.

Interpret the response

HTTP 201 returns the mailbox tool draft result. originalMessageId chooses reply drafting; otherwise a new draft is created. A draft is distinct from a scheduled or sent message.

Worked requests and responses

Successful fixture request · HTTP 201

Input

{
  "mailboxId": "mbx_mail_fixture",
  "to": [
    "recipient@example.test"
  ],
  "subject": "Synthetic fixture",
  "bodyText": "Synthetic content for review."
}

SDK response or error

{
  "success": true,
  "data": {
    "id": "draft_created_fixture",
    "threadId": "thr_mail_fixture",
    "folderId": "drafts",
    "direction": "draft",
    "subject": "Synthetic fixture",
    "sender": "sender@example.test",
    "recipients": [
      "recipient@example.test"
    ],
    "date": "2026-10-08T00:00:00.000Z",
    "bodyText": "Synthetic content for review.",
    "read": false,
    "starred": false,
    "attachments": [],
    "bodyHtml": null
  }
}

Supported variant · HTTP 201

Input

{
  "mailboxId": "mbx_mail_fixture",
  "originalMessageId": "msg_mail_fixture",
  "to": [
    "recipient@example.test"
  ],
  "subject": "Synthetic fixture",
  "bodyText": "Synthetic content for review."
}

SDK response or error

{
  "success": true,
  "data": {
    "id": "draft_created_fixture",
    "threadId": "thr_mail_fixture",
    "folderId": "drafts",
    "direction": "draft",
    "subject": "Synthetic fixture",
    "sender": "sender@example.test",
    "recipients": [
      "recipient@example.test"
    ],
    "date": "2026-10-08T00:00:00.000Z",
    "bodyText": "Synthetic content for review.",
    "read": false,
    "starred": false,
    "attachments": [],
    "bodyHtml": null
  }
}

Refused requests

Unauthenticated caller · HTTP 401

Input

{
  "mailboxId": "mbx_mail_fixture",
  "to": [
    "recipient@example.test"
  ],
  "subject": "Synthetic fixture",
  "bodyText": "Synthetic content for review."
}

SDK response or error

{
  "code": "auth_error",
  "status": 401,
  "message": "Fixture authentication refused"
}

Service HTTP body

{
  "success": false,
  "error": {
    "message": "Fixture authentication refused"
  }
}

Permission denied · HTTP 403

Input

{
  "mailboxId": "mbx_mail_fixture",
  "to": [
    "recipient@example.test"
  ],
  "subject": "Synthetic fixture",
  "bodyText": "Synthetic content for review."
}

SDK response or error

{
  "code": "permission_denied",
  "status": 403,
  "message": "TopoloMail permission denied"
}

Service HTTP body

{
  "success": false,
  "error": {
    "message": "TopoloMail permission denied"
  }
}

Other organization · HTTP 403

Input

{
  "mailboxId": "mbx_mail_fixture",
  "to": [
    "recipient@example.test"
  ],
  "subject": "Synthetic fixture",
  "bodyText": "Synthetic content for review."
}

SDK response or error

{
  "code": "permission_denied",
  "status": 403,
  "message": "Mailbox does not belong to your organization"
}

Service HTTP body

{
  "success": false,
  "error": {
    "message": "Mailbox does not belong to your organization"
  }
}

Other verified workspace · HTTP 404

Input

{
  "mailboxId": "mbx_mail_fixture",
  "to": [
    "recipient@example.test"
  ],
  "subject": "Synthetic fixture",
  "bodyText": "Synthetic content for review."
}

SDK response or error

{
  "code": "http_error",
  "status": 404,
  "message": "Mailbox not found"
}

Service HTTP body

{
  "success": false,
  "error": {
    "message": "Mailbox not found"
  }
}

Verify the result

  • Read messages.get on the returned ID and verify draft folder, recipients and content before any send.

Recover

An unsent draft can be separately changed or deleted with its discovered ID. Inspect drafts before repeating creation after a timeout; creation is not declared idempotent.

  • HTTP 401 auth_error: Authenticate again in the intended environment and context, then repeat identity and action discovery.
  • HTTP 403 permission_denied: Stop for the exact permission, organization, sender or Reply-To refusal. Do not broaden access or switch credentials automatically.
  • HTTP 404 http_error: Rediscover the exact mailbox and child IDs in the same authorized workspace; do not guess another ID.

The captured SDK errors preserve the service code when structured, otherwise http_error and HTTP status. Do not invent a more specific code. Preserve the live request ID and inspect actual diagnostics for uncaptured failures.

Evidence and limits

  • Actual exported Mail handler dispatcher, widget handler, domain handlers, SDK transport/projection and shipped SQLite control/delivery/tracking migrations.

  • Identity, permissions, verified workspace grants, provider connection state, OAuth URL generation, mailbox Durable Object operations and content protection are synthetic ports.

  • Nexus AI and Auth archive are allowlisted in-process responses. No paid generation, billing, live OAuth, encryption custody, email delivery, asynchronous delivery or deployed outcome is proved. External network egress is refused.

The captured requests use synthetic identities and .test recipients. They demonstrate handler and SDK response behavior; they do not authorize delivery, provider consent, paid generation, deletion or other live effects. Current catalog discovery and environment proof remain separate release requirements.