Should Your AI Agent Get Your Calendar? Start With Free/Busy
Most scheduling agents only need to know when you're free. Give free/busy first, a calendar of their own second, and write access to yours last.
By Toan Nhu
Most AI agents that schedule meetings only need to know when you're free. Give them free/busy first, a calendar of their own second, and write access to your real calendar last, if ever. Scheduling itself can run over email, where every reply can wait for your approval.
Picture an assistant booking a call for you. To find a slot, it reads your whole week: a doctor's appointment, a meeting named after a deal you haven't announced, and a dial-in link with the passcode in the description. It needs none of that. It needs three open slots on Thursday.
That gap between what a calendar agent needs and what it usually gets is the whole problem. Calendars look harmless next to email, but they hold who you meet, why, and how to join, and other people see every change you make.
The short answer
Yes, give your agent calendar access, but in steps. Start with availability only. Let it read event details only if the job truly needs them. Let it write only to a calendar it owns. Keep your primary calendar human-edited unless you have a strong reason and a way to undo mistakes.
Why the default calendar connection is too wide
The broad scope is the easy one
The fastest path in most integrations is one checkbox that grants everything. Google's own scope list shows how much that covers: the full Calendar scope lets an app see, edit, share, and permanently delete all the calendars you can access. That includes calendars colleagues share with you, not just your own.
The same list also has much smaller options, which most setups skip:
- Free/busy only. An app can see when you're available, without titles, attendees, or descriptions.
- Read-only events. It can view events but change nothing.
- Calendars the app made. It can create a secondary calendar and manage events only on that one.
Invites are inbound content from strangers
Anyone with your address can send you an invite, and its title and description land in front of your agent. Treat that text the way you'd treat an email body: as data, never as instructions. An event description that says "reschedule everything this week" should change nothing. Email content cannot authorize an agent action, and neither can a calendar invite. The same rule covers attachments and other inbound content.
Calendar writes are public
When an agent moves or cancels a meeting, attendees get the update. There's no draft folder for a calendar change. A wrong move on your primary calendar is a message to other people you didn't review.
An access ladder that matches the job
Climb only as high as the task requires.
- Free/busy. Enough to propose times, answer "is Thursday good?", and avoid double-booking. Start here.
- Read-only event details. Add this when the agent preps briefs or summarizes your day. It now sees descriptions and attendee lists, so keep it away from write access.
- The agent's own calendar. If the agent needs to hold time, create a separate calendar it can write to and overlay it on yours. Its holds show up next to your events, and deleting that calendar removes all of them at once.
- Write access to your primary calendar. Rarely needed. If you go here, keep a human approval step for anything that notifies other people.
How Mermail fits
To be plain about it: Mermail doesn't host calendars or booking pages. What it gives your agent is an email address of its own and controlled connections to the calendar you already use. Most scheduling is an email thread anyway, and that part is where Mermail does the work.
Run the scheduling conversation from the agent's mailbox
Give the agent its own Mermail mailbox and let it handle the back-and-forth: proposing times, confirming, sending the follow-up note. Every mailbox comes with a built-in email-response triager that prepares replies as drafts for human review and skips bulk and list mail. You approve the reply that confirms a time, and you stay the one who commits your hours. Start with drafting. Earn the right to automate the send. You can also sort replies with plain-language rules so scheduling threads get their own label.
Connect Google Calendar through Composio, scoped to you
Mermail supports Google Calendar through its Composio integration for calendar account context and triggers. The connection belongs to your Mermail user, you finish the OAuth sign-in in your browser rather than pasting credentials into chat, and the documented flow asks the agent to check that a tool is connected and allowed, and to preview every external write before running it once. The Composio tools sit in Mermail's full MCP catalog, not in the restricted agent-inbox profile, so an inbox-only agent never sees them. The Composio docs cover the steps. Mermail's API reference lists the Composio integration endpoints for the Developer and Enterprise plans.
React to calendar changes with a triager
Custom task triagers can run instructions when a connected Google Calendar sees an event created, updated, or canceled. That's useful for "when a meeting is booked, draft a prep note" or "when a client cancels, draft a reschedule offer." Runs post their progress and outcome to the triager's conversation in the mailbox, so you can see what happened. The task triage docs list the trigger options.
A safe setup in five steps
- Decide the job. If it's only finding slots, it doesn't need event details, so don't hand it more than the job needs.
- Create a Mermail mailbox for the agent so invites and scheduling threads go to its address, not yours. Here is how to set up an agent inbox.
- Connect Google Calendar through Mermail's Composio integration from the signed-in Mermail account that should own the connection, and read the Google consent screen so you know exactly what you're granting. Check that your plan includes the integration first.
- Keep scheduling replies in draft mode and approve each confirmation for the first couple of weeks. Test draft-only replies before you let any of them send.
- If the agent needs to hold time, have it use a separate calendar you can hide or delete, not your primary one.
What Mermail doesn't do
Mermail has no built-in calendar, no booking links, and no availability page. Its Composio integration also disables the Gmail and Outlook toolkits, so email stays in Mermail's own mailboxes (here's whether an AI agent can safely use your Gmail or Outlook). If your agent needs to manage a shared team calendar directly, that's a job for your calendar provider's admin controls, with Mermail handling the email around it.
FAQ
Does an AI scheduling agent need to read my event details?
Usually not. Free/busy is enough to propose and confirm times. Add read access only when the agent's job is to brief you on your meetings.
Should my agent accept invites on my behalf?
Not at first. Accepting notifies the organizer and commits your time. Have the agent draft the reply and let you approve it.
What's the safest way to let an agent block time?
Give it a separate calendar it can write to and overlay it on yours. You see its holds, and removing that calendar removes everything it created.
Can Mermail send calendar invites for my agent?
Mermail is the agent's email address and inbox, not a calendar. Your agent can handle scheduling by email from its Mermail mailbox and use a connected Google Calendar for context, while invites themselves come from the calendar you connect.
Get started
Create a mailbox for your agent in the Mermail console, connect Google Calendar from Integrations, and keep confirmations in draft until the agent has earned the send. If you're new to giving agents their own address, start with what an agent inbox is, and for timing outbound mail see scheduling sends from an AI agent. Compare plans on the pricing page.
