Email & Calendar — Gmail, Outlook & Google Calendar
Giving an Agent an Inbox and a Calendar
Langoedge agents can work directly inside Google Workspace (Gmail, Google Calendar) and Microsoft 365 (Outlook mail and calendar) — searching messages, drafting and sending correspondence, checking free/busy time, and booking meetings.
These apps are reached through an MCP Connector, not through built-in tools.
Prerequisite — an active account connection. Connect the Google Workspace or Microsoft 365 account on the Connect page before your agent can touch mail or calendar. Without it, the connector cannot list any tools and any step relying on it will fail at run time.
Setting It Up
Connect the account
Add an MCP Connector
Scope it — this one matters
What These Apps Let an Agent Do
Exact tool names come from the provider, but the capabilities are stable:
Email (Gmail / Outlook)
- Search the inbox — find messages by sender, subject, content, or the provider's own query syntax.
- Draft — compose a message and leave it in Drafts for a human to review and send.
- Send — dispatch immediately.
- Manage labels and folders — organise threads into categories.
- Handle attachments — read and download files attached to a message.
- Delete — remove messages. Withhold this one unless you have a specific reason not to.
Calendar (Google Calendar / Outlook)
- Check availability — read free/busy across a date range so the agent can offer real open slots.
- Create events — schedule a meeting and invite attendees.
- Read and update events — inspect or amend existing bookings.
Human-in-the-Loop Email
The single most useful pattern here: expose the draft tool and withhold the send tool. The agent composes; a person reviews and sends. This is a configuration-level guarantee rather than a prompt-level request, so no amount of unusual conversation can talk the agent into emailing a customer something you haven't seen.
For workflows where sending automatically is genuinely wanted, pair it with a Quality Gate — a conditional edge that routes the drafted message past a supervisor LLM (or a human approval step) before the send tool is reachable.
Security
All email and calendar integrations authorise over OAuth 2.0. Credentials are held by the connect layer and referenced by an opaque account id — Langoedge stores the link, not your password, and the LLM never sees a token. Access is scoped to the graph owner's connected accounts, so a published graph sends mail as its owner, not as whoever triggered it.