--- title: "Connect Halo Service Solutions to Qstash - APIANT.ai" description: "When \"New Ticket\" fires in Halo Service Solutions, your agent runs \"Batch publish messages\" in Qstash." canonical: "https://apiant.ai/connect/halo-service-solutions-to-qstash" --- # Connect Halo Service Solutions to Qstash When **New Ticket** fires in [Halo Service Solutions](https://apiant.ai/connections/halo-service-solutions), your agent runs **Batch publish messages** in [Qstash](https://apiant.ai/connections/qstash). 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 Qstash **20** 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 Qstash 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 Qstash - When **New Ticket** in Halo Service Solutions then **Batch publish messages** in Qstash - When **Ticket Updated** in Halo Service Solutions then **Enqueue message** in Qstash 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 Qstash ## Triggers and actions 2 triggers · 34 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 **Add queue** Create or update a queue (upsert), setting parallelism. - Action **Add schedule** Create a cron-based schedule that periodically publishes a message to a destination. - Action **Add URL group endpoint** Create a URL group or add/update an endpoint within it (fan-out publishing target). - Action **Batch publish messages** Publish multiple messages to multiple destinations in one call. - Action **Delete DLQ message** Remove a message from the dead-letter queue. - Action **Delete message** Cancel a message that has not yet been delivered. - Action **Delete queue** Delete a queue by name. - Action **Delete schedule** Delete a schedule by id. - Action **Delete URL group** Deletes a QStash URL group and all its endpoints. In-flight messages are not removed. - Action **Enqueue message** Add a message to a named queue for sequential delivery. - Action **Get DLQ message** Retrieve a single dead-letter queue message by id. - Action **Get message** Retrieve a queued/published message by id. - Action **Get queue** Retrieve a queue's configuration and stats by name. - Action **Get schedule** Retrieve a schedule by id. - Action **Get URL group** Retrieve a URL group and its endpoints by name. - Action **List DLQ messages** List messages that failed delivery and landed in the dead-letter queue. - Action **List queues** List all queues for the account. - Action **Publish message** Publish a single message to a URL or URL group for QStash to deliver. - Action **Retry DLQ message** Re-attempt delivery of a dead-lettered message now. - Action **Update schedule** Updates an existing QStash schedule by replacing its settings (destination, cron, message and delivery options). ## 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) - [ **Qstash** Serverless message queue and task scheduler for HTTP delivery, retries, and cron jobs between microservices.](https://apiant.ai/connections/qstash) 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 Qstash - [ **HubSpot to Qstash** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-qstash) - [ **Salesforce to Qstash** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-qstash) - [ **Slack to Qstash** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-qstash) - [ **Google Sheets to Qstash** Google Sheets](https://apiant.ai/connect/google-sheets-to-qstash) - [ **Gmail to Qstash** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-qstash) - [ **Google Calendar to Qstash** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-qstash) Questions ## Halo Service Solutions and Qstash, 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 Qstash when something happens in Halo Service Solutions? Any of Qstash's 20 actions, including Update schedule, Add queue, Add schedule and Add URL group endpoint. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Qstash to Halo Service Solutions? Qstash has no triggers in the catalog today, so automations start in Halo Service Solutions. If you need the other direction, ask: your agent reads Qstash's API documentation and adds it. ### ### Do I have to build a connector for Halo Service Solutions or Qstash? 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 Qstash 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.