Triage Kaiten cards across boards and hold the deadlines

The agent calls the API of your Kaiten at the address you entered when connecting — the cloud https://your-company.kaiten.ru or your own domain if Kaiten runs on your servers. It reads spaces, boards and columns, cards with their due dates, assignees, tags, checklists and custom properties, comments and attached files, and out of that assembles a triage across boards: what is overdue, what has no assignee, what has not moved.

The agent takes the way Kaiten is built literally: the state of work here is set not by a separate status field but by the column the card sits in, so it reads «done» from the position on the board rather than from a label inside the card itself. It reads the structure just as literally: space, board, column and card are four levels, and the same question about what is overdue gives different lists at board level and at space level, so the agent always names the slice it counted on.

When writing, the agent does exactly what it was asked for: it creates a card in the right space and column, sets the assignee, due date and tags, adds a comment, moves the card between columns and boards, and archives what is finished. Before a move it checks that the board and the column exist and are open to the key, and after a change it re-reads the card — so it shows the actual state rather than what it sent.

The agent holds the request rate itself so as not to run into the server limits, and takes large boards page by page rather than in a single call. About new cards, comments and files it learns from Kaiten webhooks rather than by polling in circles, so a fresh card reaches the digest without waiting for the next sweep. If data is missing or the key cannot see it, the agent says so directly instead of showing an empty table.