--- title: "Connect Halo Service Solutions to RacingHub - APIANT.ai" description: "When \"New Ticket\" fires in Halo Service Solutions, your agent runs \"Get constructor\" in RacingHub." canonical: "https://apiant.ai/connect/halo-service-solutions-to-racinghub" --- # Connect Halo Service Solutions to RacingHub When **New Ticket** fires in [Halo Service Solutions](https://apiant.ai/connections/halo-service-solutions), your agent runs **Get constructor** in [RacingHub](https://apiant.ai/connections/racinghub). Describe the whole flow and it is built, tested on every scenario and kept running. Halo Service Solutions **2** triggers Halo Service Solutions **14** actions RacingHub **22** actions What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it. ## What do you want Halo Service Solutions and RacingHub 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 Halo Service Solutions can start in RacingHub - When **New Ticket** in Halo Service Solutions then **Get constructor** in RacingHub - When **Ticket Updated** in Halo Service Solutions then **Get constructor standings** in RacingHub 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 Halo Service Solutions and RacingHub ## Triggers and actions 2 triggers · 36 actions - Trigger **New Ticket** Triggers when a new ticket is logged in Halo. - Trigger **Ticket Updated** Triggers when a ticket is created or updated in Halo. - Action **Add action to ticket** Adds a new action (note, update or outcome) to an existing Halo ticket. - Action **Add project** Creates a new project in Halo and returns the created project record. - Action **Create Site** Creates a new site for a customer in Halo. - Action **Create Ticket** Creates a new ticket in Halo with a summary, description and optional customer, user, type, priority, status and assignment. - Action **Create User** Creates a new end user in Halo under the chosen site. - Action **Get customer** Returns a single Halo customer (client) by its ID, optionally with extra details and ticket activity. - Action **Get project** Returns a single Halo project by its ID, including its details and custom fields. - Action **Get ticket** Returns a single Halo ticket by its ID, optionally with extra details and its last action. - Action **Get user** Returns a single Halo user (end-user contact) by ID, with optional details, ticket activity and pop-ups. - Action **List customers** Returns a list of customers (clients) in Halo, optionally filtered by search text or top level. - Action **List tickets** Returns tickets from Halo, optionally filtered by customer, agent, status, dates, search text and more. - Action **List users** Returns the users (end-user contacts) in Halo, optionally filtered by customer, site, search text and other criteria. - Action **Update ticket** Updates an existing Halo ticket's summary, details, customer, assignment, status, priority and category. Fields left blank are not changed. - Action **Update user** Updates an existing Halo user's name, site, email or phone number. Fields left blank keep their current values. - Action **Get constructor** Get a Formula 1 constructor's details by constructor ID. - Action **Get constructor standings** Get the constructors' championship standings for a season. - Action **Get driver** Get a Formula 1 driver's details by driver ID. - Action **Get driver standings** Get the drivers' championship standings for a season. - Action **Get race** Get details of a specific race by race ID. - Action **Get season** Get details of a Formula 1 season by year. - Action **List constructors** List all Formula 1 constructors (teams) on record. - Action **List constructor season history** List the seasons a constructor competed in. - Action **List driver race results** List a driver's race results across their career. - Action **List drivers** List all Formula 1 drivers in the RacingHub database. - Action **List driver season history** List the seasons a driver competed in. - Action **List race pit stops** List the pit stops made during a race. - Action **List race qualifying results** List the qualifying session results for a race. - Action **List race results** List the final results of a race. - Action **List races** List Formula 1 races. - Action **List race starting grid** List the starting grid order for a race. - Action **List season constructors** List the constructors that competed in a given season. - Action **List season drivers** List the drivers who competed in a given season. - Action **List season races** List the races held in a given season. - Action **List seasons** List all Formula 1 seasons on record. - Action **List sprint race results** List the results of a race's sprint session. - Action **List sprint race starting grid** List the starting grid for a race's sprint session. ## Each app on its own - [ **Halo Service Solutions** Halo Service Solutions is a UK based company, which provides Service Desk, ITSM and PSA software solutions.](https://apiant.ai/connections/halo-service-solutions) - [ **RacingHub** RacingHub serves historical Formula 1 data and statistics as a REST API.](https://apiant.ai/connections/racinghub) Reviews ## What our customers say ## More from Halo Service Solutions - [ **Halo Service Solutions to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/halo-service-solutions-to-hubspot) - [ **Halo Service Solutions to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/halo-service-solutions-to-salesforce) - [ **Halo Service Solutions to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/halo-service-solutions-to-slack) - [ **Halo Service Solutions to Mailchimp** Mailchimp marketing automation and email platform.](https://apiant.ai/connect/halo-service-solutions-to-mailchimp) - [ **Halo Service Solutions to Stripe** Stripe is a payment processing platform for online businesses.](https://apiant.ai/connect/halo-service-solutions-to-stripe) - [ **Halo Service Solutions to Shopify** Shopify is a commerce platform for online stores and retail point-of-sale.](https://apiant.ai/connect/halo-service-solutions-to-shopify) ## More into RacingHub - [ **Vercel to RacingHub** Vercel is a platform for building, deploying, and scaling fast, modern web applications effortlessly.](https://apiant.ai/connect/vercel-to-racinghub) - [ **HubSpot to RacingHub** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-racinghub) - [ **Salesforce to RacingHub** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-racinghub) - [ **Slack to RacingHub** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-racinghub) - [ **Google Sheets to RacingHub** Google Sheets](https://apiant.ai/connect/google-sheets-to-racinghub) - [ **Gmail to RacingHub** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-racinghub) Questions ## Halo Service Solutions and RacingHub, answered ### ### What can start an automation from Halo Service Solutions? Any of Halo Service Solutions's 2 triggers in the catalog, including New Ticket and Ticket Updated. Describe the moment in plain language and your agent picks the right one. ### ### What can your agent do in RacingHub when something happens in Halo Service Solutions? Any of RacingHub's 22 actions, including Get constructor, Get constructor standings, 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 RacingHub to Halo Service Solutions? RacingHub has no triggers in the catalog today, so automations start in Halo Service Solutions. If you need the other direction, ask: your agent reads RacingHub's API documentation and adds it. ### ### Do I have to build a connector for Halo Service Solutions or RacingHub? 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 Halo Service Solutions and RacingHub 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.