Connect Halo Service Solutions to Qstash

Both apps 36Halo Service Solutions 16Qstash 20

• 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).

No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.