Integration
Connect Chaport and Halo Service Solutions
When Chat Stage Updated (instant) fires in Chaport, your agent runs Add action to ticket in Halo Service Solutions, or New Ticket in Halo Service Solutions to Send a Message in Chaport. 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 Chaport and Halo Service Solutions 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 Chaport and Halo Service Solutions can do together
From Chaport to Halo Service Solutions
When Chat Stage Updated (instant) in Chaport
then Add action to ticket in Halo Service Solutions
When New Chat Started in Chaport
then Create Ticket in Halo Service Solutions
From Halo Service Solutions to Chaport
When New Ticket in Halo Service Solutions
then Send a Message in Chaport
When Ticket Updated in Halo Service Solutions
then Create an Operator in Chaport
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 Chaport and Halo Service Solutions
Triggers and actions 10 triggers · 26 actions
Trigger
Chat Closed (instant)Fires when a chat is closed. Webhook event: chat.closed.
Trigger
Chat FinishedTriggers when chat is finished.
Trigger
Chat Stage Updated (instant)Fires when a chat's stage changes. Webhook event: chat.stageUpdated.
Trigger
Message Read (instant)Fires when a message is read. Webhook event: message.read.
Trigger
New Chat StartedTriggers when chat is started.
Trigger
New Message Sent (instant)Fires when a new message is sent in a chat. Webhook event: message.sent.
Trigger
New Visitor (instant)Fires when a new visitor is created. Webhook event: visitor.created.
Trigger
Visitor UpdatedTriggers when visitor data is updated.
Action
Create an OperatorAdds a new operator to your Chaport account and returns the created operator.
Action
Delete a MessageDeletes one message from a Chaport chat. Identify the visitor and the message you want removed.
Action
Delete an OperatorRemoves an operator from your Chaport account.
Action
List OperatorsReturns every operator in your Chaport account, with each operator's name, email, role and status.
Action
List VisitorsReturns the visitors in your Chaport account, one page at a time.
Action
Retrieve an OperatorReturns one Chaport operator with their name, email, role, job title and current status.
Action
Retrieve a VisitorReturns one Chaport visitor with their name, contact details, notes and any custom data held about them.
Action
Retrieve Last Visitor ChatReturns a visitor's most recent Chaport chat, including its stage, operators and — when asked for — the transcript.
Action
Send a MessagePosts a message into a Chaport visitor's chat, starting a chat if there isn't one open.
Action
Update an OperatorUpdates a Chaport operator's details. Anything you leave blank keeps its current value.
Action
Update a VisitorUpdates an existing Chaport visitor's contact details, notes and custom data. Only the fields you fill in are changed; blank fields are left untouched.
Action
Update Operator StatusSets a Chaport operator's availability status, such as online or offline, optionally for a limited time.
Trigger
New TicketTriggers when a new ticket is logged in Halo.
Trigger
Ticket UpdatedTriggers when a ticket is created or updated in Halo.
Action
Add action to ticketAdds a new action (note, update or outcome) to an existing Halo ticket.
Action
Add projectCreates a new project in Halo and returns the created project record.
Action
Create SiteCreates a new site for a customer in Halo.
Action
Create TicketCreates a new ticket in Halo with a summary, description and optional customer, user, type, priority, status and assignment.
Action
Create UserCreates a new end user in Halo under the chosen site.
Action
Get customerReturns a single Halo customer (client) by its ID, optionally with extra details and ticket activity.
Action
Get projectReturns a single Halo project by its ID, including its details and custom fields.
Action
Get ticketReturns a single Halo ticket by its ID, optionally with extra details and its last action.
Action
Get userReturns a single Halo user (end-user contact) by ID, with optional details, ticket activity and pop-ups.
Action
List customersReturns a list of customers (clients) in Halo, optionally filtered by search text or top level.
Action
List ticketsReturns tickets from Halo, optionally filtered by customer, agent, status, dates, search text and more.
Action
List usersReturns the users (end-user contacts) in Halo, optionally filtered by customer, site, search text and other criteria.
Action
Update ticketUpdates an existing Halo ticket's summary, details, customer, assignment, status, priority and category. Fields left blank are not changed.
Action
Update userUpdates an existing Halo user's name, site, email or phone number. Fields left blank keep their current values.
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 Chaport
Chaport to StripeStripe is a payment processing platform for online businesses.
Chaport to ChatraceOmnichannel chatbot platform for automating customer support and sales via WhatsApp, SMS, Messenger...
Chaport to keycdn IP Location FinderGet the IP geolocation data through the simple REST API. All the responses are JSON encoded
Chaport to ProxiedMailProxiedMail provides creating email addresses, forwarding and receiving emails with full context.
Chaport to PublicaWith Publica, you can sell, share and consume all kinds of digital content directly through a reliable and...
Chaport to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
More into Halo Service Solutions
Google Sheets to Halo Service SolutionsGoogle Sheets
Gmail to Halo Service SolutionsGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to Halo Service SolutionsGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to Halo Service SolutionsGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
ActiveCampaign to Halo Service SolutionsActiveCampaign is a marketing automation, email marketing, and CRM platform.
Airtable to Halo Service SolutionsOrganize anything with Airtable, a modern database created for everyone.
Questions
Chaport and Halo Service Solutions, answered
What can start an automation from Chaport?
Any of Chaport's 8 triggers in the catalog, including Chat Stage Updated (instant), New Chat Started, New Message Sent (instant) and New Visitor (instant). Describe the moment in plain language and your agent picks the right one.
What can your agent do in Halo Service Solutions when something happens in Chaport?
Any of Halo Service Solutions's 14 actions, including Create Site, Create Ticket, Create User and Update ticket. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Halo Service Solutions to Chaport?
Yes. When something happens in Halo Service Solutions, your agent can act in Chaport too. This page covers both directions: Halo Service Solutions's triggers and Chaport's actions are listed here as well.
Do I have to build a connector for Chaport or Halo Service Solutions?
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 Chaport and Halo Service Solutions 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.