# Connect Request Tracker (RT) to PractiTest

When **Ticket Created** fires in [Request Tracker (RT)](https://apiant.ai/connections/request-tracker-rt), your agent runs **Add Issue** in [PractiTest](https://apiant.ai/connections/practitest). Describe the whole flow and it is built, tested on every scenario and kept running.

Request Tracker (RT) **3** triggers Request Tracker (RT) **19** actions PractiTest **22** actions

What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.

## What do you want Request Tracker (RT) and PractiTest to do together?

Give your AI client this address.

`https://mcp.apiant.ai`

Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.

### Set it up in your client

### Claude Code

Run this in the directory you want to work in.

`claude mcp add --transport http -s project apiant-ai https://mcp.apiant.ai`

Start Claude Code there, approve the server, and sign in in the browser page it opens.

[Claude Code guide (opens in a new tab)](https://apiant.ai/docs/mcp/claude-code)

### Claude, web and desktop

Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### Cursor

Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### Zed

Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### Codex and the ChatGPT desktop app

Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### Any other MCP client

Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

Example flows

## What Request Tracker (RT) can start in PractiTest

- When **Ticket Created** in Request Tracker (RT) then **Add Issue** in PractiTest
- When **Ticket Status Changed** in Request Tracker (RT) then **Update Issue** in PractiTest

Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.

Everything your agent can do with Request Tracker (RT) and PractiTest

## Triggers and actions 3 triggers · 41 actions

- Trigger

**Ticket Correspondence**

Triggers when a ticket is replied to (that is, corresponded with).

- Trigger

**Ticket Created**

Triggers when a new Request Tracker ticket is created.

- Trigger

**Ticket Status Changed**

Triggers when a Request Tracker ticket changes status. Can watch for any status change or only for changes to a specific status.

- Action

**Add asset**

Create an asset.

- Action

**Add user**

Create a user.

- Action

**Comment on a Ticket**

Add an internal comment to a ticket and send to any internal watchers.

- Action

**Create Ticket**

Create a new ticket in Request Tracker.

- Action

**Find Attachment**

Locate an attachment by ID.

- Action

**Find Ticket**

Locate a ticket by ID.

- Action

**Find Tickets**

Issue a query to find matching tickets.

- Action

**Find Transaction**

Find a transaction by ID

- Action

**Get asset**

Retrieves one asset by ID: name, description, status, catalog, owner, held by, contact, custom fields.

- Action

**Get queue**

Get a queue by id or name.

- Action

**Get user**

Get a user by id or name.

- Action

**List queues**

List all queues visible to user.

- Action

**List ticket history**

List transactions of a ticket.

- Action

**Reply to a Ticket**

Reply to the requestor and any internal or external watchers of a ticket.

- Action

**Update ticket**

General ticket update (Owner, Priority, Queue, custom fields).

- Action

**Update Ticket Due Date**

Update the due date of a ticket.

- Action

**Update Ticket Status**

Update the status of a ticket.

- Action

**Update Ticket Subject**

Update the subject of a ticket.

- Action

**Update user**

Update a user.

- Action

**Add Instance**

Adds a test to a test set in a PractiTest project as a new instance.

- Action

**Add Issue**

Creates an issue in a PractiTest project.

- Action

**Add Test**

Create a new test case in a project.

- Action

**Create a Run**

Uploads a new run result for a test instance in a PractiTest project — typically automated test results from CI, or a manual run with step results.

- Action

**Create Requirement**

Creates a new requirement.

- Action

**Delete Issue**

Deletes a specific issue from a PractiTest project.

- Action

**Delete Requirement**

Deletes a specific requirement from a PractiTest project.

- Action

**Delete Test**

Deletes a specific test from a PractiTest project.

- Action

**Get Issue**

Retrieves a single issue from a PractiTest project, including its attributes and custom field values.

- Action

**Get Requirement**

Retrieves a single requirement from a PractiTest project by its system id.

- Action

**Get Run**

Retrieve a single test run by id.

- Action

**Get Test**

Retrieve a single test by id.

- Action

**List Instances**

Lists the test instances in a PractiTest project, optionally filtered by test set, test, name or display id.

- Action

**List Issues**

Lists the issues in a PractiTest project, optionally narrowed by filter, display ids, title or PTQL query.

- Action

**List Projects**

Lists the projects in the PractiTest account. With a personal API token, only the projects that user can access are returned.

- Action

**List Requirements**

Returns all requirements in a PractiTest project, optionally narrowed by filter, display ids, name or PTQL query.

- Action

**List Runs**

List all test runs in a project.

- Action

**List Tests**

List all tests in a project.

- Action

**List Users**

Lists the users in the PractiTest account, optionally filtered by email address or to active users only.

- Action

**Update Issue**

Updates an existing issue in a PractiTest project. Only the fields you fill in are changed.

- Action

**Update Requirement**

Update a requirement's fields.

- Action

**Update Test**

Updates a specific test in a PractiTest project. Only the fields you fill in are changed.

## Each app on its own

- [ **Request Tracker (RT)** Request Tracker (RT) is an open-source, enterprise-grade ticketing system.](https://apiant.ai/connections/request-tracker-rt)
- [ **PractiTest** PractiTest QA and test management solution helps users to manage the development and testing process, with...](https://apiant.ai/connections/practitest)

Reviews

## What our customers say

## More from Request Tracker (RT)

- [ **Request Tracker (RT) to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/request-tracker-rt-to-salesforce)
- [ **Request Tracker (RT) to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/request-tracker-rt-to-slack)
- [ **Request Tracker (RT) to Stripe** Stripe is a payment processing platform for online businesses.](https://apiant.ai/connect/request-tracker-rt-to-stripe)
- [ **Request Tracker (RT) to Shopify** Shopify is a commerce platform for online stores and retail point-of-sale.](https://apiant.ai/connect/request-tracker-rt-to-shopify)
- [ **Request Tracker (RT) to Trello** Trello is a visual collaboration tool that organizes projects into boards, lists, and cards.](https://apiant.ai/connect/request-tracker-rt-to-trello)
- [ **Request Tracker (RT) to Zoom** Zoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...](https://apiant.ai/connect/request-tracker-rt-to-zoom)

## More into PractiTest

- [ **HubSpot to PractiTest** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-practitest)
- [ **Salesforce to PractiTest** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-practitest)
- [ **Slack to PractiTest** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-practitest)
- [ **Google Sheets to PractiTest** Google Sheets](https://apiant.ai/connect/google-sheets-to-practitest)
- [ **Gmail to PractiTest** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-practitest)
- [ **Google Calendar to PractiTest** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-practitest)

Questions

## Request Tracker (RT) and PractiTest, answered

###

### What can start an automation from Request Tracker (RT)?

Any of Request Tracker (RT)'s 3 triggers in the catalog, including Ticket Created, Ticket Status Changed and Ticket Correspondence. Describe the moment in plain language and your agent picks the right one.

###

### What can your agent do in PractiTest when something happens in Request Tracker (RT)?

Any of PractiTest's 22 actions, including Create a Run, Create Requirement, Update Issue and Update Requirement. Your agent maps the data both ways and tests every scenario before it ships.

###

### Can it also run from PractiTest to Request Tracker (RT)?

PractiTest has no triggers in the catalog today, so automations start in Request Tracker (RT). If you need the other direction, ask: your agent reads PractiTest's API documentation and adds it.

###

### Do I have to build a connector for Request Tracker (RT) or PractiTest?

No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.

###

### What happens when something fails?

Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.

###

### Is there a free plan?

Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.
