Integration / Sales & Customer Support
Request Tracker (RT) integration
Request Tracker is a ticketing and workflow platform for managing support requests, queues, users, assets, knowledge articles, and related operations.
About Request Tracker (RT)
Request Tracker (RT) is a ticketing and workflow platform for managing support requests, queues, users, assets, and knowledge articles. It helps support and operations teams track work, enforce process, and keep request history in one place.
All integrations- Category
- Sales & Customer Support, Developer Tools & DevOps
- Connection
- API key
- Type
- Tool
- Actions
- 11
- Tags
- library
Example prompts
What you can ask Growf to do with Request Tracker (RT)
- “List new high priority support tickets”
- “Create ticket in customer support queue”
- “Summarize unresolved tickets by queue”
Available actions
11 actions your agents can run in Request Tracker (RT)
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.
Put Request Tracker (RT) to work inside Growf.
Connect it once and every workspace, agent and workflow can use it — securely, with your team in the loop.