--- title: "Connect Request Tracker (RT) to Fly.io Machines API - APIANT.ai" description: "When \"Ticket Created\" fires in Request Tracker (RT), your agent runs \"Create App\" in Fly.io Machines API." canonical: "https://apiant.ai/connect/request-tracker-rt-to-fly-io-machines-api" --- # Connect Request Tracker (RT) to Fly.io Machines API When **Ticket Created** fires in [Request Tracker (RT)](https://apiant.ai/connections/request-tracker-rt), your agent runs **Create App** in [Fly.io Machines API](https://apiant.ai/connections/fly-io-machines-api). 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 Fly.io Machines API **11** 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 Fly.io Machines API to do together? Give your AI client this address. `https://mcp.apiant.ai` One 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.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) can start in Fly.io Machines API - When **Ticket Created** in Request Tracker (RT) then **Create App** in Fly.io Machines API - When **Ticket Status Changed** in Request Tracker (RT) then **Create Machine** in Fly.io Machines API 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 Fly.io Machines API ## Triggers and actions 3 triggers · 30 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. - Action **Create App** Creates a new Fly.io app in the chosen organization and returns its id. - Action **Create Machine** Creates a new Machine in a Fly.io app from the image and configuration you provide, and returns the created Machine. - Action **Create Volume** Creates a persistent storage volume for a Fly.io app in the chosen region. - Action **Delete App** Deletes a Fly.io app by its name. - Action **Delete Machine** Deletes a Machine from a Fly.io app, optionally force-killing it if it is still running. - Action **Delete Volume** Destroys a volume in a Fly.io app and returns the deleted volume's details. - Action **Extend Volume** Extends a Fly.io volume to a larger size in gigabytes. Returns the updated volume and whether its Machine needs a restart. - Action **Start Machine** Starts a stopped or suspended Machine in a Fly.io app. - Action **Stop Machine** Stops a running Fly.io Machine in an app, optionally choosing the stop signal and how long to wait before it is killed. - Action **Suspend Machine** Suspends a Machine in a Fly.io app so its next start can resume from a snapshot instead of a cold boot. - Action **Update Machine** Updates a Fly.io Machine's configuration, such as its image, guest size, environment variables, services or restart policy, and returns the updated Machine. ## 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) - [ **Fly.io Machines API** Fly.io Machines API is a low-level interface to deploy and manage lightweight VMs globally with fine-grained...](https://apiant.ai/connections/fly-io-machines-api) 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 Fly.io Machines API - [ **HubSpot to Fly.io Machines API** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-fly-io-machines-api) - [ **Salesforce to Fly.io Machines API** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-fly-io-machines-api) - [ **Slack to Fly.io Machines API** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-fly-io-machines-api) - [ **Google Sheets to Fly.io Machines API** Google Sheets](https://apiant.ai/connect/google-sheets-to-fly-io-machines-api) - [ **Gmail to Fly.io Machines API** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-fly-io-machines-api) - [ **Google Calendar to Fly.io Machines API** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-fly-io-machines-api) Questions ## Request Tracker (RT) and Fly.io Machines API, 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 Fly.io Machines API when something happens in Request Tracker (RT)? Any of Fly.io Machines API's 11 actions, including Create App, Create Machine, Create Volume and Update Machine. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Fly.io Machines API to Request Tracker (RT)? Fly.io Machines API has no triggers in the catalog today, so automations start in Request Tracker (RT). If you need the other direction, ask: your agent reads Fly.io Machines API's API documentation and adds it. ### ### Do I have to build a connector for Request Tracker (RT) or Fly.io Machines API? 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 Fly.io Machines API 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.