corestack_ ticket_ get
Read a support ticket.
When to use it
Read one support ticket and its conversation, as the ticket page shows it to the person: the opening message, then every
reply from the person's side and from Corefinity, oldest first. Each message comes as body_html (what the page shows) and
body_text (the same without markup). Files are listed with a url the person opens in the Control Panel while signed
in; the files themselves are not sent to you. can says whether the person can reply, close, reopen or change the
priority of the ticket.
Ask for it
Using the Corefinity MCP server, call corestack_ticket_get with ticket_id 48210. (Read a support ticket.) Tell me what it returned.Inputs
client_company_idinteger
The client company the ticket is in, when your agency raised it for a client (the same value you listed it with); your own company when left out. At least 1.
ticket_idintegerRequired
The ticket's number, from corestack_tickets_list. At least 1.
Example call
{
"name": "corestack_ticket_get",
"arguments": {
"ticket_id": 48210
}
}If it is refused
| Reason | What to do |
|---|---|
tenant_mismatch | There is no such ticket, or it is not in your company (or in client_company_id, a client company your agency reaches). A ticket of another company that the person follows is read in the Control Panel, and only while their company is one of the ticket's companies (for example their agency's ticket about their websites); following a ticket of an unrelated company shows nothing anywhere. |
pin_refused | The token is limited to some sites; a ticket belongs to the whole company. |
invalid_arguments | The arguments do not match the tool's input schema, or the Control Panel refused a field. Fix the fields named in the answer and call again. |
scope_required | The token lacks a scope this call needs. Open the link in the answer to add it, then call again. |
rate_limited | Too many calls. Wait for the number of seconds the answer names. |
temporarily_unavailable | The Control Panel could not answer just now. Nothing was started; try again shortly. |
internal_error | Something went wrong on our side. Quote the trace id to support. |
The same task elsewhere
Was this helpful?