Update Mail mailbox settings

Outcome

Change reviewed mailbox profile, display and assistant settings.

Before you start

• Verify the intended environment, credential and authorized organization context before discovery.
• Discover Mail, the exact action and its mailboxes:manage 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.mailboxes.update --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.mailboxes.update --data @payload.json --json
topolo actions plan app_topolo_mail.mailboxes.update --resource-type workspace --resource-id <discovered-workspace-id> --data @payload.json --confirm --json
topolo actions call app_topolo_mail.mailboxes.update --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

• Persists the specified mailbox profile fields and queues agent-prompt propagation when supplied. No email is sent.

Interpret the response

data is the updated mailbox profile. Reply-To must remain in the mailbox domain. displayName/status retain current values when the handler receives empty values; the action schema only accepts non-empty optional strings. agentPrompt is persisted and propagated to the mailbox through waitUntil; a successful response does not independently prove asynchronous propagation.

Worked requests and responses

Successful fixture request · HTTP 200

Input

{
  "mailboxId": "mbx_mail_fixture",
  "displayName": "Reviewed fixture",
  "agentPrompt": "Synthetic operator instructions"
}

SDK response or error

{
  "success": true,
  "data": {
    "id": "mbx_mail_fixture",
    "organizationId": "org_mail_fixture",
    "workspaceId": "ws_mail_fixture",
    "userId": "usr_mail_fixture",
    "organizationSlug": null,
    "address": "fixture@example.test",
    "displayName": "Reviewed fixture",
    "fromName": "Fixture sender",
    "replyToAddress": "fixture@example.test",
    "status": "active",
    "agentPrompt": "Synthetic operator instructions",
    "outboundProfileId": null,
    "connectionType": "topolo_hosted",
    "connectionStatus": "active",
    "connectionStatusReason": null,
    "providerIdentity": null,
    "lastSyncAt": null,
    "createdAt": "2026-10-08T00:00:00.000Z",
    "updatedAt": "2026-10-08T00:00:00.000Z"
  }
}

Refused requests

Unauthenticated caller · HTTP 401

Input

{
  "mailboxId": "mbx_mail_fixture",
  "displayName": "Reviewed fixture",
  "agentPrompt": "Synthetic operator instructions"
}

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",
  "displayName": "Reviewed fixture",
  "agentPrompt": "Synthetic operator instructions"
}

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",
  "displayName": "Reviewed fixture",
  "agentPrompt": "Synthetic operator instructions"
}

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",
  "displayName": "Reviewed fixture",
  "agentPrompt": "Synthetic operator instructions"
}

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 403

Input

{
  "mailboxId": "mbx_mail_fixture",
  "replyToAddress": "outside@other.test"
}

SDK response or error

{
  "code": "permission_denied",
  "status": 403,
  "message": "reply_to_address must share the mailbox domain (example.test); got other.test"
}

Service HTTP body

{
  "success": false,
  "error": {
    "message": "reply_to_address must share the mailbox domain (example.test); got other.test"
  }
}

Verify the result

• Read mailboxes.get and compare each supplied field with the reviewed change. Verify any asynchronous assistant behavior separately.

Recover

Read and retain the previous reviewed settings before changing them. To restore supported fields, plan a new mailboxes.update with those values; history and asynchronous propagation are not automatic rollback.

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

Related actions

• Get Mail mailbox

• Get Mail connection

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.