# How to connect Outlook to Grok Bot (no API keys) > Connect Outlook to Grok Bot with ClawLink in one click — 270 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup. Web version: https://claw-link.dev/grokbot/outlook Grok Bot runs on its own cloud computer, so most Outlook guides send you to register an OAuth app and paste keys into a sandbox that resets. ClawLink gives Grok Bot a more practical Outlook setup: it runs one CLI command, you approve once in the browser, and Grok Bot can call real Outlook actions from chat with no auth, token refresh, or tool wiring to build yourself. **Start here — paste this into Grok Bot to set up ClawLink:** > Set up ClawLink for me and tell me when it's ready. > 1. Pair this machine. It prints an approval link, so show me the link and stop, don't wait: `npx -y @useclawlink/cli login` > 2. I'll approve it in my browser, then reply "approved". > 3. When I say approved, connect the app: `npx -y @useclawlink/cli connect outlook` > 4. Then run `npx -y @useclawlink/cli whoami` and tell me whether ClawLink is ready. ## Setup It takes three steps to connect Grok Bot to Outlook. 1. **Pair from the terminal** — ask Grok Bot to run `npx -y @useclawlink/cli login` and approve the link it prints. 2. **Connect Outlook** — `npx -y @useclawlink/cli connect outlook`, then approve in the browser. 3. **Use it from chat** — ask Grok Bot in plain English. **The same CLI works from any agent with shell access:** ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect outlook # connect Outlook (browser OAuth) npx -y @useclawlink/cli actions outlook # list available actions npx -y @useclawlink/cli run outlook --input '' # execute (add --confirm for writes) ``` ### Install by command The prompt above does all of this. By hand, it is two commands Grok Bot runs in its own terminal, and one browser approval: ```bash npx -y @useclawlink/cli login # prints an approval link, approve it in your browser npx -y @useclawlink/cli connect outlook ``` Pair once and it sticks: the key is written to ~/.clawlink/credentials.json inside Grok Bot's sandbox, so it survives between sessions. Prefer native tools over shell commands? Add `https://claw-link.dev/api/mcp` as a custom connector at grok.com/connectors and approve the ClawLink sign-in. Same account, no CLI. Verify the connection by asking Grok Bot: > Use Outlook to calendar create event and walk me through the result in plain English. ### Using a different agent? The CLI above is not specific to Grok Bot. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account the same way: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Outlook is connected in the dashboard, that agent calls the same 270 Outlook tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Outlook MCP for Grok Bot Looking for a Outlook MCP server for Grok Bot? ClawLink connects Outlook to Grok Bot and exposes 270 Outlook tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using a different agent? The [OpenClaw Outlook integration](https://claw-link.dev/openclaw/outlook) and the [Hermes Outlook integration](https://claw-link.dev/hermes/outlook) connect the same ClawLink account the same way. ## What the Grok Bot Outlook integration can do 270 Outlook tools are ready for Grok Bot once the account is connected. The 30 below are the ones people reach for most; your agent can call all 270. ### 30 of 270 Outlook tools for Grok Bot | Tool | What it does | |---|---| | **Calendar create event** `outlook_calendar_create_event` | Create a new Outlook calendar event | | **Create contact** `outlook_create_contact` | Create a new Outlook contact | | **Create draft** `outlook_create_draft` | Create a new draft Outlook email | | **Get message** `outlook_get_message` | Get a specific Outlook message | | **Get profile** `outlook_get_profile` | Get the connected Outlook user profile | | **List calendars** `outlook_list_calendars` | List Outlook calendars | | **List mail folders** `outlook_list_mail_folders` | List Outlook mail folders | | **List messages** `outlook_list_messages` | List Outlook messages | | **List user contacts** `outlook_list_user_contacts` | List Outlook contacts | | **Query emails** `outlook_query_emails` | Query Outlook emails with filters | | **Reply email** `outlook_reply_email` | Reply directly to an Outlook message | | **Search messages** `outlook_search_messages` | Search Outlook messages | | **Send email** `outlook_send_email` | Send a new Outlook email | | **Download outlook attachment** `outlook_download_outlook_attachment` | Downloads a specific file attachment from an email message in a Microsoft Outlook mailbox; the | | **Find meeting times** `outlook_find_meeting_times` | Suggests meeting times based on organizer and attendee availability, time constraints, and | | **Get calendar event** `outlook_get_calendar_event` | Retrieve a specific event from a specified calendar | | **Get calendar event attachment** `outlook_get_calendar_event_attachment` | Retrieve a specific attachment from an event within a calendar | | **Get calendar from event** `outlook_get_calendar_from_event` | Retrieve the parent calendar that contains a specific event | | **Get calendar from group** `outlook_get_calendar_from_group` | Retrieve a specific calendar from a calendar group in Microsoft Outlook | | **Get calendar group** `outlook_get_calendar_group` | Retrieve the properties and relationships of a calendar group object | | **Get calendar group calendar event extension** `outlook_get_calendar_group_calendar_event_extension` | Retrieve an open extension from a calendar event within a specific calendar group and calendar | | **Get calendar group schedule** `outlook_get_calendar_group_schedule` | Retrieve free/busy schedule information for a specific user's calendar within a calendar group | | **Get calendar permission** `outlook_get_calendar_permission` | Retrieve a specific calendar permission for a user's calendar | | **Get calendar permission from calendar** `outlook_get_calendar_permission_from_calendar` | Retrieve a specific calendar permission from a user's calendar | | **Get calendar schedule** `outlook_get_calendar_schedule` | Get free/busy schedule information for users, distribution lists, or resources | | **Get calendar view** `outlook_get_calendar_view` | Get events ACTIVE during a time window (includes multi-day events) | | **Get child folder message** `outlook_get_child_folder_message` | Retrieve a specific email message from a child mail folder | | **Get child folder message content** `outlook_get_child_folder_message_content` | Get the MIME content of a message from a child mail folder | | **Get child mail folder** `outlook_get_child_mail_folder` | Retrieve a specific child mail folder from a parent mail folder | | **Get contact extension** `outlook_get_contact_extension` | Retrieve an open extension from a contact in Microsoft Graph | ## Example prompts **Calendar Create Event** > Use Outlook to calendar create event and walk me through the result in plain English. **Create Contact** > Create it in Outlook for me, then confirm the important fields before you finish. **Create Draft** > Create it in Outlook for me, then confirm the important fields before you finish. **Get Message** > Pull the relevant data from Outlook, summarize it in plain English, and point out anything that needs attention. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for Grok Bot. That is fine if you want to build and maintain the integration yourself. Most teams just want Outlook working from chat. | | Manual | ClawLink | |---|---|---| | **Connection flow** | Register a Outlook app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect Outlook through the hosted browser flow and ClawLink keeps the token lifecycle out of your app code. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Outlook. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. | | **Agent usability** | You still need to expose the right Outlook actions to the runtime in a format your agent can reliably use. | 270 tools for Outlook are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Outlook to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for Grok Bot users instead. You install the plugin once, connect Outlook in the browser, and the 270 tools above work from chat. There is no SDK, no config file, and no API key handling. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### Grok Bot says it cannot add ClawLink as an MCP server Grok Bot only attaches MCP servers that are reachable over the public internet, so a local stdio server is refused. You do not need one. Ask Grok Bot to run `npx -y @useclawlink/cli login` in its terminal instead. The CLI is a shell command, not an MCP server. If you would rather have native tools, add `https://claw-link.dev/api/mcp` as a custom connector at grok.com/connectors and approve the ClawLink sign-in. ### Connection succeeds but no tools appear Reconnect Outlook from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded. ### "Tool schema not loaded yet" error when calling Outlook tools 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. ### Outlook returns 403 or "permission denied" on one action while others work 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. ### OAuth finished in the browser but the account is still missing 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. ### Is there a Grok Bot Outlook integration? Yes. ClawLink is the fastest way to connect Grok Bot to Outlook: link your Outlook account once in the browser and Grok Bot can call the Outlook API through 270 ready-made tools — no custom code or token handling. ### How do I connect Outlook to Grok Bot with ClawLink? Ask Grok Bot to run `npx -y @useclawlink/cli login` in its terminal and approve the link it prints, then `npx -y @useclawlink/cli connect outlook` to authorize Outlook. Grok Bot calls the tools from the next message, and the pairing persists in its sandbox, so this is a one-time step: no config files or API keys to manage. ### How long does it take to connect Outlook to Grok Bot? About two minutes. Sign in, click Connect next to Outlook in the dashboard, authenticate, and Grok Bot can use it from the next chat message. ### Why use ClawLink instead of wiring Outlook up myself? The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for Grok Bot. That is fine if you want to build and maintain the integration yourself. Most teams just want Outlook working from chat. ### Grok Bot says it cannot add ClawLink as an MCP server Grok Bot only attaches MCP servers that are reachable over the public internet, so a local stdio server is refused. You do not need one. Ask Grok Bot to run `npx -y @useclawlink/cli login` in its terminal instead. The CLI is a shell command, not an MCP server. If you would rather have native tools, add `https://claw-link.dev/api/mcp` as a custom connector at grok.com/connectors and approve the ClawLink sign-in. ## Related - [Grok Bot Microsoft Teams integration](https://claw-link.dev/grokbot/microsoft-teams) — Chat, meetings, and team collaboration - [SharePoint](https://claw-link.dev/grokbot/sharepoint) — Browse sites, lists, and files in SharePoint - [Grok Bot Microsoft OneDrive integration](https://claw-link.dev/grokbot/onedrive) — Browse, search, and manage OneDrive files