Integration
Connect Halo Service Solutions and Salesforce
When New Ticket fires in Halo Service Solutions, your agent runs Create object record in Salesforce, or New object record in Salesforce to Add action to ticket in Halo Service Solutions. 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 Salesforce 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 and Salesforce can do together
From Halo Service Solutions to Salesforce
When New Ticket in Halo Service Solutions
then Create object record in Salesforce
When Ticket Updated in Halo Service Solutions
then Find most recent created or updated record in Salesforce
From Salesforce to Halo Service Solutions
When New object record in Salesforce
then Add action to ticket in Halo Service Solutions
When New or updated object record in Salesforce
then Create Ticket in Halo Service Solutions
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 Salesforce
Triggers and actions 4 triggers ยท 23 actions
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.
Trigger
New object recordPolling trigger: fires for each new record created in the specified SObject type. Polls SOQL ordered by CreatedDate descending.
Trigger
New or updated object recordPolling trigger: fires for each record created or modified in the specified SObject type. Polls SOQL ordered by SystemModstamp descending.
Action
Create object recordCreates a new record of the specified SObject type (standard or custom, e.g. Account, Contact, Lead, Opportunity, Case, or MyObject__c) with the supplied field values.
Action
Delete object recordDeletes an existing SObject record by object type and record ID.
Action
Describe objectReturns the full field and metadata description (describe) for an SObject type โ useful for discovering available fields and their API names.
Action
Find most recent created or updated recordReturns the single most recently created or last-modified record for the specified SObject type (ordered by SystemModstamp DESC, LIMIT 1).
Action
Find object recordsFinds matching records for an SObject type by a field/value equality match via SOQL. Returns Id and the requested fields for all matches.
Action
Get object recordRetrieves a single SObject record by object type and record ID. Optionally restrict returned fields with a comma-separated 'fields' list.
Action
List objectsLists all available SObject types (standard and custom) on the org.
Action
SOQL queryExecutes a SOQL query against the org and returns matching records. Example: SELECT Id, Name FROM Account WHERE CreatedDate = TODAY.
Action
Update object recordUpdates an existing SObject record by object type and record ID with the supplied field values. Salesforce returns no body on success (HTTP 204).
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 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.
Halo Service Solutions to QuickBooks OnlineQuickBooks Online accounting โ manage customers, invoices, bills, payments, vendors, expenses, and more via...
More into Salesforce
HubSpot to SalesforceHubSpot is your all-in-one stop for all of your marketing software needs.
Google Calendar to SalesforceGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to SalesforceGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Mailchimp to SalesforceMailchimp marketing automation and email platform.
QuickBooks Online to SalesforceQuickBooks Online accounting โ manage customers, invoices, bills, payments, vendors, expenses, and more via...
Pipedrive to SalesforcePipedrive is a sales CRM and pipeline management tool.
Questions
Halo Service Solutions and Salesforce, 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 Salesforce when something happens in Halo Service Solutions?
Any of Salesforce's 9 actions, including Create object record, Find most recent created or updated record, Update object record and Describe object. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Salesforce to Halo Service Solutions?
Yes. When something happens in Salesforce, your agent can act in Halo Service Solutions too. This page covers both directions: Salesforce's triggers and Halo Service Solutions's actions are listed here as well.
Do I have to build a connector for Halo Service Solutions or Salesforce?
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 Salesforce 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.