# Connect Request Tracker (RT) to Railway When **Ticket Created** fires in [Request Tracker (RT)](https://apiant.ai/connections/request-tracker-rt), your agent runs **Get project** in [Railway](https://apiant.ai/connections/railway). 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 Railway **16** 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 Railway to do together? Give your AI client this address. `https://mcp.apiant.ai` 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 Railway - When **Ticket Created** in Request Tracker (RT) then **Get project** in Railway - When **Ticket Status Changed** in Request Tracker (RT) then **Add domain** in Railway 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 Railway ## Triggers and actions 3 triggers · 35 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 **Add domain** Adds a Railway-provided or custom domain to a service instance. - Action **Add environment** Creates a new environment in a project. - Action **Add service** Creates a new service in a project, from a GitHub repo, Docker image, or empty. - Action **Delete deployment** Removes a deployment from a Railway service's deployment history. - Action **Delete environment** Deletes a Railway environment and all of its deployments. - Action **Get deployment** Fetches a deployment by ID. - Action **Get project** Fetches a project by ID including its services. - Action **Get service** Fetches a service by ID. - Action **Get variables** Fetches variables for a service/environment. - Action **List deployments** Lists the deployments of a Railway service in an environment (up to the 100 most recent). - Action **List domains** Returns the custom domains and Railway-provided domains attached to a service in one environment, with each custom domain's DNS and certificate status. - Action **List environments** Lists all environments for a project. - Action **List projects** Lists all projects accessible to the token. - Action **Rollback deployment** Rolls a Railway service back to a previous deployment. - Action **Update service** Updates a Railway service's name or icon. - Action **Update variables** Creates or updates several variables at once for a Railway service, or the shared variables of an environment. ## 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) - [ **Railway** Cloud infrastructure platform for deploying and hosting applications, databases, and background jobs from...](https://apiant.ai/connections/railway) 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 Railway - [ **Slack to Railway** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-railway) - [ **JIRA to Railway** Atlassian JIRA Cloud — issue tracking and project management.](https://apiant.ai/connect/jira-to-railway) - [ **HubSpot to Railway** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-railway) - [ **Salesforce to Railway** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-railway) - [ **Google Sheets to Railway** Google Sheets](https://apiant.ai/connect/google-sheets-to-railway) - [ **Gmail to Railway** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-railway) Questions ## Request Tracker (RT) and Railway, 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 Railway when something happens in Request Tracker (RT)? Any of Railway's 16 actions, including Update service, Update variables, Add domain and Add environment. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Railway to Request Tracker (RT)? Railway has no triggers in the catalog today, so automations start in Request Tracker (RT). If you need the other direction, ask: your agent reads Railway's API documentation and adds it. ### ### Do I have to build a connector for Request Tracker (RT) or Railway? 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.