Integration
Connect Request Tracker (RT) to RotaCloud
When Ticket Created fires in Request Tracker (RT), your agent runs Create User in RotaCloud. 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 RotaCloud to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny 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) can start in RotaCloud
When Ticket Created in Request Tracker (RT)
then Create User in RotaCloud
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 RotaCloud
Triggers and actions 3 triggers · 42 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.
- Assign User to Location
Adds a RotaCloud user to a location, keeping the locations they are already assigned to.
- Assign User to Role
Adds a role to a RotaCloud user's roles, keeping the roles they already have.
- Create Leave
Creates leave within RotaCloud.
- Create Location
Creates a location within RotaCloud.
- Create Role
Creates a role within RotaCloud.
- Create Shift
Creates a shift within RotaCloud.
- Create User
Creates a user within RotaCloud.
- Delete Location
Deletes a location from the RotaCloud account.
- Delete Role
Deletes a role from the RotaCloud account.
- Delete User
Deletes a user from the RotaCloud account.
- Find Leave by ID
Fetches a leave request by ID, with its employee, leave type, dates, status and messages. An error occurs if the leave is not found.
- Find Location by ID
Returns the RotaCloud location with the specified ID.
- Find Location by Name
Returns the RotaCloud locations whose name matches the specified name (case-insensitive).
- Find Role by ID
Returns the RotaCloud role with the specified ID.
- Find Role by Name
Returns the roles whose name matches the specified name.
- Find Shift by ID
Fetches a shift by ID, with its times, location, role, assigned employee, notes and whether it is published or open. An error occurs if the shift is not found.
- Find User by Email
Returns the RotaCloud user whose email address matches the specified email.
- Find User by ID
Retrieves a single RotaCloud user by their ID.
- Unassign User From Location
Removes a user from one location in RotaCloud, keeping their other location assignments.
- Unassign User From Role
Unssigns a user from a role within RotaCloud.
- Update Location
Updates an existing RotaCloud location's name, address, geolocation or timezone. Fields left blank are left unchanged.
- Update Role
Updates a role within RotaCloud.
- Update User
Updates an existing user by ID
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 RotaCloud
HubSpot to RotaCloudHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to RotaCloudGoogle Sheets
Gmail to RotaCloudGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to RotaCloudGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Request Tracker (RT) and RotaCloud, 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 RotaCloud when something happens in Request Tracker (RT)?
Any of RotaCloud's 23 actions, including Create Leave, Create Location, Create Role and Create Shift. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from RotaCloud to Request Tracker (RT)?
RotaCloud has no triggers in the catalog today, so automations start in Request Tracker (RT). If you need the other direction, ask: your agent reads RotaCloud's API documentation and adds it.
Do I have to build a connector for Request Tracker (RT) or RotaCloud?
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.