Integration
Connect Request Tracker (RT) and ServeManager
When Ticket Created fires in Request Tracker (RT), your agent runs Upload File in ServeManager, or New Attempt in ServeManager to Create Ticket in Request Tracker (RT). Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want Request Tracker (RT) and ServeManager to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne connection does both: ask your client to act in an app once, or have it build an automation that keeps running. 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.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)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)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)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)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)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)Example flows
What Request Tracker (RT) and ServeManager can do together
From Request Tracker (RT) to ServeManager
When Ticket Created in Request Tracker (RT)
then Upload File in ServeManager
When Ticket Status Changed in Request Tracker (RT)
then Create Company in ServeManager
From ServeManager to Request Tracker (RT)
When New Attempt in ServeManager
then Create Ticket in Request Tracker (RT)
When New Company in ServeManager
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 ServeManager
Triggers and actions 8 triggers · 31 actions
Trigger
Ticket CorrespondenceTriggers when a ticket is replied to (that is, corresponded with).
Trigger
Ticket CreatedTriggers when a new Request Tracker ticket is created.
Trigger
Ticket Status ChangedTriggers when a Request Tracker ticket changes status. Can watch for any status change or only for changes to a specific status.
Action
Add assetCreate an asset.
Action
Add userCreate a user.
Action
Comment on a TicketAdd an internal comment to a ticket and send to any internal watchers.
Action
Create TicketCreate a new ticket in Request Tracker.
Action
Find AttachmentLocate an attachment by ID.
Action
Find TicketLocate a ticket by ID.
Action
Find TicketsIssue a query to find matching tickets.
Action
Find TransactionFind a transaction by ID
Action
Get assetRetrieves one asset by ID: name, description, status, catalog, owner, held by, contact, custom fields.
Action
Get queueGet a queue by id or name.
Action
Get userGet a user by id or name.
Action
List queuesList all queues visible to user.
Action
List ticket historyList transactions of a ticket.
Action
Reply to a TicketReply to the requestor and any internal or external watchers of a ticket.
Action
Update ticketGeneral ticket update (Owner, Priority, Queue, custom fields).
Action
Update Ticket Due DateUpdate the due date of a ticket.
Action
Update Ticket StatusUpdate the status of a ticket.
Action
Update Ticket SubjectUpdate the subject of a ticket.
Action
Update userUpdate a user.
Trigger
Invoice IssuedTriggers when an invoice is issued.
Trigger
New AttemptTriggers when a new service attempt is logged on any job.
Trigger
New CompanyTriggers when a new company is added in ServeManager.
Trigger
New JobTriggers when a new job is created in ServeManager.
Trigger
New NoteTriggers when a new note is added to any job.
Action
Cancel JobCancels a job and records a cancellation note on it.
Action
Create CompanyCreates a company (client, law firm or process server) in ServeManager, optionally with a primary contact, address, email and phone.
Action
Delete AttemptDeletes a service attempt.
Action
Find CompanyFinds ServeManager companies by a text search over company and contact details, most reliably a full email address.
Action
Find Court CaseFinds court cases by case number, plaintiff, defendant or court branch name.
Action
Find JobFinds jobs by a text search over company names, recipients, zip codes and other job details.
Action
Get AttemptReturns one service attempt by ID, including serve type, outcome, recipient and address.
Action
Get Court CaseReturns one court case by ID, including its plaintiff, defendant, case number and court.
Action
Get JobReturns one ServeManager job by its ID, including recipient, status and client details.
Action
List EmployeesLists the employees on your ServeManager account with their contact details and permission level.
Action
Update CompanyUpdates a company's name, type, website or note. An address given here is added to the company; existing addresses are kept.
Action
Upload FileAttaches a file from a public URL to an existing job, either as a document to be served or as a miscellaneous attachment. ServeManager downloads the file itself.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from Request Tracker (RT)
Request Tracker (RT) to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Request Tracker (RT) to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Request Tracker (RT) to StripeStripe is a payment processing platform for online businesses.
Request Tracker (RT) to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Request Tracker (RT) to TrelloTrello is a visual collaboration tool that organizes projects into boards, lists, and cards.
Request Tracker (RT) to ZoomZoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...
More into ServeManager
HubSpot to ServeManagerHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to ServeManagerSalesforce is a leading enterprise customer relationship management (CRM) platform.
Google Sheets to ServeManagerGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to ServeManagerGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to ServeManagerGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to ServeManagerGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Questions
Request Tracker (RT) and ServeManager, 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 ServeManager when something happens in Request Tracker (RT)?
Any of ServeManager's 12 actions, including Create Company, Update Company, Upload File and Find Company. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from ServeManager to Request Tracker (RT)?
Yes. When something happens in ServeManager, your agent can act in Request Tracker (RT) too. This page covers both directions: ServeManager'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 ServeManager?
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.
Can my AI client use Request Tracker (RT) and ServeManager without building an automation?
Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.
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.