Archive empty Mail workspace

Outcome

Archive a selected canonical Mail workspace after confirming it contains no mailboxes.

Before you start

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

• Calls the Auth archive service, then removes the app workspace mirror. Mailboxes are not deleted by this action.

Interpret the response

data.archived and data.workspaceId identify the platform archive result. A non-empty workspace is refused with HTTP 409. Workspace creation, renaming and default selection belong to Auth.

Worked requests and responses

Successful fixture request · HTTP 200

Input

{
  "workspaceId": "ws_mail_fixture"
}

SDK response or error

{
  "success": true,
  "data": {
    "archived": true,
    "workspaceId": "ws_mail_fixture"
  }
}

Refused requests

Unauthenticated caller · HTTP 401

Input

{
  "workspaceId": "ws_mail_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

{
  "workspaceId": "ws_mail_fixture"
}

SDK response or error

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

Service HTTP body

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

Refused semantic request · HTTP 409

Input

{
  "workspaceId": "ws_mail_fixture"
}

SDK response or error

{
  "code": "http_error",
  "status": 409,
  "message": "A non-empty workspace cannot be archived"
}

Service HTTP body

{
  "success": false,
  "error": {
    "message": "A non-empty workspace cannot be archived"
  }
}

Verify the result

• List Mail workspaces through the published Auth workspace catalog and confirm the selected identity is archived or absent. Preserve an uncertain Auth result before retrying.

Recover

The old workspace identity is archived; no restore action is declared. Do not delete mailboxes merely to bypass the empty-workspace check. Export and separately approve any required deletion first.

• 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 409 http_error: Inspect this captured refusal: A non-empty workspace cannot be archived. 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 Mail mailboxes

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.