# Connect Request Tracker (RT) and SQL Server

When **Ticket Created** fires in [Request Tracker (RT)](https://apiant.ai/connections/request-tracker-rt), your agent runs **Add Row** in [SQL Server](https://apiant.ai/connections/sql-server), or **New or Updated Row** in SQL Server to **Create Ticket** in Request Tracker (RT). 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 SQL Server **4** triggers SQL Server **7** 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 SQL Server 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) and SQL Server can do together

### From Request Tracker (RT) to SQL Server

- When **Ticket Created** in Request Tracker (RT) then **Add Row** in SQL Server
- When **Ticket Status Changed** in Request Tracker (RT) then **Update Row** in SQL Server

### From SQL Server to Request Tracker (RT)

- When **New or Updated Row** in SQL Server then **Create Ticket** in Request Tracker (RT)
- When **New Row** in SQL Server then **Update ticket** in Request Tracker (RT)

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 SQL Server

## Triggers and actions 7 triggers · 26 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.

- Trigger

**New or Updated Row**

Triggers when a new row is added or modified.

- Trigger

**New or Updated Row (Custom Query)**

Fires for each new or changed row returned by a SELECT statement you write against the connected SQL Server database.

- Trigger

**New Row**

Triggers when you add a new row.

- Trigger

**New Table**

Fires when a new table appears in the connected SQL Server database.

- Action

**Add Row**

Add one row to a table on the connected SQL Server database.

- Action

**Delete Row**

Delete the rows in a table whose chosen column equals a value.

- Action

**Find Row**

Find the first row in a table whose chosen column matches a value.

- Action

**Find Rows via Custom Query**

Runs a SELECT statement you write against the connected SQL Server database and returns every row it matches.

- Action

**Find Row via Custom Query**

Runs a SELECT statement you write against the connected SQL Server database and returns the first row it matches.

- Action

**Run Custom Statement**

Runs a statement you write against the connected SQL Server database that changes data rather than returning rows, and reports how many rows it changed.

- Action

**Update Row**

Change column values on every row of a table whose chosen column matches a value.

## 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)
- [ **SQL Server** Connect directly to a Microsoft SQL Server database and run SQL statements from your automations.](https://apiant.ai/connections/sql-server)

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 SQL Server

- [ **HubSpot to SQL Server** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-sql-server)
- [ **Slack to SQL Server** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-sql-server)
- [ **Mailchimp to SQL Server** Mailchimp marketing automation and email platform.](https://apiant.ai/connect/mailchimp-to-sql-server)
- [ **Shopify to SQL Server** Shopify is a commerce platform for online stores and retail point-of-sale.](https://apiant.ai/connect/shopify-to-sql-server)
- [ **QuickBooks Online to SQL Server** QuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...](https://apiant.ai/connect/quickbooks-online-to-sql-server)
- [ **Pipedrive to SQL Server** Pipedrive is a sales CRM and pipeline management tool.](https://apiant.ai/connect/pipedrive-to-sql-server)

Questions

## Request Tracker (RT) and SQL Server, 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 SQL Server when something happens in Request Tracker (RT)?

Any of SQL Server's 7 actions, including Update Row, Add Row, Find Row and Find Rows via Custom Query. Your agent maps the data both ways and tests every scenario before it ships.

###

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

Yes. When something happens in SQL Server, your agent can act in Request Tracker (RT) too. This page covers both directions: SQL Server's triggers and Request Tracker (RT)'s actions are listed here as well.

###

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

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.
