The sampler sees your screen; your calendar knows the rest. Connect it once and meetings appear in your captured day, even when you are away from the keyboard, so drafted entries can cite them.
Glossa reads the day's events, read-only, and folds them into your timeline. It never writes anything back.
Connect in Settings
Fastmail, Proton, iCloud, Outlook, your firm's internal system: if it can publish an ICS feed, paste the link and Glossa reads it.
Paste a feed URL
Calendar integration is included in the Glossa AI plan. See pricing
Your timeline gets complete. A client call taken from the sofa never touches your Mac's screen, but it is in your calendar, so it lands in the captured day like everything else.
Drafts get better evidence. "ACME weekly sync, 10:00–10:28" is exactly the kind of receipt Glossa cites when it writes your entries.
Nothing is written back. Access is read-only, fetched locally on your Mac. Your calendar provider talks to your machine, not to any Glossa server, because there isn't one.
I build Glossa on my own, in the order people ask. Native Microsoft 365 sign-in, Tripletex, Harvest, Moco, your agency's home-grown timesheet: tell me what would save you the copy-paste and I'll tell you honestly where it sits on the list.
Until then, approved entries copy cleanly into anything that takes text. No integration is required to get your hours out.