Approve Quinyx absence requests with AI

1. An employee sends an absence request from the mobile app or the staff portal. Quinyx notifies the managers who have write access on the absence permission and a direct manager role one level above the employee.
2. In the web app, the manager opens Schedule, clicks the bell icon in the upper-left corner and opens Absence requests under Needs Approval.
3. The request shows the period and the shifts scheduled in it. In the mobile Manager menu, the Time trackers icon shows how many holiday days the employee has left, if the organization uses Time Trackers.
4. For each shift in the period the manager picks Unassign, Delete, Reassign or Keep, writes a comment and selects Approve or Deny.
5. Every request is read and decided by hand, so one that arrives while the manager is away waits.

Go through the absence requests waiting for me in Quinyx. Approve those where at least 3 colleagues are still scheduled each day and the shifts can stay open, deny the ones that overlap the stocktake week, and list the rest for me.

1. 01

   Read the inbox

   Your agent calls list_approval_requests with category absence_request. It sees only the requests Quinyx sends to your account, which depend on your role and permissions, so a manager with a narrower role sees a shorter list.

2. 02

   Open each request

   get_approval_request returns the period, the employee's comment, every shift scheduled inside the period and the holiday days left when the organization uses Time Trackers. A request with no balance data is not denied for that reason; it goes on your list.

3. 03

   Check who else is working

   For each day in the period the agent calls list_shifts for the same unit and counts colleagues already scheduled. The count is judged against the number in your prompt, for example 3.

4. 04

   Choose an action per shift

   Shifts in an approved period are set to keep or unassign by default; an unassigned shift becomes open and can be offered to colleagues later. Delete and reassign are never picked on their own: a request that needs either goes on your list.

5. 05

   Decide and comment

   approve_request runs for the matches and deny_request for the ones your rule rejects, each with a comment that names the rule. Both ask for your OK per call until you switch confirmation off. Right before deciding, the agent reads the request again and skips one that another manager handled in the meantime.

Absence requests waiting: 6
Approved 3, e.g. Elena Ruiz, 4 to 5 Nov (4 colleagues scheduled each day), 2 shifts unassigned
Denied 1 (Sam Okafor, overlaps stocktake week)
Left for you 2:
- Priya Nair: only 2 colleagues scheduled on 12 Nov
- Jake Ortiz: request covers a shift that needs a reassign

curl -X POST https://cotlet.dev/api/v1/quinyx/requests/77310/approve \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"comment":"Approved: 4 colleagues are scheduled each day. Both shifts are now open.","shift_actions":[{"shift_id":"90412","action":"unassign"},{"shift_id":"90437","action":"unassign"}]}'

{
  "request_id": "77310",
  "category": "absence_request",
  "status": "approved",
  "employee": "Elena Ruiz",
  "shift_actions": [
    {
      "shift_id": "90412",
      "action": "unassign"
    },
    {
      "shift_id": "90437",
      "action": "unassign"
    }
  ],
  "comment": "Approved: 4 colleagues are scheduled each day. Both shifts are now open."
}

MCP: add https://cotlet.dev/mcp/v1 with the same key; the call is quinyx_write → approve_request. Example data.

• Offer open Quinyx shifts to the right employees
• Attest Quinyx worked hours before payroll
• Quinyx API and MCP server: every tool
• All use cases