Request Tracker (RT)
for LuumenAI
Read RT queues, tickets, and history. Create and update tickets as approved steps.
Connect Request Tracker and your queues become context the agent can use. It reads tickets, history, attachment lists, and user records to answer questions about what is open, who owns it, and what changed. Creating a ticket, updating fields, commenting, or replying to a requester is prepared first and held for your approval by default. Luumen authenticates with an API key.
The Request Tracker (RT) toolbox
11 tools: 7 read, 4 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadGet QueueRetrieve one visible RT queue by id or exact name, including lifecycle and capability-sensitive links.
- ReadGet TicketRetrieve one visible RT ticket, including its current fields and capability-sensitive links for allowed follow-up operations.
- ReadGet Ticket HistoryReturn one page of detailed ticket history, including transaction types, field changes, comments, creators, and timestamps.
- ReadList QueuesList queues visible to the connected RT user so an agent can select a queue for ticket search or creation.
- ReadList Ticket AttachmentsList attachment metadata references associated with a visible RT ticket without downloading attachment content.
- ReadSearch TicketsSearch visible RT tickets with an explicit TicketSQL expression and return one bounded page.
- ReadSearch UsersSearch RT users with structured field conditions and return one bounded page of user references or selected fields for requester and owner lookup.
- WriteAdd Ticket CommentAdd a private internal comment to an RT ticket. Approval by default
- WriteCreate TicketCreate a durable RT ticket in a queue. Approval by default
- WriteReply to TicketSend public correspondence on an RT ticket. Approval by default
- WriteUpdate TicketUpdate selected metadata on an existing RT ticket and verify every requested field by reading it back. Approval by default
One prompt, start to finish
What a governed Request Tracker (RT) run looks like inside Luumen.
Questions
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — add ticket comment, create ticket, reply to ticket, update ticket — is shown as a plan and requires approval by default, including the 2 actions classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Request Tracker (RT) — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Often connected alongside
All integrations
Put Request Tracker (RT) to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.