Topolo Docs Topolo Platform
Open workspace

Get reply thread

Get one reply thread with its messages oldest first (inbound replies and auto-replies, outbound human replies) and the contact it is with.

Outcome

Get one reply thread with its messages oldest first (inbound replies and auto-replies, outbound human replies) and the contact it is with.

Before you start

  • Verify the intended environment, signed-in credential, authorized organization and the action permission workspace:read.
  • Discover and select an authorized canonical Engage workspace. Pass resourceType=workspace and resourceId separately from action input.

Discover the target

topolo whoami --json
topolo actions get app_topolo_engage.threads.get --json
topolo workspaces list topolo-engage --json

Set ENGAGE_WORKSPACE_ID to the identifier of the selected authorized workspace.

Input contract

FieldRequiredDeclared constraints
idYes{"type":"string","minLength":1,"maxLength":128}

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.threads.get --data @payload.json --json
topolo actions plan app_topolo_engage.threads.get --resource-type workspace --resource-id "$ENGAGE_WORKSPACE_ID" --data @payload.json --json

Execute the unchanged validated read.

: "${ENGAGE_WORKSPACE_ID:?Set ENGAGE_WORKSPACE_ID to your selected workspace identifier}"
topolo actions call app_topolo_engage.threads.get --resource-type workspace --resource-id "$ENGAGE_WORKSPACE_ID" --data @payload.json --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 · reply inbox actions > threads.list and threads.get > gets a thread with its messages and contact, or 404

Action input

{
  "id": "eng_thr_1"
}

Actual local response

{
  "thread": {
    "id": "eng_thr_1",
    "enrollmentId": "eng_enr_1",
    "contactId": "contact_1",
    "seatId": "eng_seat_1",
    "campaignId": "eng_cmp_1",
    "subject": "Quick question, Ada",
    "status": "open",
    "intent": "unclassified",
    "ownerUserId": null,
    "firstReplyAt": "2026-10-06T08:30:00.000Z",
    "lastReplyAt": "2026-10-06T08:30:00.000Z",
    "slaDueAt": "2026-10-06T12:30:00.000Z",
    "respondedAt": null,
    "closedAt": null,
    "followUpOn": null,
    "referredContactId": null,
    "lastSnippet": "Sounds interesting",
    "createdAt": "2026-10-06T08:30:00.000Z",
    "updatedAt": "2026-10-06T08:30:00.000Z",
    "overdue": false
  },
  "messages": [
    {
      "id": "eng_thm_1",
      "threadId": "eng_thr_1",
      "direction": "inbound",
      "rfcMessageId": "<reply-4@acme.io>",
      "nexusMessageId": "email_inbound_4",
      "snippet": "Sounds interesting",
      "bodyText": "Sounds interesting, tell me more.",
      "receivedAt": "2026-10-06T08:30:00.000Z",
      "sentAt": null,
      "sentBy": null,
      "autoReply": false
    }
  ],
  "contact": {
    "id": "contact_1",
    "email": "ada@acme.io",
    "name": "Ada Lovelace"
  }
}

Source test: reply inbox actions > threads.list and threads.get > gets a thread with its messages and contact, or 404. Actual route handlers with SQLite repositories; synthetic identity/workspace grants and provider ports.

Captured HTTP 200 · inbound replies thread into the inbox > keeps each workspace's threads apart

Action input

{
  "id": "eng_thr_2"
}

Actual local response

{
  "thread": {
    "id": "eng_thr_2",
    "enrollmentId": "eng_enr_2",
    "contactId": "contact_2",
    "seatId": "eng_seat_2",
    "campaignId": "eng_cmp_2",
    "subject": "Quick question, Ada",
    "status": "open",
    "intent": "unclassified",
    "ownerUserId": null,
    "firstReplyAt": "2026-10-06T08:30:00.000Z",
    "lastReplyAt": "2026-10-06T08:30:00.000Z",
    "slaDueAt": "2026-10-06T12:30:00.000Z",
    "respondedAt": null,
    "closedAt": null,
    "followUpOn": null,
    "referredContactId": null,
    "lastSnippet": null,
    "createdAt": "2026-10-06T08:30:00.000Z",
    "updatedAt": "2026-10-06T08:30:00.000Z",
    "overdue": false
  },
  "messages": [
    {
      "id": "eng_thm_2",
      "threadId": "eng_thr_2",
      "direction": "inbound",
      "rfcMessageId": "<reply-23@acme.io>",
      "nexusMessageId": "email_inbound_23",
      "snippet": null,
      "bodyText": null,
      "receivedAt": "2026-10-06T08:30:00.000Z",
      "sentAt": null,
      "sentBy": null,
      "autoReply": false
    }
  ],
  "contact": {
    "id": "contact_2",
    "email": "grace@acme.io",
    "name": "Ada Lovelace"
  }
}

Source test: inbound replies thread into the inbox > keeps each workspace's threads apart. Actual route handlers with SQLite repositories; synthetic identity/workspace grants and provider ports.

Captured HTTP 200 · reply inbox actions > threads.list and threads.get > gets a thread with its messages and contact, or 404

Action input

{
  "id": "eng_thr_1"
}

Actual local response

{
  "thread": {
    "id": "eng_thr_1",
    "enrollmentId": "eng_enr_1",
    "contactId": "contact_1",
    "seatId": "eng_seat_1",
    "campaignId": "eng_cmp_1",
    "subject": "Quick question, Ada",
    "status": "open",
    "intent": "unclassified",
    "ownerUserId": null,
    "firstReplyAt": "2026-10-06T08:30:00.000Z",
    "lastReplyAt": "2026-10-06T08:30:00.000Z",
    "slaDueAt": "2026-10-06T12:30:00.000Z",
    "respondedAt": null,
    "closedAt": null,
    "followUpOn": null,
    "referredContactId": null,
    "lastSnippet": "Sounds interesting",
    "createdAt": "2026-10-06T08:30:00.000Z",
    "updatedAt": "2026-10-06T08:30:00.000Z",
    "overdue": false
  },
  "messages": [
    {
      "id": "eng_thm_1",
      "threadId": "eng_thr_1",
      "direction": "inbound",
      "rfcMessageId": "<reply-4@acme.io>",
      "nexusMessageId": "email_inbound_4",
      "snippet": "Sounds interesting",
      "bodyText": "Sounds interesting, tell me more.",
      "receivedAt": "2026-10-06T08:30:00.000Z",
      "sentAt": null,
      "sentBy": null,
      "autoReply": false
    }
  ],
  "contact": {
    "id": "contact_1",
    "email": "ada@acme.io",
    "name": null
  }
}

Source test: reply inbox actions > threads.list and threads.get > gets a thread with its messages and contact, or 404. Actual route handlers with SQLite repositories; synthetic identity/workspace grants and provider ports.

Captured HTTP 200 · reply inbox actions > threads.list and threads.get > gets a thread with its messages and contact, or 404

Action input

{
  "id": "eng_thr_1"
}

Actual local response

{
  "thread": {
    "id": "eng_thr_1",
    "enrollmentId": "eng_enr_1",
    "contactId": "contact_1",
    "seatId": "eng_seat_1",
    "campaignId": "eng_cmp_1",
    "subject": "Quick question, Ada",
    "status": "open",
    "intent": "unclassified",
    "ownerUserId": null,
    "firstReplyAt": "2026-10-06T08:30:00.000Z",
    "lastReplyAt": "2026-10-06T08:30:00.000Z",
    "slaDueAt": "2026-10-06T12:30:00.000Z",
    "respondedAt": null,
    "closedAt": null,
    "followUpOn": null,
    "referredContactId": null,
    "lastSnippet": "Sounds interesting",
    "createdAt": "2026-10-06T08:30:00.000Z",
    "updatedAt": "2026-10-06T08:30:00.000Z",
    "overdue": false
  },
  "messages": [
    {
      "id": "eng_thm_1",
      "threadId": "eng_thr_1",
      "direction": "inbound",
      "rfcMessageId": "<reply-4@acme.io>",
      "nexusMessageId": "email_inbound_4",
      "snippet": "Sounds interesting",
      "bodyText": "Sounds interesting, tell me more.",
      "receivedAt": "2026-10-06T08:30:00.000Z",
      "sentAt": null,
      "sentBy": null,
      "autoReply": false
    }
  ],
  "contact": null
}

Source test: reply inbox actions > threads.list and threads.get > gets a thread with its messages and contact, or 404. Actual route handlers with SQLite repositories; synthetic identity/workspace grants and provider ports.

Effects and response meaning

  • Get one reply thread with its messages oldest first (inbound replies and auto-replies, outbound human replies) and the contact it is with.

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 404 · reply inbox actions > threads.list and threads.get > gets a thread with its messages and contact, or 404

Action input

{
  "id": "eng_thr_missing"
}

Actual local response

{
  "error": {
    "code": "not_found",
    "message": "Thread was not found in this workspace."
  }
}

Source test: reply inbox actions > threads.list and threads.get > gets a thread with its messages and contact, or 404. Actual route handlers with SQLite repositories; synthetic identity/workspace grants and provider ports.

Captured HTTP 404 · reply inbox actions > threads.list and threads.get > is invisible to another organization and needs workspace:write to change

Action input

{
  "id": "eng_thr_1"
}

Actual local response

{
  "error": {
    "code": "not_found",
    "message": "Thread was not found in this workspace."
  }
}

Source test: reply inbox actions > threads.list and threads.get > is invisible to another organization and needs workspace:write to change. Actual route handlers with SQLite repositories; synthetic identity/workspace grants and provider ports.

Captured HTTP 404 · inbound replies thread into the inbox > keeps each workspace's threads apart

Action input

{
  "id": "eng_thr_2"
}

Actual local response

{
  "error": {
    "code": "not_found",
    "message": "Thread was not found in this workspace."
  }
}

Source test: inbound replies thread into the inbox > keeps each workspace's threads apart. Actual route handlers with SQLite repositories; synthetic identity/workspace grants and provider ports.

Error recovery

  • HTTP 404 not_found: Rediscover the identifier using the related list or get action in the same authorized resource. Do not guess identifiers or change organization context.

Evidence and limits

  • /api/threads/{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.