Skip to main content
Request Tracker (RT) logo
  • Category: customer support
  • Auth: API_KEY
  • Composio-managed OAuth available? N/A
  • Tools: 11
  • Triggers: 0
  • Slug: REQUEST_TRACKER
  • Version: 20261101_00

Tools

Slug: REQUEST_TRACKER_ADD_TICKET_COMMENTAdd a private internal comment to an RT ticket. The comment creates a durable transaction that REST2 cannot remove; RT scrips may still notify staff.

Input Parameters

string
Optional nonempty message body.
string
Optional message subject.
integer
required
Numeric RT ticket id.
string
Work time to record using an RT-accepted scalar.
array
Optional small base64-encoded attachments stored in the durable ticket transaction.
string ("text/plain" | "text/html")
MIME type of the message body; defaults to text/plain when content exists.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: REQUEST_TRACKER_CREATE_TICKETCreate a durable RT ticket in a queue. Creation may run RT scrips or send notifications and cannot be fully erased through REST2.

Input Parameters

string
Initial owner username.
integer
required
Numeric destination queue id from List Queues.
string
Initial lifecycle status; must be valid for the queue lifecycle.
string
Initial ticket message content.
string
required
Ticket subject; CR and LF characters are not allowed.
integer
Initial integer priority from 0 through 99.
string
MIME type of initial content. Ticket creation supports verified plain text.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: REQUEST_TRACKER_GET_QUEUERetrieve one visible RT queue by id or exact name, including its lifecycle and capability-sensitive link relation names.

Input Parameters

string
required
Queue numeric id or exact queue name.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: REQUEST_TRACKER_GET_TICKETRetrieve one visible RT ticket, including its current fields and capability-sensitive relation names for allowed follow-up operations.

Input Parameters

integer
required
Numeric RT ticket id.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: REQUEST_TRACKER_GET_TICKET_HISTORYReturn one page of detailed ticket history, including transaction types, field changes, comments, creators, and timestamps.

Input Parameters

integer
Maximum transactions in this page (1-100).
integer
required
Numeric ticket id whose history to read.
string
Opaque continuation cursor from a previous history page; it retains the ticket id and page size.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: REQUEST_TRACKER_LIST_QUEUESList queues visible to the connected RT user so an agent can select a queue for ticket search or creation. Returns one bounded page.

Input Parameters

integer
Maximum queue references in this page (1-100).
string
Opaque continuation cursor from a previous queue page.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: REQUEST_TRACKER_LIST_TICKET_ATTACHMENTSList attachment metadata references associated with a visible RT ticket without downloading attachment content.

Input Parameters

integer
Maximum attachment references in this page (1-100).
integer
required
Numeric ticket id whose attachment metadata to list.
string
Opaque continuation cursor from a previous attachment page.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: REQUEST_TRACKER_REPLY_TO_TICKETSend public correspondence on an RT ticket. This can email requestors or other recipients according to RT configuration and creates a durable transaction that REST2 cannot remove.

Input Parameters

string
Optional nonempty message body.
string
Optional message subject.
integer
required
Numeric RT ticket id.
string
Work time to record using an RT-accepted scalar.
array
Optional small base64-encoded attachments stored in the durable ticket transaction.
string ("text/plain" | "text/html")
MIME type of the message body; defaults to text/plain when content exists.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: REQUEST_TRACKER_SEARCH_TICKETSSearch visible RT tickets with an explicit TicketSQL expression and return one bounded page. Use a condition such as id > 0 when listing tickets; an omitted search does not list all tickets.

Input Parameters

string
Comma-separated additional ticket fields to include when supported by the RT instance.
integer
Maximum tickets in this page (1-100).
string
Non-empty TicketSQL expression required on the first call, for example Status = 'open' AND Queue = 'General'. Omit when continuing with next_cursor.
string
Opaque continuation cursor returned by a previous call; it retains the original TicketSQL, fields, and page size.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: REQUEST_TRACKER_SEARCH_USERSSearch RT users with structured field conditions and return one bounded page of user references for requester and owner lookup.

Input Parameters

array
Structured RT user-search conditions required on the first call. For example, filter EmailAddress with operator = and the target address. An empty array lists users on the verified RT instance, but explicit conditions are preferred. Omit when continuing with next_cursor.
integer
Maximum users in this page (1-100).
string
Opaque continuation cursor returned by a previous call; it retains the validated filters and page size.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: REQUEST_TRACKER_UPDATE_TICKETUpdate selected metadata on an existing RT ticket and verify every requested field by reading it back. Omitted fields are unchanged.

Input Parameters

string
ETag returned by Get Ticket; provide it to reject a conflicting concurrent update.
string
New owner username.
integer
New numeric queue id.
string
New status valid under the ticket’s lifecycle.
string
New subject.
integer
New integer priority from 0 through 99.
integer
required
Numeric ticket id to update.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not