--- title: "Connect Halo Service Solutions to Spike.sh - APIANT.ai" description: "When \"New Ticket\" fires in Halo Service Solutions, your agent runs \"Add alert rule\" in Spike.sh." canonical: "https://apiant.ai/connect/halo-service-solutions-to-spike-sh" --- # Connect Halo Service Solutions to Spike.sh When **New Ticket** fires in [Halo Service Solutions](https://apiant.ai/connections/halo-service-solutions), your agent runs **Add alert rule** in [Spike.sh](https://apiant.ai/connections/spike-sh). 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 Spike.sh **25** 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 Spike.sh 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 Spike.sh - When **New Ticket** in Halo Service Solutions then **Add alert rule** in Spike.sh - When **Ticket Updated** in Halo Service Solutions then **Add escalation** in Spike.sh 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 Spike.sh ## Triggers and actions 2 triggers · 39 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 **Acknowledge incident** Acknowledge one or more Spike.sh incidents by counter id or incident id. - Action **Add alert rule** Create a new alert routing/automation rule with conditions and actions. - Action **Add escalation** Creates a new escalation policy for a Spike.sh team, defining who is notified, through which channel, and how long to wait between steps. - Action **Add integration** Create a new integration for a team (source system that sends alerts into Spike). - Action **Add on-call** Create a new on-call schedule for a team. - Action **Add service** Create a new service in a team, with name and description. - Action **Create Incident** Creates a Spike incident through one of your integrations and sends alerts. The integration decides which service and escalation policy the incident is routed to. - Action **Delete alert rule** Archives (soft-deletes) a Spike alert rule so it no longer applies to incoming incidents. - Action **Delete escalation** Archives (soft-deletes) a Spike escalation policy by its ID. - Action **Escalate incident** Escalates one or more Spike incidents to the next step of their escalation policy. - Action **Get escalation** Get escalation policy details by id. - Action **Get incident** Fetch a single incident by counter id. - Action **Get integration** Fetches an integration by its token, including its name, type, service, escalation settings and webhook URL. An error occurs if the integration is not found. - Action **Get service** Get a Spike service's details, along with its incidents and open-incident count. - Action **List alert rules** Lists all alert rules (enabled and disabled) configured for a Spike team. - Action **List escalations** Lists the escalation policies that belong to a Spike team. - Action **List incidents** Lists the incidents for a Spike.sh team. - Action **List on-calls** Lists the on-call schedules for a team. - Action **List services** Lists the services in a Spike team. - Action **List teams** Lists every team in your Spike organisation. Use a team's ID from here wherever other Spike actions ask for a team. - Action **Resolve incident** Resolve one or more incidents by counter id array. - Action **Update alert rule** Replace an existing Spike alert rule's name, conditions and actions. - Action **Update escalation** Replaces an existing escalation policy's name, steps and start delay. The whole policy is replaced, so send every step you want to keep. - Action **Update on-call** Updates an on-call schedule's name and/or moves it to another team. Rotations and layers are not changed by this action. - Action **Update service** Updates the name and/or description of an existing Spike.sh service. ## 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) - [ **Spike.sh** Spike is an incident management system with unlimited alerts and on-call schedules](https://apiant.ai/connections/spike-sh) 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 Spike.sh - [ **HubSpot to Spike.sh** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-spike-sh) - [ **Salesforce to Spike.sh** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-spike-sh) - [ **Slack to Spike.sh** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-spike-sh) - [ **Google Sheets to Spike.sh** Google Sheets](https://apiant.ai/connect/google-sheets-to-spike-sh) - [ **Gmail to Spike.sh** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-spike-sh) - [ **Google Calendar to Spike.sh** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-spike-sh) Questions ## Halo Service Solutions and Spike.sh, 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 Spike.sh when something happens in Halo Service Solutions? Any of Spike.sh's 25 actions, including Create Incident, Update alert rule, Update escalation and Update on-call. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Spike.sh to Halo Service Solutions? Spike.sh has no triggers in the catalog today, so automations start in Halo Service Solutions. If you need the other direction, ask: your agent reads Spike.sh's API documentation and adds it. ### ### Do I have to build a connector for Halo Service Solutions or Spike.sh? 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 Spike.sh 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.