How to connect Outlook to OpenClaw

The ClawHub skill teaches OpenClaw about Outlook, but the calls run through the ClawLink plugin and your connected account. Make sure Outlook is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.

Reconnect Outlook from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.

Outlook tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Outlook call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.

Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.

This is a real limit of Microsoft's Search API, not a ClawLink restriction: Microsoft Search is built for Microsoft 365 organizations and personal mailboxes have no search index. It is the single most common Outlook error in our production logs. On a personal account, skip Search messages and use List messages or Query emails instead — both work on personal and work accounts, and both take filters (read status, sender, date, subject) that cover most search needs. On a work or school account, the search tool itself works.

Ask the agent to diagnose it:

Run clawlink_list_integrations and report Outlook's connection status. Do not retry the failed search. If the connected account is a personal @outlook.com or @hotmail.com address, switch that task to List messages or Query emails.

Graph returns this when the message, event, or folder no longer exists or never existed in the mailbox the agent is querying. The usual causes: the item was deleted or moved after the agent fetched its id, or the id came from a different mailbox (for example, a shared mailbox whose connection is separate from the agent's own). Have the agent re-run the list or search that produced the id and retry with a fresh one. The id alone cannot tell you which case it is — the list output can.

Ask the agent to diagnose it:

Re-run the list or search tool that produced the failing id, then retry the original call with an id from that fresh output. Report the error you get either way.

This is the placeholder-argument trap: the agent passed an empty id, "me", or an example id from documentation instead of a real one. "me" is a valid value for the user argument, not for message, event, or folder ids. Real ids look like AAMkADAwATNiZmY… and only come from list or search results. Ask the agent to run a list or search first, then retry with an id from that output. Most "malformed id" failures are this, not an account problem.

ClawLink's confirmation gate is what this error is. Destructive tools — Delete message, Move message, and the permanent-delete variants — return a preview and require explicit confirmation before any change reaches Microsoft. The agent should present the preview and wait for your approval; reconnecting the account does not bypass it, and the gate is on purpose. If the agent's runtime does not offer a confirm step, ask it to draft the call and approve it explicitly.

Microsoft Graph is throttling the mailbox, usually because the agent fired a burst of calls (for example, downloading every attachment in a folder at once). Wait a few seconds and retry; for bulk work, space the calls out or batch them — the batch tools accept up to 20 messages per call and reject anything larger ("List should have at most 20 items after validation").

Try reconnecting Outlook and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete.

Yes. ClawLink is the fastest way to connect OpenClaw to Outlook: link your Outlook account once in the browser and OpenClaw can call the Outlook API through 270 ready-made tools — no custom code or token handling.

Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Outlook skill from ClawHub, then you click Connect in the dashboard to authorize Outlook. OpenClaw calls the tools from the next message — no config files or API keys to manage.

About two minutes. Sign in, click Connect next to Outlook in the dashboard, authenticate, and OpenClaw can use it from the next chat message.

The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Outlook working from chat.

Yes. ClawLink connects personal Microsoft accounts and work or school (Microsoft 365) accounts through the same hosted OAuth flow, and the consent screen shows the same reach either way: read and send mail, manage calendar and contacts, and mailbox settings. One tool is the exception. The Search messages tool refuses personal accounts — Microsoft's Search API is built for Microsoft 365 organizations, not for personal mailboxes — so agents on a personal account should use List messages or Query emails instead, which work on both account types.

ClawLink gates destructive and write actions behind explicit confirmation. When the agent calls a tool like Delete message or Move message, the call returns a preview plus "requires explicit confirmation before execution" until you approve it. The approval is separate from Microsoft's own safety checks, and it applies to any action that permanently changes mailbox data, not just Outlook.

The ClawHub skill teaches OpenClaw about Outlook, but the calls run through the ClawLink plugin and your connected account. Make sure Outlook is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.