Use this skill when working with HaloPSA agents (technicians) and teams — listing technicians, retrieving agent details, and listing team structures. Essential for MSP service managers assigning tickets, understanding team capacity, and looking up technician IDs for ticket assignment.
1 email curto, só com as skills novas de Documentos. 4 minutos de leitura, sem spam, cancela com 1 clique.
Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.
Ler descrição completaRecolher descrição
HaloPSA Agents and Teams
Overview
Agents in HaloPSA are the technicians who handle tickets and service delivery. Teams are groupings of agents that tickets can be assigned to. Use these tools to discover agent IDs and team structures before assigning tickets or filtering work queues.
API Patterns
List Agents
Tool: halopsa_agents_list
Key parameters:
team_id — Filter agents by team ID
inactive — Include inactive agents (default: active only)
limit — Maximum results (default: 50)
Response includes:
record_count — Total matching agents
agents — Array of agent records with ID, name, email, team membership
Get Agent Details
Tool: halopsa_agents_get
Parameters:
agent_id (required) — The agent's numeric ID
Returns full agent profile including contact details, skills, team assignments, and availability settings.
List Teams
Tool: halopsa_teams_list
Parameters:
limit — Maximum results (default: 50)
Response includes:
record_count — Total teams
teams — Array of team records with ID, name, and member count
Common Workflows
Find an Agent by Name Before Assigning a Ticket
Call halopsa_agents_list to get all active agents
Search the result for the agent by name
Use the agent's id when calling halopsa_tickets_update to assign
List All Technicians in a Team
Call halopsa_teams_list to find the team ID by name
Call halopsa_agents_list with team_id set to the team's ID
Review the returned agents for team membership
Check Agent Details for Escalation
Call halopsa_agents_get with the agent's ID
Review availability, skills, and contact information
Use details to determine escalation appropriateness
Notes
Agent IDs are required when assigning tickets via halopsa_tickets_update
Inactive agents are excluded by default — set inactive: true to include them when auditing
Teams are used for ticket routing rules in HaloPSA; consult HaloPSA admin settings for routing configuration
This skill is read-only; agent and team creation/modification must be done through the HaloPSA admin interface
