Integration
Connect Halo Service Solutions to Instatus
When New Ticket fires in Halo Service Solutions, your agent runs Add component in Instatus. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want Halo Service Solutions and Instatus to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne 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.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)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)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)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)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)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)Example flows
What Halo Service Solutions can start in Instatus
When New Ticket in Halo Service Solutions
then Add component in Instatus
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 Instatus
Triggers and actions 2 triggers · 28 actions
- New Ticket
Triggers when a new ticket is logged in Halo.
- Ticket Updated
Triggers when a ticket is created or updated in Halo.
- Add action to ticket
Adds a new action (note, update or outcome) to an existing Halo ticket.
- Add project
Creates a new project in Halo and returns the created project record.
- Create Site
Creates a new site for a customer in Halo.
- Create Ticket
Creates a new ticket in Halo with a summary, description and optional customer, user, type, priority, status and assignment.
- Create User
Creates a new end user in Halo under the chosen site.
- Get customer
Returns a single Halo customer (client) by its ID, optionally with extra details and ticket activity.
- Get project
Returns a single Halo project by its ID, including its details and custom fields.
- Get ticket
Returns a single Halo ticket by its ID, optionally with extra details and its last action.
- Get user
Returns a single Halo user (end-user contact) by ID, with optional details, ticket activity and pop-ups.
- List customers
Returns a list of customers (clients) in Halo, optionally filtered by search text or top level.
- List tickets
Returns tickets from Halo, optionally filtered by customer, agent, status, dates, search text and more.
- List users
Returns the users (end-user contacts) in Halo, optionally filtered by customer, site, search text and other criteria.
- Update ticket
Updates an existing Halo ticket's summary, details, customer, assignment, status, priority and category. Fields left blank are not changed.
- Update user
Updates an existing Halo user's name, site, email or phone number. Fields left blank keep their current values.
- Add component
Creates a new component on an Instatus status page and returns the created component.
- Add incident update
Posts a new update to an existing incident on an Instatus status page, optionally changing the incident status and affected component statuses.
- Add maintenance
Schedules a new maintenance on an Instatus status page, with its affected components, timing and subscriber notification options.
- Add subscriber
Adds a subscriber (by email or phone) to a status page, subscribed to all components or to specific ones.
- Create Incident
Creates a new incident on an Instatus status page, optionally marking affected components and notifying subscribers.
- Delete incident
Deletes an incident from an Instatus status page.
- Get component
Returns one component on an Instatus status page, including its name, current status, description and group.
- Get incident
Returns a single incident on a status page, including its updates, affected components and the teammate who created it.
- Get maintenance
Returns one scheduled maintenance on a status page, including its updates and affected components.
- List components
Returns the components on an Instatus status page, with each component's name, status and group.
- List maintenances
Returns the scheduled, in-progress and completed maintenances on an Instatus status page.
- List status pages
Returns the status pages in your Instatus account, including each page's id, name, subdomain and current status.
- List subscribers
Returns the subscribers of an Instatus status page, optionally filtered by email/phone search or subscription status.
- Update component
Updates a component on an Instatus status page, such as its name, description, status, order or group.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from Halo Service Solutions
Halo Service Solutions to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Halo Service Solutions to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Halo Service Solutions to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Halo Service Solutions to MailchimpMailchimp marketing automation and email platform.
Halo Service Solutions to StripeStripe is a payment processing platform for online businesses.
Halo Service Solutions to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
More into Instatus
Google Sheets to InstatusGoogle Sheets
Gmail to InstatusGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to InstatusGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Halo Service Solutions and Instatus, 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 Instatus when something happens in Halo Service Solutions?
Any of Instatus's 14 actions, including Create Incident, Update component, Add component and Add incident update. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Instatus to Halo Service Solutions?
Instatus has no triggers in the catalog today, so automations start in Halo Service Solutions. If you need the other direction, ask: your agent reads Instatus's API documentation and adds it.
Do I have to build a connector for Halo Service Solutions or Instatus?
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 Instatus 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.