Practical guides for software engineers — unified calendar and email, AI task extraction, and scheduling when your team spans Google and Microsoft.
Kvika is in private beta
Unified calendar, email, and tasks for engineering teams.
Incremental sync, process-then-advance cursors, name resolution without extra scopes, trace dedupe, and draft-then-confirm AI — themes from twelve months shipping a unified calendar, mail, and task workspace.
'Email Alex and book a meeting' — prompt contracts, clientActions arrays, mapper registries, and why stopping after the first tool is a model habit you have to break.
External attendees stay fixed. Focus blocks move. The isEventManageable rules and isManaged opt-in that keep automatic rescheduling from cancelling your client call.
Multiple tabs, webhooks, cron, and user clicks hitting the same expired Microsoft or Google token — proactive refresh, fire-and-forget listeners, and reconnect UX when invalid_grant wins.
Focus hours, meeting load, task sources, and integration health — computed from CalendarEvent, Task, and CalendarSync rows you already have, with rule-based insights instead of a metrics warehouse.
When the model returns 2025-06-09T14:00 with no Z, calling toISOString() schedules the wrong meeting. Wall-clock local strings and explicit offset handling in meeting drafts.
HTML strip in code, classification in the LLM, batch size eight, 14-day lookback — a Teams pipeline designed for false negatives over invented tasks.
One user message produced two email drafts and two meeting cards. The agent did not call tools twice — the trace tree echoed the same Lambda JSON in four places. How we parse and fingerprint tool output.
AWS Bedrock action groups invoke Lambdas that POST to internal compose, meeting, and Jira routes — shared-secret auth, userEmail propagation, and why we never duplicated business logic in Lambda.
One LLM call per ten emails, temporary IDs in prompts, conservative confidence thresholds, and human-review-friendly task creation — how we extract action items without spamming false positives.
Gmail Pub/Sub, Microsoft Graph webhooks, and a unified SSE channel — layered with incremental sync and polling so near-live inboxes do not devolve into full fetches every thirty seconds.
Microsoft Graph findMeetingTimes often returns zero suggestions. emptySuggestionsReason, per-attendee tokens, and the manual calendar grid fallback we built when the API gives up.
Users say 'email Sarah' — not sarah@company.com. A three-tier directory lookup across Teams, past calendar attendees, and org search, with fuzzy scoring and graceful degradation when admin consent blocks directory APIs.
modifiedLocally, CONFLICT status, and scoped delete reconciliation — how we sync Google and Outlook calendars while letting users drag events and an algorithm reschedule focus blocks.
Saving Gmail historyId or Outlook deltaLink right after fetch loses mail when LLM extraction fails mid-run. Process-then-advance is a different contract than mirror sync.
Gmail uses historyId. Outlook uses deltaLink. Two JSON shapes, two deletion semantics — how we merge both into one live inbox without re-fetching everything on every refresh.
A practical guide to incremental calendar sync across Google and Microsoft — sync tokens, delta queries, and the normalization layer every unified calendar needs.
Why engineers miss tasks hidden in email threads — and a practical system for turning messages into tracked work without living in your inbox.
Practical strategies for finding meeting times across Gmail Calendar and Outlook — without the back-and-forth email chains.