Connect Request Tracker (RT) to your AI agent

Support 11 actions available

Request Tracker is a ticketing and workflow platform for managing support requests, queues, users, assets, knowledge articles, and related operations.

We set up the connection using your own Request Tracker (RT) account, with keys you control, and keep it running. Your agent picks it up and starts doing the work.

What your agent can do in Request Tracker (RT)

Each one is a real action the agent can take on its own, the same things a person clicking around Request Tracker (RT) could do. Read-only by default; write actions are confirmed against your policy.

  • Add Ticket Comment Add a private internal comment to an RT ticket. The comment creates a durable transaction that REST2 cannot remove; RT scrips may still notify staff.
  • Create Ticket Create a durable RT ticket in a queue. Creation may run RT scrips or send notifications and cannot be fully erased through REST2.
  • Get Queue Retrieve one visible RT queue by id or exact name, including lifecycle and capability-sensitive links.
  • Get Ticket Retrieve one visible RT ticket, including its current fields and capability-sensitive links for allowed follow-up operations.
  • Get Ticket History Return one page of detailed ticket history, including transaction types, field changes, comments, creators, and timestamps.
  • List Queues List queues visible to the connected RT user so an agent can select a queue for ticket search or creation. Returns one bounded page.
  • List Ticket Attachments List attachment metadata references associated with a visible RT ticket without downloading attachment content.
  • Reply to Ticket Send 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.
  • Search Tickets Search 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.
  • Search Users Search RT users with structured field conditions and return one bounded page of user references or selected fields for requester and owner lookup.
  • Update Ticket Update selected metadata on an existing RT ticket and verify every requested field by reading it back. Omitted fields are unchanged.

How we connect it

  1. 1

    Connect your account

    You create a key in Request Tracker (RT), a key you create and control, and paste it in once. It lives in a secrets store on your server, not with us.

  2. 2

    Set the guardrails

    Read-only by default. You choose which write actions the agent may take, and anything outside that policy gets confirmed with you first.

  3. 3

    We keep it running

    Health checks on every connection, updates handled for you, and we watch the first week of activity to make sure the work lands.

Request Tracker (RT) questions, answered.

With a key you create and control. You paste it in once, it is stored in a secrets store on your server, permissions are scoped to the minimum the agent needs, and you can revoke it at any time.
The actions Request Tracker (RT)'s API allows, the same things a person clicking around the app could do. Connections start read-only by default; write actions are confirmed against the policy you set before the agent takes them.
Connections are priced per tool on top of the base plan. Some are included, some are premium. See pricing for how connection charges work.
Standard tools are ready inside 7 business days of the setup call. We test the connection end to end, walk you through how the agent uses it, and watch the first week of activity.

Ready to put Request Tracker (RT) to work?

Tell us what your team runs on. We set up the connection, secure it, and your agent takes it from there.

All product names, logos, and brands are property of their respective owners; used for identification only. ZeroToClaw is not affiliated with or endorsed by Request Tracker (RT).