Review calendar drafts through an AI assistant
By Tristan Doehl · · Updated
An AI assistant connected to Teetrack can help review calendar drafts without moving each request through the browser. The useful sequence is the same as a manual review: inspect the candidates, decide what they represent, then confirm or dismiss specific entries.
Check the connection before the drafts
The list_calendar_connections tool lists connected accounts and feeds, including lastSyncedAt and syncError. It does not list individual calendars inside each account. trigger_calendar_sync requests a refresh: a response with queued: true means the job was accepted. When you pass a connection_id, queued: false with the message “Sync already in progress or recently triggered” means the connection is still in its cooldown, and nextSyncAvailableAt from list_calendar_connections shows when another request will be accepted. Check the connection’s updated lastSyncedAt and syncError afterwards to see whether the sync completed successfully.
Use list_calendar_events to inspect the synced schedule and get_calendar_suggestions to retrieve pending draft entries. get_calendar_suggestions takes no parameters, so the assistant must filter the returned drafts by date itself. These are different views: an event can be synced without having an automatic draft, particularly outside the import window or when auto-import is disabled.
Review a defined set of entries
For an illustrative request, ask: “List the pending drafts for 4 May 2026 with their IDs, projects, and times. Do not confirm them yet.” The returned list gives you concrete targets for the next instruction.
Suppose the list contains a client review, a lunch appointment, and an internal planning session. Dismiss the lunch appointment with dismiss_draft_track, which removes the draft and remembers the event so the next sync does not bring it back. Assign the planning session to the internal project; once both remaining drafts are checked, bulk_confirm_draft_tracks can confirm them together. Identify the review by its draft ID before confirming and correcting it, so two similar titles cannot be confused.
Confirm the selected draft, then correct its times
Sync resets an unconfirmed draft’s times and description from its source event every 30 minutes. Project changes survive, but a shortened draft can return to its original duration. Use confirm_draft_track for the selected draft, then update_track to correct the confirmed entry’s times and description. Verify those changes before using it in a report.
Check that the selected entries represent completed work. Draft suggestions do not include the billable flag; use get_track to inspect it. “Confirm everything” may include future meetings or unrelated projects, so specify the IDs of the entries you actually reviewed.
Verify the result of each operation
After the changes, query the pending drafts again and inspect the confirmed time records. A batch can partially succeed if some IDs are invalid or no longer drafts, so compare the returned counts and remaining entries with your request. Retry only the part that still needs work.
OAuth connections need calendars:read to inspect connections and suggestions and calendars:write for sync and draft actions. Reading or editing the underlying entry also needs the corresponding track permissions. Plan limits still apply: calling a tool does not enable automatic import on Free. The assistant provider receives the data returned by these tools.
Keep the decision attached to the work
The MCP setup overview describes the connection, and the calendar import article explains which drafts are created. Use the assistant to carry out a review you can describe clearly; your decision about the work is still what makes a calendar proposal suitable for reporting.
