--- title: "Connect Request Tracker (RT) to F1 API - APIANT.ai" description: "When \"Ticket Created\" fires in Request Tracker (RT), your agent runs \"Find drivers by name\" in F1 API." canonical: "https://apiant.ai/connect/request-tracker-rt-to-f1-api" --- # Connect Request Tracker (RT) to F1 API When **Ticket Created** fires in [Request Tracker (RT)](https://apiant.ai/connections/request-tracker-rt), your agent runs **Find drivers by name** in [F1 API](https://apiant.ai/connections/f1-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 F1 API **12** 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 F1 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 F1 API - When **Ticket Created** in Request Tracker (RT) then **Find drivers by name** in F1 API - When **Ticket Status Changed** in Request Tracker (RT) then **Find teams by name** in F1 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 F1 API ## Triggers and actions 3 triggers · 31 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 **Find drivers by name** Searches Formula 1 drivers by first name or surname and returns the matching drivers. - Action **Find teams by name** Finds Formula 1 teams whose name matches the search text. - Action **Get driver** Returns the details of one Formula 1 driver — name, nationality, birthday, racing number and short name. - Action **Get driver standings** Returns the drivers' championship standings for a season, with each driver's position, points, wins and team. - Action **Get team** Returns the details of a Formula 1 team, including its nationality, first appearance and championship counts. - Action **List circuits** Returns all Formula 1 circuits, both active and historic, with location, length and lap record details. - Action **List drivers** Returns all Formula 1 drivers in the database, both active and retired. - Action **List drivers by season** Returns every Formula 1 driver who took part in the given season, with their team. - Action **List races by season** Returns the races of a Formula 1 season, with schedule, circuit, winner and winning team for each race. - Action **List seasons** Returns the Formula 1 World Championship seasons, with each season's year, name and Wikipedia link. - Action **List teams** Returns all Formula 1 teams, active and historic, with their nationality and championship counts. - Action **List teams by season** Returns the Formula 1 teams that competed in a given season. ## 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) - [ **F1 API** Free F1 data in real time with his own NPM package](https://apiant.ai/connections/f1-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 F1 API - [ **Tally to F1 API** The simplest way to create beautiful forms and surveys, for free.](https://apiant.ai/connect/tally-to-f1-api) - [ **HubSpot to F1 API** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-f1-api) - [ **Salesforce to F1 API** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-f1-api) - [ **Slack to F1 API** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-f1-api) - [ **Google Sheets to F1 API** Google Sheets](https://apiant.ai/connect/google-sheets-to-f1-api) - [ **Gmail to F1 API** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-f1-api) Questions ## Request Tracker (RT) and F1 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 F1 API when something happens in Request Tracker (RT)? Any of F1 API's 12 actions, including Find drivers by name, Find teams by name, Get driver and Get driver standings. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from F1 API to Request Tracker (RT)? F1 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 F1 API's API documentation and adds it. ### ### Do I have to build a connector for Request Tracker (RT) or F1 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 F1 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.