Snooze Mail message

Outcome

Hide a selected inbox message until an approved future time.

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.messages.snooze.set --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.messages.snooze.set --data @payload.json --json
topolo actions plan app_topolo_mail.messages.snooze.set --resource-type workspace --resource-id <discovered-workspace-id> --data @payload.json --confirm --json
topolo actions call app_topolo_mail.messages.snooze.set --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

Effects

• Upserts a local snooze overlay; underlying message and folder remain unchanged. Inbox reads remove expired overlays so messages reappear.

Interpret the response

data.success:true and snoozeUntil report an epoch-millisecond overlay. until must be later than the server clock. Optional subject/sender/thread/date are summary snapshots, not changes to underlying message content.

Worked requests and responses

Successful fixture request · HTTP 200

Input

{
  "mailboxId": "mbx_mail_fixture",
  "messageId": "msg_mail_fixture",
  "until": 1791417660000,
  "subject": "Synthetic fixture"
}

SDK response or error

{
  "success": true,
  "data": {
    "success": true,
    "snoozeUntil": 1791417660000
  }
}

Refused requests

Unauthenticated caller · HTTP 401

Input

{
  "mailboxId": "mbx_mail_fixture",
  "messageId": "msg_mail_fixture",
  "until": 1791417660000,
  "subject": "Synthetic fixture"
}

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",
  "messageId": "msg_mail_fixture",
  "until": 1791417660000,
  "subject": "Synthetic fixture"
}

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",
  "messageId": "msg_mail_fixture",
  "until": 1791417660000,
  "subject": "Synthetic fixture"
}

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",
  "messageId": "msg_mail_fixture",
  "until": 1791417660000,
  "subject": "Synthetic fixture"
}

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",
  "messageId": "msg_mail_fixture",
  "until": 1791417599999
}

SDK response or error

{
  "code": "http_error",
  "status": 400,
  "message": "A future snooze time is required"
}

Service HTTP body

{
  "success": false,
  "error": {
    "message": "A future snooze time is required"
  }
}

Verify the result

• Read snoozed.list, match the message ID and snoozeUntil. Confirm the inbox hides the active snooze without interpreting it as deletion.

Recover

Plan messages.snooze.delete for the same mailbox/message to remove the overlay; this does not move or mark the underlying message.

• 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 snooze 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

• List snoozed Mail messages

• List Mail messages

• Unsnooze Mail message

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.