Outcome
Store an approved message for future delivery.
Before you start
- Verify the intended environment, credential and authorized organization context before discovery.
- Discover Mail, the exact action and its messages:send 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.scheduled.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.scheduled.create --data @payload.json --json
topolo actions plan app_topolo_mail.scheduled.create --resource-type workspace --resource-id <discovered-workspace-id> --data @payload.json --confirm --json
topolo actions call app_topolo_mail.scheduled.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
| Field | Required | Meaning |
|---|---|---|
mailboxId | Yes | Mailbox ID from mailboxes.collection.list in the selected workspace; it is distinct from the workspace resource ID. |
sendAt | Yes | Future scheduled-send deadline in Unix epoch milliseconds. A sweep owns actual dispatch; this does not promise dispatch at an exact instant. |
to | Yes | Non-empty array of approved recipient email addresses. Saving a draft does not authorize sending to them. |
cc | No | Optional non-empty array of approved copied recipient email addresses. |
bcc | No | Optional non-empty array of approved blind-copy recipient email addresses. |
subject | Yes | Reviewed message subject; non-empty for message/draft payloads, optional summary snapshot for snooze. |
bodyText | No | Fallback plain-text body when text is absent or empty; the handler uses non-empty text first. Prefer one reviewed plain-text representation. |
bodyHtml | No | Fallback HTML body when html is absent or empty; the handler uses non-empty html first. Review rendered content before sending and prefer one reviewed HTML representation. |
text | No | Preferred plain-text message body when non-empty; bodyText is the fallback. This field is not an audio upload. |
html | No | Preferred HTML message body when non-empty; bodyHtml is the fallback. This field is not a template identifier. |
attachments | No | Mailbox 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. |
trackOpens | No | Optional explicit open-tracking choice. A tracking-pixel fetch is not reliable proof a human read the message. |
Effects
- Creates a pending scheduled-send row and protected payload; later asynchronous processing can send the approved email without another user call.
Interpret the response
HTTP 201 returns data.id and data.sendAt in epoch milliseconds. The payload is retained in R2 and a pending row is created. A later sweep claims and sends it; this response does not establish eventual delivery or an exact dispatch time.
Worked requests and responses
Successful fixture request · HTTP 201
Input
{
"mailboxId": "mbx_mail_fixture",
"sendAt": 1791417660000,
"to": [
"recipient@example.test"
],
"subject": "Synthetic fixture",
"bodyText": "Synthetic content for review."
}
SDK response or error
{
"success": true,
"data": {
"success": true,
"id": "sch_00000000-0000-4000-8000-000000000002",
"sendAt": 1791417660000
}
}
Refused requests
Unauthenticated caller · HTTP 401
Input
{
"mailboxId": "mbx_mail_fixture",
"sendAt": 1791417660000,
"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",
"sendAt": 1791417660000,
"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",
"sendAt": 1791417660000,
"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",
"sendAt": 1791417660000,
"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"
}
}
Refused semantic request · HTTP 400
Input
{
"mailboxId": "mbx_mail_fixture",
"sendAt": 1791417599999,
"to": [
"recipient@example.test"
],
"subject": "Synthetic fixture",
"bodyText": "Synthetic content for review."
}
SDK response or error
{
"code": "http_error",
"status": 400,
"message": "A future send time is required"
}
Service HTTP body
{
"success": false,
"error": {
"message": "A future send time is required"
}
}
Verify the result
- Read scheduled.list, match data.id, recipients, subject and sendAt. After dispatch inspect the sent folder and transport result separately.
Recover
Cancel through scheduled.delete while the item is still pending, before it is claimed by delivery. Once sent it cannot be recalled; reconcile state before retrying creation.
- 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. - HTTP 400
http_error: Inspect this captured refusal: A future send time is required. Correct only the reviewed request or prerequisite, revalidate it, and plan again. Do not repeat an uncertain send, paid generation or deletion.
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.
Related actions
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.