← ClaudeAtlas

alga-psa-ticket-triagelisted

Reading the Alga PSA service desk: open queues by board, status, priority and assignee; stale, unassigned and aging tickets; a single ticket's full history (comments with internal notes, logged time, linked assets); finding the ticket behind an RMM alert by external link; and knowledge articles that match a problem. Read-only: proposes ticket changes, never makes them.
WYRE-AI/msp-claude-plugins · ★ 55 · AI & Automation · score 84
Install: claude install-skill WYRE-AI/msp-claude-plugins
# Alga PSA Ticket Triage ## Overview Dispatchers and service managers use this to see what is open, what is stuck and who owns it, and to brief a technician on one ticket before they pick it up. Every tool here is a read and none is admin-gated in Conduit. Assigning, re-prioritising, commenting on or closing a ticket can't be done through this connector: propose the change and name the ticket so a person can make it in Alga. ## Key Concepts | Concept | How it shows up | |---|---| | Board | A ticket queue (Service Desk, Projects, Onboarding ...). `alga_boards_list`; inactive boards are hidden unless `include_inactive` is true | | Status | Per board. `alga_statuses_list` with `type` = ticket **requires** `board_id`. Ticket rows carry `status_name` and `status_is_closed` | | Priority | `alga_priorities_list` with `item_type` = ticket | | Category | `alga_ticket_categories_list`, filterable by board and parent category | | Comment | `alga_tickets_comments_list`; each has `is_internal`. Internal notes are visible to internal users and must not be quoted to clients | | External link | A ticket created from another system keeps that system's name and record ID | ## Common Workflows ### Open-queue review 1. Resolve names to IDs: `alga_boards_list`, then `alga_statuses_list` (type ticket, the board's `board_id`), `alga_priorities_list`, `alga_users_list` for technicians. 2. Pull the queue with `alga_tickets_list`: `is_open` true, the `board_id`, sorted by `latest_activity