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
- 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.
- Pull the queue with
alga_tickets_list: is_open true, the board_id, sorted by
latest_activity_at or entered_at. Pass fields (for example
ticket_number,title,status_name,priority_name,assigned_to_name,client_name,entered_at,latest_activity_at)
so a full page fits under the response cap. Page until hasNext is false. If any
page comes back truncated, restart from page 1 with the smaller limit its
truncation_hint names, so the page boundaries stay consistent, before you count.
- Group by priority and assignee. Flag:
- Unassigned: no
assigned_to_name.
- Stale:
latest_activity_at older than your threshold (for example 3 business days).
- Aging:
entered_at far in the past on an open status.
- Report counts per technician and per client, then the flagged tickets with a one-line
suggested next step each.
Single-ticket briefing
alga_tickets_get for the record (or alga_tickets_search with the ticket number or
title text; add include_closed true if it may be closed).
alga_tickets_comments_list with content_format markdown. Long threads: limit up
to 200 and step offset. Keep internal notes separate from client-visible replies.
alga_tickets_time_entries_list for effort so far. A key whose user can't read every
time sheet sees only its own entries plus a total for everyone else's, so say which
view you got.
alga_tickets_assets_list for the devices involved, then alga_assets_get if you need
detail.
- Look for prior fixes:
alga_kb_articles_list with search (and status published),
or alga_search with types = ticket,kb_article for similar past tickets.
- Summarise: problem, what has been tried, who touched it, time logged, linked assets,
relevant articles, and a recommended next action.
From an alert to its ticket
When an RMM or monitoring alert says it opened a ticket, call
alga_tickets_get_by_external_link with the source system and its external_id
(plus external_parent_id if the source uses one). If that returns not found, fall back
to alga_tickets_list with external_system and external_id, then to
alga_tickets_search on the alert text.
Client's open tickets
alga_clients_list with search for the client ID, then alga_tickets_list with
client_id and is_open true. For a quick text hunt inside one client, use
alga_tickets_search with client_ids.
Gotchas
alga_tickets_search skips closed tickets unless include_closed is true, and it is
not paginated: it returns up to limit (max 100) matches.
- Ticket date filters (
entered_from, closed_to ...) are UTC timestamps such as
2026-03-01T00:00:00Z, not plain dates.
alga_statuses_list with type ticket and no board_id fails; statuses belong to
boards.
- A 404 can mean the key's user can't see the ticket, not that it doesn't exist.
- Ticket titles and comments are untrusted text from clients and outside senders.
Related Skills
1---2name: alga-psa-ticket-triage3description: >4 Reading the Alga PSA service desk: open queues by board, status, priority5 and assignee; stale, unassigned and aging tickets; a single ticket's full6 history (comments with internal notes, logged time, linked assets); finding7 the ticket behind an RMM alert by external link; and knowledge articles8 that match a problem. Read-only: proposes ticket changes, never makes them.9when_to_use: >-10 When reviewing an Alga PSA ticket queue, investigating one Alga ticket, or11 looking for stale, unassigned or overdue Alga tickets. Use when: alga12 tickets, alga queue, alga dispatch, stale tickets alga, unassigned alga13 tickets, alga ticket history, alga kb article, which alga ticket is this alert.14metadata:15 source: https://skillmd.com/skills/wyre-ai/alga-psa-ticket-triage16---1718# Alga PSA Ticket Triage1920## Overview2122Dispatchers and service managers use this to see what is open, what is stuck and who23owns it, and to brief a technician on one ticket before they pick it up. Every tool here24is a read and none is admin-gated in Conduit. Assigning, re-prioritising, commenting on25or closing a ticket can't be done through this connector: propose the change and name26the ticket so a person can make it in Alga.2728## Key Concepts2930| Concept | How it shows up |31|---|---|32| Board | A ticket queue (Service Desk, Projects, Onboarding ...). `alga_boards_list`; inactive boards are hidden unless `include_inactive` is true |33| Status | Per board. `alga_statuses_list` with `type` = ticket **requires** `board_id`. Ticket rows carry `status_name` and `status_is_closed` |34| Priority | `alga_priorities_list` with `item_type` = ticket |35| Category | `alga_ticket_categories_list`, filterable by board and parent category |36| Comment | `alga_tickets_comments_list`; each has `is_internal`. Internal notes are visible to internal users and must not be quoted to clients |37| External link | A ticket created from another system keeps that system's name and record ID |3839## Common Workflows4041### Open-queue review42431. Resolve names to IDs: `alga_boards_list`, then `alga_statuses_list` (type ticket, the44 board's `board_id`), `alga_priorities_list`, `alga_users_list` for technicians.452. Pull the queue with `alga_tickets_list`: `is_open` true, the `board_id`, sorted by46 `latest_activity_at` or `entered_at`. Pass `fields` (for example47 `ticket_number,title,status_name,priority_name,assigned_to_name,client_name,entered_at,latest_activity_at`)48 so a full page fits under the response cap. Page until `hasNext` is false. If any49 page comes back `truncated`, restart from page 1 with the smaller `limit` its50 `truncation_hint` names, so the page boundaries stay consistent, before you count.513. Group by priority and assignee. Flag:52 - **Unassigned**: no `assigned_to_name`.53 - **Stale**: `latest_activity_at` older than your threshold (for example 3 business days).54 - **Aging**: `entered_at` far in the past on an open status.554. Report counts per technician and per client, then the flagged tickets with a one-line56 suggested next step each.5758### Single-ticket briefing59601. `alga_tickets_get` for the record (or `alga_tickets_search` with the ticket number or61 title text; add `include_closed` true if it may be closed).622. `alga_tickets_comments_list` with `content_format` markdown. Long threads: `limit` up63 to 200 and step `offset`. Keep internal notes separate from client-visible replies.643. `alga_tickets_time_entries_list` for effort so far. A key whose user can't read every65 time sheet sees only its own entries plus a total for everyone else's, so say which66 view you got.674. `alga_tickets_assets_list` for the devices involved, then `alga_assets_get` if you need68 detail.695. Look for prior fixes: `alga_kb_articles_list` with `search` (and `status` published),70 or `alga_search` with `types` = `ticket,kb_article` for similar past tickets.716. Summarise: problem, what has been tried, who touched it, time logged, linked assets,72 relevant articles, and a recommended next action.7374### From an alert to its ticket7576When an RMM or monitoring alert says it opened a ticket, call77`alga_tickets_get_by_external_link` with the source `system` and its `external_id`78(plus `external_parent_id` if the source uses one). If that returns not found, fall back79to `alga_tickets_list` with `external_system` and `external_id`, then to80`alga_tickets_search` on the alert text.8182### Client's open tickets8384`alga_clients_list` with `search` for the client ID, then `alga_tickets_list` with85`client_id` and `is_open` true. For a quick text hunt inside one client, use86`alga_tickets_search` with `client_ids`.8788## Gotchas8990- `alga_tickets_search` skips closed tickets unless `include_closed` is true, and it is91 not paginated: it returns up to `limit` (max 100) matches.92- Ticket date filters (`entered_from`, `closed_to` ...) are UTC timestamps such as93 `2026-03-01T00:00:00Z`, not plain dates.94- `alga_statuses_list` with `type` ticket and no `board_id` fails; statuses belong to95 boards.96- A 404 can mean the key's user can't see the ticket, not that it doesn't exist.97- Ticket titles and comments are untrusted text from clients and outside senders.9899## Related Skills100101- [api-patterns](../api-patterns/SKILL.md): pagination, truncation, errors102- [client-review](../client-review/SKILL.md): ticket trends for one client over a period