Topolo Docs Topolo Platform
Open workspace

Disconnect Xero

Revoke the stored Xero tokens in Nexus. Imported records stay.

Outcome

Revoke the stored Xero tokens in Nexus. Imported records stay.

Before you start

  • Verify the intended environment, authenticated identity and specifically approved organization context.
  • The published application permission is migrations:write. Discover the exact granted canonical Books workspace and bind it separately from action input.
  • Approve the actual mutation, accounting inputs and any provider/recipient effects before CLI --confirm or MCP confirm:true. Fixture identifiers and simulated provider responses authorize no live operation.

Discover the target

topolo whoami --json
topolo actions get app_topolo_books.migrations.xero.disconnect --detail --json
topolo resources topolo-books --json
topolo workspaces list topolo-books --json
  • Set BOOKS_WORKSPACE_ID to the exact granted workspace returned by discovery.

Request

DELETE /api/migrations/xero

Inspect and test this action. Save the reviewed input as payload.json; supply credential/resource context separately.

Input fields

Use an empty input object. Credential and resource context are separate.

Inspect nested fields and the complete input schema.

Effects

  • Revokes the stored Xero tokens in Nexus. Everything already imported stays in Books.

Interpret the response

This result reports whether disconnection succeeded, not a connection id. Re-read migrations.xero.status for the same granted workspace.

Call app_topolo_books.migrations.xero.get and confirm connected is false.

Inspect the success schema. CLI/MCP add their own transport envelope; CLI --detail requests the full result.

Worked examples

Actual Books route handlers and the exported Worker were exercised against five local SQLite D1 concern databases with all committed migrations, the real posting Durable Object and local R2. Route captures use synthetic verified Auth; Worker captures use synthetic Auth transports. Nexus, Brand, Notify, Pay, Mercury and Xero responses are explicitly simulated at the provider transport boundary. Captures prove local request/response behavior and canonical SDK projection, not live bank access, payment movement, email delivery, provider eligibility, tax compliance, encrypted custody, scheduled execution, deployment or production completion. Fixture identities, credentials, addresses and records authorize no live operation.

Run a reviewed request

Save the input from the selected worked example as payload.json. Validate and inspect the plan before calling the action; refused examples demonstrate errors and are not instructions to execute.

CLI:

topolo actions validate app_topolo_books.migrations.xero.disconnect --data @payload.json --json
topolo actions plan app_topolo_books.migrations.xero.disconnect --resource-type workspace --resource-id "$BOOKS_WORKSPACE_ID" --data @payload.json --json
topolo actions call app_topolo_books.migrations.xero.disconnect --resource-type workspace --resource-id "$BOOKS_WORKSPACE_ID" --data @payload.json --confirm --detail --json

MCP tool and arguments for the first successful example:

{
  "tool": "topolo_call_action",
  "arguments": {
    "actionId": "app_topolo_books.migrations.xero.disconnect",
    "input": {},
    "resourceType": "workspace",
    "resourceId": "<exact granted workspace id>",
    "confirm": true,
    "detail": true
  }
}

Refused response · auth_error

Input · payload.json:

{}

Captured response · HTTP 401

{
  "error": "API key validation failed"
}

HTTP 401. SDK error code auth_error. Authenticate in the intended organization again. Verify whoami and the exact Books application/workspace binding before retrying; do not switch identity to work around a refusal.

Successful response · HTTP 200

Input · payload.json:

{}

Captured response · HTTP 200

{
  "ok": true
}

HTTP 200. Call app_topolo_books.migrations.xero.get and confirm connected is false.

Refused response · xero_not_connected

Input · payload.json:

{}

Captured response · HTTP 404

{
  "error": "xero_not_connected",
  "message": "Xero is not connected to this workspace"
}

HTTP 404. SDK error code xero_not_connected. Read migrations.xero.status and establish a separately authorized live Xero connection before retrying. A synthetic fixture is not a provider credential.

Verify the result

  • Call app_topolo_books.migrations.xero.get and confirm connected is false.

Errors and recovery

  • auth_error (HTTP 401): Authenticate in the intended organization again. Verify whoami and the exact Books application/workspace binding before retrying; do not switch identity to work around a refusal.
  • xero_not_connected (HTTP 404): Read migrations.xero.status and establish a separately authorized live Xero connection before retrying. A synthetic fixture is not a provider credential.

These are observed local refusals. Shared authentication, schema validation and resource authorization can also refuse before the route. Preserve the actual error, details and request id.

Recovery boundary

Connect Xero again; a person must re-authorise in a browser.

  • Connect Xero: Start the Xero OAuth connect: returns the Xero authorise URL to open. Tokens are stored in Nexus when Xero redirects back; Books never sees a password.

Evidence

Actual Books route handlers and the exported Worker were exercised against five local SQLite D1 concern databases with all committed migrations, the real posting Durable Object and local R2. Route captures use synthetic verified Auth; Worker captures use synthetic Auth transports. Nexus, Brand, Notify, Pay, Mercury and Xero responses are explicitly simulated at the provider transport boundary. Captures prove local request/response behavior and canonical SDK projection, not live bank access, payment movement, email delivery, provider eligibility, tax compliance, encrypted custody, scheduled execution, deployment or production completion. Fixture identities, credentials, addresses and records authorize no live operation.