Catch overdue YouGile tasks across every board

The agent calls YouGile through api-v2: it reads projects, boards and columns, tasks with their deadlines and assignees, task chats, employees and departments. Out of that it assembles a company-wide triage — what is past its deadline, with whom it is stuck, what was created, changed and completed in the last 24 hours for every project. The walk goes top down, from project to column, so a task does not get lost on a board you forgot about.

YouGile is built around chats: the discussion of a task lives in its message feed rather than in the description field, and the real reason a deadline moved or an assignee changed is most often written exactly there rather than on the card itself. So the agent reads the whole task chat and pulls the substance of what was agreed out of it, instead of judging the state of the work from the card fields and the column position alone.

In writing, the agent creates a task in the column you pick, writes out the brief, assigns an owner and a deadline, moves tasks between columns and posts messages in the task chat. Before creating anything it checks that the project, board and column exist and are open to the key, and after a change it re-reads the task to show its actual state. A chat message goes out under the key owner name, and the agent says so in advance.

One key serves every request, and the agent sees exactly the boards that key is open to: a closed board simply does not exist for it rather than answering with an error. YouGile hands over lists in pages, so a company-wide triage is a walk through projects, boards and columns rather than a single request, and the agent makes sure it reached the end. Notifications about a new or changed task arrive unsigned, so the agent treats them as a signal and re-reads the data through the API; if something is out of sight, it says so directly instead of showing an empty table.