Integration
Connect Request Tracker (RT) to Updown.io
When Ticket Created fires in Request Tracker (RT), your agent runs Create Check in Updown.io. 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 Updown.io 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 Updown.io
When Ticket Created in Request Tracker (RT)
then Create Check in Updown.io
When Ticket Status Changed in Request Tracker (RT)
then Create Recipient in Updown.io
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 Updown.io
Triggers and actions 3 triggers · 29 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.
Action
Create CheckCreates a new uptime check in updown.io for a URL you want monitored, and returns the created check including its token.
Action
Create RecipientAdds a new alert recipient (email, SMS, webhook, Slack-compatible or Microsoft Teams) to your updown.io account and returns the created recipient.
Action
Delete CheckDeletes an uptime check from updown.io by its token.
Action
Delete RecipientRemoves an alert recipient from your updown.io account by its id.
Action
Get CheckReturns a single updown.io uptime check by its token, including its current status, uptime and settings.
Action
Get Check MetricsReturns performance metrics for an updown.io check over a period — uptime, apdex, request counts and average timings, optionally grouped by time or monitoring location.
Action
List ChecksReturns every uptime check on your updown.io account with its current status and settings.
Action
List DowntimesReturns the recorded outages for an updown.io check, newest first, with the reason, start and end times and duration of each.
Action
List RecipientsReturns every alert recipient on your updown.io account — email addresses, phone numbers, webhooks and chat integrations.
Action
Update CheckUpdates the settings of an existing updown.io uptime check — its URL, name, interval, threshold, alert muting and more. Anything left blank keeps its current value.
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 Updown.io
HubSpot to Updown.ioHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to Updown.ioSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to Updown.ioSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to Updown.ioGoogle Sheets
Gmail to Updown.ioGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to Updown.ioGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Request Tracker (RT) and Updown.io, 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 Updown.io when something happens in Request Tracker (RT)?
Any of Updown.io's 10 actions, including Create Check, Create Recipient, Update Check and Get Check. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Updown.io to Request Tracker (RT)?
Updown.io has no triggers in the catalog today, so automations start in Request Tracker (RT). If you need the other direction, ask: your agent reads Updown.io's API documentation and adds it.
Do I have to build a connector for Request Tracker (RT) or Updown.io?
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.