Skip to main content
You do not need these names to use the server. Ask in plain language and the assistant picks the right tool. The list is here for when you want to know exactly what a connection can do. What each tool returns is bounded by the credential behind it. On an OAuth connection every listing and every single-record read is filtered to the permissions of the person who approved it; an API key reaches the whole workspace. See Authentication.

Tickets

Tickets are addressed by ticket number or by UUID, so 42 and the UUID both work.
search and fetch are the two tools the ChatGPT connector specification requires, so they overlap with ListTickets and GetTicket rather than adding anything new. They have no separate REST endpoint, which is why they are not linked above.

Comments and drafts

A ticket holds at most one draft per comment type. There is no tool for reading a draft back, or for editing a comment once it is posted.

Customers

There is no tool for reading or updating a customer. A ticket reports its customer’s email address, so read the ticket instead.

Team members

Managing team members needs the member-management permission on the connected account.

Forms

Reports

Workspaces

An OAuth grant covers the workspace you picked when you approved it. An API key covers the workspace it was generated in.