Update sending seat

Outcome

Change a seat's display name, from address, time zone or warm-up plan. Provide at least one field (422 invalid_input).

Before you start

• Verify the intended environment, signed-in credential, authorized organization and the action permission workspace:write.
• Discover and select an authorized canonical Engage workspace. Pass resourceType=workspace and resourceId separately from action input.
• Review the exact effects and obtain approval before CLI --confirm or MCP confirm:true. A local capture does not authorize a live mutation.

Discover the target

topolo whoami --json
topolo actions get app_topolo_engage.seats.update --json
topolo workspaces list topolo-engage --json

Set ENGAGE_WORKSPACE_ID to the identifier of the selected authorized workspace.

Input contract

Validate, plan and execute

Build payload.json from the current schema and discovered identifiers. The action description above defines its behavior, limits, side effects and declared errors.

: "${ENGAGE_WORKSPACE_ID:?Set ENGAGE_WORKSPACE_ID to your selected workspace identifier}"
topolo actions validate app_topolo_engage.seats.update --data @payload.json --json
topolo actions plan app_topolo_engage.seats.update --resource-type workspace --resource-id "$ENGAGE_WORKSPACE_ID" --data @payload.json --confirm --json

Review the plan and approve its exact effects before executing the unchanged request.

: "${ENGAGE_WORKSPACE_ID:?Set ENGAGE_WORKSPACE_ID to your selected workspace identifier}"
topolo actions call app_topolo_engage.seats.update --resource-type workspace --resource-id "$ENGAGE_WORKSPACE_ID" --data @payload.json --confirm --json

For MCP, use topolo_get_action, topolo_validate_action, topolo_plan_action and topolo_call_action. Pass resource context separately where required; confirm:true is required for mutations.

Captured successful requests and responses

Captured HTTP 200 · seat WhatsApp number > keeps the number through other seat edits

Action input

{
  "id": "eng_seat_1",
  "displayName": "Ashley"
}

Actual local response

{
  "seat": {
    "id": "eng_seat_1",
    "nexusMailboxId": "mbsender_1",
    "mailboxStatus": "active",
    "mailboxCheckedAt": "2026-10-06T08:30:00.000Z",
    "whatsappConnectionId": "wac_ash",
    "displayName": "Ashley",
    "fromAddress": "ash@example.com",
    "status": "active",
    "pauseReason": null,
    "timezone": "Europe/London",
    "warmup": {
      "startDate": "2026-10-01",
      "startLimit": 10,
      "dailyIncrease": 3,
      "maxLimit": 50
    },
    "createdAt": "2026-10-06T08:30:00.000Z",
    "updatedAt": "2026-10-06T08:30:00.000Z",
    "health": {
      "windowDays": 14,
      "sent": 0,
      "bounced": 0,
      "optedOut": 0,
      "bounceRate": 0,
      "optOutRate": 0,
      "healthy": true,
      "sentToday": 0,
      "warmupCap": 25
    }
  }
}

Source test: seat WhatsApp number > keeps the number through other seat edits. Actual route handlers with SQLite repositories; synthetic identity/workspace grants and provider ports.

Captured HTTP 200 · seat routes > edits, pauses and resumes a seat

Action input

{
  "id": "eng_seat_1",
  "displayName": "Ashley",
  "fromAddress": "ASHLEY@example.com",
  "timezone": "America/New_York",
  "warmupStartDate": "2026-10-02",
  "warmupStartLimit": 5,
  "warmupDailyIncrease": 2,
  "warmupMaxLimit": 25
}

Actual local response

{
  "seat": {
    "id": "eng_seat_1",
    "nexusMailboxId": "mbsender_1",
    "mailboxStatus": "active",
    "mailboxCheckedAt": "2026-10-06T08:30:00.000Z",
    "whatsappConnectionId": null,
    "displayName": "Ashley",
    "fromAddress": "ashley@example.com",
    "status": "active",
    "pauseReason": null,
    "timezone": "America/New_York",
    "warmup": {
      "startDate": "2026-10-02",
      "startLimit": 5,
      "dailyIncrease": 2,
      "maxLimit": 25
    },
    "createdAt": "2026-10-06T08:30:00.000Z",
    "updatedAt": "2026-10-06T08:30:00.000Z",
    "health": {
      "windowDays": 14,
      "sent": 0,
      "bounced": 0,
      "optedOut": 0,
      "bounceRate": 0,
      "optOutRate": 0,
      "healthy": true,
      "sentToday": 0,
      "warmupCap": 13
    }
  }
}

Source test: seat routes > edits, pauses and resumes a seat. Actual route handlers with SQLite repositories; synthetic identity/workspace grants and provider ports.

Effects and response meaning

• Change a seat's display name, from address, time zone or warm-up plan. Provide at least one field (422 invalid_input).

Verify the outcome

• Check the response against the declared output schema and the requested operation. For mutations, use the action-specific read described in the action description before any dependent operation.

Recover

For an uncertain result, inspect current retained state with a read action before retrying. Do not replay a mutation unless its contract explicitly guarantees idempotency.

Refused requests

Captured HTTP 422 · seat routes > edits, pauses and resumes a seat

Action input

{
  "id": "eng_seat_1"
}

Actual local response

{
  "error": {
    "code": "invalid_input",
    "message": "Provide at least one field to change."
  }
}

Source test: seat routes > edits, pauses and resumes a seat. Actual route handlers with SQLite repositories; synthetic identity/workspace grants and provider ports.

Error recovery

• HTTP 422 invalid_input: Correct the request against the current action input schema, then validate it again before planning.

Related actions

• List sending seats
• Create sending seat
• Get sending seat
• Pause sending seat
• Resume sending seat
• Start mailbox connection (Google or Microsoft)
• Connect IMAP/SMTP mailbox
• Bind mailbox to seat
• Check seat mailbox
• Set seat WhatsApp number
• List seat health
• Get seat health

Evidence and limits

• /api/seats/{id}

• Actual route handlers with SQLite repositories; synthetic identity/workspace grants and provider ports.

• Widget/bootstrap use actual app handler but mocked worker runtime and app identity.

• No gateway execution, live permissions, external delivery or deployed proof.

These are local route captures with synthetic identity and simulated dependencies. They do not prove live authorization, gateway execution, production state, or external delivery.