halo-change-request

Creates HaloPSA change requests through a discover-preview-confirm-submit workflow with gated writes.

650|182|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/automateyournetwork/netclaw --skill halo-change-request
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: halo-change-request
Source: https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/halo-change-request
Command: npx skills add https://github.com/automateyournetwork/netclaw --skill halo-change-request

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires fastmcp, httpx, python-dotenv.

What problem does it solve?

Raising a change request in HaloPSA/HaloITSM is error-prone because a change request is not a fixed object type — it is a per-organization ticket type whose id and custom fields vary, and orgs often define several change types (customer, internal, emergency). This Skill discovers the correct type, confirms it with a human, and gates the single write behind explicit approval so no unreviewed change ticket is ever submitted.

Core Features & Use Cases

  • Ticket Type Discovery & Caching: Lists creatable request types, asks the operator to confirm the right change type per category, and caches the confirmed catalog per tenant in Memory MCP.
  • Schema Learning: Reads the authoritative field schema via halo_get_ticket_type and inspects a real populated ticket to learn how fields are actually filled.
  • Gated Single Write: halo_create_change_request previews the exact /api/Tickets POST body with submit=false and only writes after explicit per-change operator approval.
  • Use Case: An engineer needs to file a customer-facing network change in Halo. The Skill recalls the cached customer change type, previews the full ticket payload, waits for approval, submits, and logs the decision and ticket id to the GAIT audit trail.

Quick Start

Ask the agent to open a change request in Halo for a planned network change and let it discover the ticket type, preview the ticket, and wait for your approval before submitting.

Frequently Asked Questions about halo-change-request

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a change request in HaloPSA via API?

Use halo_create_change_request with a summary, details, and the discovered ticket type id. Call it first with submit=false to preview the exact POST body, then re-call with submit=true only after explicit operator approval.

How do I find the change request ticket type id in Halo?

Call halo_list_ticket_types with can_create_only=true to list creatable request types, since change request is a per-org ticket type rather than a fixed object. When several change-shaped types appear, present them to the operator and confirm which one applies before caching it in Memory.

Does this work with both HaloPSA and HaloITSM?

Yes, HaloPSA and HaloITSM are the same product with the same REST API, differing only in packaging. The same OAuth2 client-credentials flow and ticket tools work against either edition.

Can the skill submit a Halo change ticket without approval?

No, the workflow always previews the exact /api/Tickets payload with submit=false and stops for explicit per-change human approval. Only after approval of that specific preview does it re-call with submit=true to perform the single write.

What environment variables are required for the Halo MCP server?

HALO_BASE_URL, HALO_CLIENT_ID, and HALO_CLIENT_SECRET are required for OAuth2 client-credentials authentication. Optional variables include HALO_TENANT, HALO_SCOPE, HALO_VERIFY_SSL, HALO_TIMEOUT, and pagination or rate-limit tuning settings.