Run your Outlook inbox and calendar through your agent

Most of the work an inbox creates is sorting, before any writing happens. You scan what came in overnight, decide what needs a reply today, push the rest, and line the messages up against the meetings on your calendar so you know what is urgent. That triage is the same motion every morning, and it eats the first stretch of the day before you have answered a single thing.

An agent that can read your Outlook and your calendar at the same time can do that sorting for you and hand you a short list to act on. Your Operator.io agent does exactly that, reading and sending mail, managing folders, and creating or moving calendar events through Microsoft Graph, with the sign in and token refresh handled for you. It reaches Outlook through Composio, which you link once. One prompt turns that into a morning rundown plus an assistant you can hand a reply to in plain language.

How it works

You send the Outlook prompt, and the agent works your mail and calendar from the channel you already talk to it in.

• Each morning it reads you the day's calendar and a short triage of the overnight inbox, telling you which messages need a reply and which can wait.
• When you ask it to answer someone or send a message, it drafts the email first and shows it to you before anything goes out.
• It can put events on your calendar, move a meeting and let the attendees know, and find an open slot when you are trying to schedule something.

Sending always waits on you. The draft is a proposal you read and edit, and nothing leaves your account until you say go, so a busy morning never turns into an email you did not mean to send.

Composio calls the same Outlook mail API and Outlook calendar API that Microsoft documents for developers. Listing overnight messages maps to Graph endpoints like GET /me/messages with filters on received time. Creating a calendar event maps to POST /me/events. Moving a meeting and notifying attendees uses the event update and send endpoints. It wraps these as named tools the agent can invoke without you writing OAuth code or managing refresh tokens.

Microsoft's own developer channel explains what Graph is in a couple of minutes, the single API behind Outlook mail, calendar, and contacts, which is the surface Composio calls on your behalf here.

Connect Composio first

This prompt reaches your Outlook through Composio, so it needs to be connected to your agent first. Open the MCPs page in your Operator dashboard, add Composio, and sign in to your own account in the window that opens. The Composio setup guide walks through it, and the prompts library will offer to connect it inline the first time you send a prompt that needs it. Its free tier covers twenty thousand tool calls a month with no card, which is plenty for a daily inbox triage that might use a handful of calls each morning.

Outlook itself authorizes the first time the agent reaches for it. You will get a link to sign in to your Microsoft account and approve the access through the standard OAuth 2.0 authorization code flow that Microsoft Entra ID uses for all Graph integrations. After that, Composio holds the refresh token and renews it on schedule. The Outlook toolkit underneath covers mail, folders, attachments, and the calendar through Microsoft Graph. The toolkit page lists the specific actions available, including listing messages, creating drafts, sending mail, and managing calendar events.

Microsoft Graph works with both personal Microsoft accounts and work or school accounts on Microsoft 365. The API reads from primary mailboxes and shared mailboxes in Exchange Online. It does not reach in place archive mailboxes, so if your important threads live in an archive, move them back to the inbox or tell the agent to check a specific folder you keep active.

The prompt

This is the instruction the agent acts on:

Be my Outlook assistant, working my Outlook account through Composio. Each
morning, read me my calendar for the day and a short triage of the email
that came in overnight, telling me which messages need a reply and which can
wait. When I ask you to answer someone or send a message, draft it first and
show me before anything goes out. You can also put events on my calendar,
move a meeting and let the attendees know, and find an open slot when I am
trying to schedule something. Before you start, ask me what time to send the
morning rundown, whose email matters most to me, and confirm that you always
show me a draft before sending anything.

The same prompt is saved in the prompts library, so you can send it to your agent without retyping a word.

Using it day to day

The morning rundown sets up the rest. At the time you picked, the agent tells you what is on the calendar and which overnight emails it thinks need an answer, and you work straight down the list in the channel: reply to that one, push the third, archive the rest. When you say reply to the client about Thursday, it writes the draft in your voice from the thread, shows it to you, and sends it once you approve, so the actual sending is a quick yes rather than a switch into Outlook.

The calendar side is where the agent saves the back and forth. Ask it to move the 2pm to Friday and let everyone know, and it reschedules the event through Graph's event update API and sends the notification. That notification is a send in its own right. The moment the agent updates an event other people are on, Graph mails them the change, so a reschedule reaches your attendees as directly as a reply reaches the person you wrote it for.

The draft first habit you keep on mail is worth carrying over to meetings that involve other people, so have the agent tell you the new time and the note it plans to attach before it commits the move, and let it shuffle your own solo blocks without the ceremony.

Ask it to find a half hour with someone this week and it reads your calendar and proposes the slots. You tell it whose mail always matters, your manager, a key client, and it leads the triage with those instead of treating every sender the same.

If you use Outlook on the web, desktop, or mobile, the agent's changes show up there too, because everything goes through the same Graph mailbox. A draft the agent creates appears in your Drafts folder. An event it moves updates on every device synced to your account.

Why route Outlook through Composio

Wiring an agent into Microsoft Graph by hand means registering an application in Microsoft Entra ID, choosing the right Mail.Read, Mail.Send, and Calendars.ReadWrite scopes, building an OAuth redirect handler, and writing code to refresh tokens before they expire. Microsoft has been steering developers away from the older Exchange Web Services protocol toward Graph, and new integrations should start on Graph from the beginning.

Composio handles the Entra registration, scope management, and token refresh as part of its platform, and exposes the mail and calendar actions as tools your agent can call. Those scopes stay visible in the Composio connection settings, so if you want the agent reading and triaging before it ever sends, you can grant the read access first and add Mail.Send later, the same way you would ease into any account you hand over.

The same Composio connection also reaches other apps you might want in the same workflow. If you later ask the agent to post a meeting summary to Slack or file a follow up task in Linear, those toolkits connect through the same MCP setup without a separate OAuth flow for each one. The Outlook account you link sits under your own account, not a shared one, and you can disconnect it from the Composio dashboard whenever you want.

To set it up, connect Composio on the MCPs page, then open the prompts library and send the Outlook prompt. It asks when to send the morning rundown and whose mail comes first, and then the inbox triage and the calendar wrangling happen before you open Outlook yourself.