Integration
Connect Request Tracker (RT) and Terros
When Ticket Created fires in Request Tracker (RT), your agent runs Create User in Terros, or New Account in Terros 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 Terros 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)Grok
Open grok.com/connectors, choose New Connector, then Custom, and paste the address. Grok signs you in in your browser.
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 Terros can do together
From Request Tracker (RT) to Terros
When Ticket Created in Request Tracker (RT)
then Create User in Terros
From Terros to 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 Terros
Triggers and actions 11 triggers · 37 actions
- Ticket Correspondence
Triggers when a ticket is replied to (that is, corresponded with).
- Ticket Created
Triggers when a new Request Tracker ticket is created.
- 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.
- Add asset
Create an asset.
- Add user
Create a user.
- Comment on a Ticket
Add an internal comment to a ticket and send to any internal watchers.
- Create Ticket
Create a new ticket in Request Tracker.
- Find Attachment
Locate an attachment by ID.
- Find Ticket
Locate a ticket by ID.
- Find Tickets
Issue a query to find matching tickets.
- Find Transaction
Find a transaction by ID
- Get asset
Retrieves one asset by ID: name, description, status, catalog, owner, held by, contact, custom fields.
- Get queue
Get a queue by id or name.
- Get user
Get a user by id or name.
- List queues
List all queues visible to user.
- List ticket history
List transactions of a ticket.
- Reply to a Ticket
Reply to the requestor and any internal or external watchers of a ticket.
- Update ticket
General ticket update (Owner, Priority, Queue, custom fields).
- Update Ticket Due Date
Update the due date of a ticket.
- Update Ticket Status
Update the status of a ticket.
- Update Ticket Subject
Update the subject of a ticket.
- Update user
Update a user.
- List Calendar Events
Triggers when a new calendar event appears in Terros.
- List Status Ids
Triggers when a new disposition (account status) is added in Terros.
- List Tasks
Triggers when a new task appears in Terros.
- List Workflow Action IDs
Triggers when a new action is added to a Terros workflow.
- List Workflow IDs
Triggers when a new workflow is added in Terros.
- List Workflow Stage IDs
Triggers when a new stage is added to a Terros workflow.
- New Account
Triggers when a new account is added in Terros.
- New User
Triggers when a new user is added to your Terros company.
- Add meeting
Creates a recurring team meeting in Terros with a schedule, reminders and optional check-in rules.
- Create/Update Account
Creates a Terros account, or updates it when the account ID is given.
- Create User
Adds a user to your Terros company.
- Delete Account
Deletes an account (a homeowner or lead record) from Terros by its account ID.
- Delete Calendar Event
Deletes a calendar event.
- Delete meeting
Archives a meeting in Terros, or permanently deletes it when Archive is set to false.
- Delete task
Removes one or more Terros tasks, archiving them by default or deleting them permanently.
- Delete User
Removes a user from your Terros company.
- Find Account
Finds a Terros account by account ID, external lead ID or source ID.
- Find User
Finds users whose name or email matches the search text.
- Get task
Returns a single Terros task by its ID, including its subject, status, owner and criteria.
- List Accounts
Returns accounts, optionally filtered by user, workflow or search text.
- List Available Closers
Lists closers and their open appointment times for a team or user.
- List Users
Returns the users in your Terros company, optionally limited to one team.
- List Workflow IDs
Returns the workflows you can see, with their IDs.
- Make Report
Runs a KPI report for the chosen KPIs, grouped by user, team or another dimension.
- Update meeting
Updates a Terros meeting, replacing its team, name, recurring schedule, reminders, check-in options, location and meeting link.
- Update User
Updates a Terros user's name, email, phone or time zone.
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 Terros
HubSpot to TerrosHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to TerrosGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to TerrosGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to TerrosGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Request Tracker (RT) and Terros, 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 Terros when something happens in Request Tracker (RT)?
Any of Terros's 18 actions, including Create/Update Account, Create User, Update meeting and Update User. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Terros to Request Tracker (RT)?
Yes. When something happens in Terros, your agent can act in Request Tracker (RT) too. This page covers both directions: Terros'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 Terros?
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 Terros 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.