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 IDinactive— Include inactive agents (default: active only)limit— Maximum results (default: 50)
Response includes:
record_count— Total matching agentsagents— 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 teamsteams— Array of team records with ID, name, and member count
Common Workflows
Find an Agent by Name Before Assigning a Ticket
- Call
halopsa_agents_listto get all active agents - Search the result for the agent by name
- Use the agent's
idwhen callinghalopsa_tickets_updateto assign
List All Technicians in a Team
- Call
halopsa_teams_listto find the team ID by name - Call
halopsa_agents_listwithteam_idset to the team's ID - Review the returned agents for team membership
Check Agent Details for Escalation
- Call
halopsa_agents_getwith 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: trueto 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