What the agent can actually do
Reading first: list the calendars an account holds, list the events in a window, open one event with its attendees. Then writing: create an event, change one, cancel or restore it, and answer an invitation with accepted, declined or tentative. Creating a calendar is there too, for the rare case you want one. Thirteen actions in total, and the read ones are the ones you will use every day.
“What do I have tomorrow, and who am I meeting?”
Google and Microsoft behind one interface
Both connect with a hosted sign-in on their own page, so no password reaches us, and afterwards the tools are identical. That matters because most people’s week is split: a personal Google calendar, a work Microsoft one, sometimes a shared team calendar. An assistant that only sees one of them cannot answer when you are actually free.
A calendar id is not a calendar name
An account holds several calendars and their identifiers are not their display names. The listing returns the exact ids, every later action takes one, and passing a name comes back as a corrective error naming the listing to run first. It reads like pedantry until an assistant books a client meeting into your subscribed holidays calendar, where nobody looks.
Times carry an offset, always
The classic failure of calendar automation is a naive local time: an event created at 14:00 with no timezone lands an hour off for whoever reads it elsewhere. Event times carry an explicit offset, so Thursday at 2pm is resolved once and stays that instant for every attendee. You notice this exactly when it is most expensive — a call with somebody in another country.
Writing to a calendar emails real people
Creating an event is not bookkeeping: the attendees receive an invitation, and a blind retry after an ambiguous failure invites them twice. So writes are explicit actions you ask for, the state is read back rather than assumed, and a failure is reported instead of retried. Answering an invitation is its own action for the same reason — the organiser sees it.
“Accept Friday’s invitation and decline the one that overlaps it.”
What it sees, and what your employer does not
The agent reaches the calendars you connected and nothing else, and you can disconnect at any time. If your company pays for the workspace, that buys seats: it gives no administrator a way to read a member’s calendar, mail or messages. And the value appears next to your other accounts — who am I meeting, what do I know about them, what did we last say.
“Before my 2pm, brief me: LinkedIn profile, our last emails, our last WhatsApp messages.”
Common questions
Which calendars can I connect?
Google Calendar and Microsoft or Outlook calendars, each with a hosted sign-in on their own page. The tools are the same afterwards, so a week split across both is one question rather than two.
Can it create events and invite people?
Yes. Because an invitation is emailed to the attendees, creating an event is an explicit action and it is never retried blindly after an ambiguous failure.
Will it get the timezone right?
Event times carry an explicit offset rather than a naive local time, which is the usual reason an automated booking lands an hour off for the other person.
Can it answer invitations for me?
It can accept, decline or mark tentative when you ask. The organiser sees the answer, so it stays a requested action rather than something it decides.
Can my employer read my calendar because they pay?
No. Company billing covers seats and gives no administrator access to a member’s calendar, mailboxes or messages.
How Calendar works with Nilyo
Connection. Included with a Google or Microsoft sign-in: one identity gives email and calendar and counts as one account.
What your agent can do. Calendars, events in a date range, creating, updating, cancelling and restoring events, RSVPs.
Pacing and safety. No local budget.
- Combine with LinkedIn and email for meeting briefs: attendees are matched to profiles and past conversations.
All Calendar guides
Related guides
Give Nilyo to your agent.
Paste one setup link. Your agent can guide OAuth, account connection and the first useful action.