organization_support_thread_get

Tool

organization_support_thread_get

Read one support thread of the caller's organization with its full conversation, each message named after its own author.

Read one support thread of the caller's organization with its full conversation, each message named after its own author. A thread of another organization — or another person's legacy personal thread — is reported as not found.

Behavior

HTTP: GET /governance/api/v1/support/threads/:id

Arguments

Name	Type	Required	Description
id	string	•	Thread uuid, from `organization_support_threads_list`.

Response

Field	Type	Always	Description
id	string	•	Thread uuid.
title	string	•	Subject of the request, e.g. "Billing export fails".
legacy	boolean	•	True for a PERSONAL thread opened before support became organization-owned. Such threads stay visible to their own author alone and cannot be migrated.
status	string	•	The status NAME the product chose, e.g. "In progress" — display text, not an id.
category	string	•	The lifecycle bucket behind that status.
messages	array	•	The whole conversation, oldest message first.
createdAt	string	•	When the thread was opened, ISO 8601 UTC.
openedByName	string	•	Name of the colleague who opened the thread. Never null — an unresolvable opener falls back to a placeholder.
lastMessageAt	string	•	When the thread last moved, ISO 8601 UTC. A thread with no replies reports its own creation.
lastMessagePreview	string	•	First 140 characters of the last message, or null when the thread has none.

Try it

Read one support thread of the caller's organization with its full conversation, each message named after its own author.

When to use

Example

Ask your agent something like this:

Read one support thread of the caller's organization with its full conversation, each message named after its own author.

The agent will invoke organization_support_thread_get with these arguments:

{
  "id": "<id>"
}