How to Connect Claude to Slack, Microsoft 365, and Google Workspace

Microsoft Copilot reached 41% adoption among M365 enterprise customers by Q1 2026, the fast uptake for any AI workplace tool. The pattern is clear: teams adopt AI faster when it's wired into the tools they already use, not sitting in a separate tab waiting for copy-pasted context.

Claude Cowork addresses this directly. Through Anthropic's connector system, Claude reads from Slack channels, Outlook inboxes, Google Drive folders, and calendar events without you copying anything. The Claude Connectors Directory now lists over 400 integrations across 30 categories, but the four that matter most for daily work are Slack, Microsoft 365, Google Workspace, and the Chrome extension.

These four aren't interchangeable. Each has a distinct permission model that determines what Claude can read, what it can write, and where it needs you to take the final action. Slack is the most interactive, with message drafting and posting. Microsoft 365 is entirely read-only. Google Workspace falls in between, with full read-write for Calendar and Drive but drafts-only for Gmail. Chrome takes a different approach entirely, giving Claude browser-level access to any website.

Understanding those boundaries before you enable anything saves you from hitting walls mid-workflow. The rest of this guide covers setup, capabilities, and the practical limits of each integration.

Claude's Slack integration gives you three distinct ways to interact, each suited to different work patterns.

Direct messages

Private conversations with @Claude inside Slack. Message Claude in a DM and it responds with the same capabilities you'd get on claude.ai, including web search and any other connectors you've enabled. Good for quick questions without context-switching.

The AI Assistant panel

Opens from Claude's icon in the Slack header. It creates a persistent sidebar conversation accessible from anywhere in the workspace, whether you're in channels, DMs, or threads.

Thread mentions

@Mention Claude in any thread and it reads the conversation history, then responds in context. It can summarize a discussion, answer a question about something that was said, or draft a follow-up. This is where Claude becomes most useful for teams.

Interactive Apps: Writing Back to Slack

In January 2026, Anthropic launched Interactive Apps built on the Model Context Protocol. For Slack, this means Claude can draft messages, preview formatting, and post them to channels or DMs from the Claude interface. The safety guardrail: Claude always asks for your explicit approval before sending. You review the draft and confirm before anything goes out.

Admin Setup

For Team and Enterprise plans, an owner enables the Slack connector in Organization settings before individual members can connect. After that, each user finds Claude in the Slack App Marketplace, clicks Connect Account, selects their Claude organization, and authorizes access.

Once connected, Claude can search workspace channels, DMs, and shared files for context. Team and Enterprise users also get Claude Code routing, which sends coding tasks mentioned in Slack to Claude Code on the web.

Data Separation Slack conversations don't appear in your claude.ai history, and Claude web chats don't show up in Slack. If you disconnect the integration, conversations auto-delete from Claude within 30 days. Slack's own retention policies apply separately.

Plan requirements: The Claude Slack app requires a paid Slack plan. The Slack connector on Claude's side is available on Pro, Max, Team, and Enterprise plans.

The Microsoft 365 connector covers the widest range of data sources but is the most restricted in what Claude can do with them. Every permission is read-only.

Once connected, Claude can pull from five Microsoft 365 services:

• Outlook: search and read email messages, metadata, and shared mailboxes
• OneDrive and SharePoint: read files and documents across personal and team storage
• Calendar: view events and shared calendars
• Teams: read chat messages and channel conversations
• Meetings: access transcripts, recordings, and AI-generated meeting insights

This makes the connector strong for research and analysis. Ask Claude to find a contract mentioned in last week's emails, cross-reference it with a SharePoint document, and summarize the key terms. It handles all of that from a single conversation.

What Claude cannot do in Microsoft 365: send emails, create calendar events, modify SharePoint files, change Teams settings, or take any write action. If you need an email drafted, Claude writes the text and you paste it into Outlook yourself.

The connector is available on all Claude plans, including Free. The requirement: a Microsoft Entra tenant tied to a Microsoft Business plan. Personal Microsoft accounts don't work.

Setup for Teams

For Team and Enterprise plans, setup is two-step. First, an organization owner enables the connector in Claude's admin settings. Then a Microsoft Entra Global Administrator grants one-time consent, either through direct Claude authentication or by manually adding service principals in Entra.

Claude uses delegated permissions. It can only access data that each individual user already has permission to view in Microsoft 365. If you can't open a SharePoint folder, neither can Claude. Admins can further restrict access by limiting which users can authenticate and selectively revoking specific permissions in Microsoft Entra.

Give Your Claude Outputs a Persistent Home

Store, index, and share everything Claude creates across your integrations. 50GB free, no credit card, and an MCP endpoint your agents can call directly.

Sign Up Free

Google Workspace connectors give Claude the broadest mix of read and write access among the three major productivity suites. Three services connect independently: Gmail, Google Drive, and Google Calendar.

Gmail

Claude can search and read emails, access metadata, manage labels, and list saved drafts. On the write side, Claude can create new drafts but cannot send them. You review and send manually. One notable gap: attachment content isn't accessible through the Gmail connector. Claude sees file names and sizes but can't read the actual attached files. If you need Claude to analyze an attachment, access it through Google Drive or upload it directly.

Google Drive

This is the most capable connector in the Google Workspace set. Claude can search across documents, read content from Sheets, Slides, PDFs, images, and Microsoft Office files stored in Drive. It can also upload files, create folders, and save generated content directly to Drive. Text extraction only, though. Images embedded inside Google Docs aren't processed.

Google Calendar

Full read-write access. Claude can view events and shared calendars, create new events, update or delete existing ones, find mutual availability across team members, manage attendees, and set up recurring meetings. This is useful for scheduling workflows where you describe what you need and Claude handles the calendar mechanics.

Setup and Permissions

Google Workspace connectors are available across all Claude tiers. For Team and Enterprise plans, an owner must enable connectors at the organization level before individual users can authenticate. Permissions can be scoped to specific Drive folders, Gmail labels, or calendars.

For organizations using Google Workspace administrative controls, you may need to adjust trust settings to allow Claude's access. The Claude Help Center has configuration guidance for Google Workspace admins.

The Chrome extension, part of Claude's Cowork approach to workplace collaboration, takes a different path from API-based connectors. Instead of connecting to a specific service, Claude for Chrome gives the AI direct access to whatever you're looking at in the browser. It can read page content, click buttons, fill forms, navigate between pages, and manage multiple tabs.

This fills the gap for tools without dedicated connectors. Internal dashboards, niche SaaS apps, websites not in the connector directory: the Chrome extension handles them all.

Claude for Chrome runs in a side panel while you browse. Core capabilities include:

• Navigating and interacting with any website through clicking, typing, and scrolling
• Managing multiple browser tabs with drag-and-drop grouping
• Sharing visual context through screenshots and image uploads
• Reading browser console logs for debugging
• Recording and saving browser workflows as reusable shortcuts
• Running scheduled automations on a daily, weekly, or monthly basis

An "Ask before acting" mode gives you step-by-step approval control. Claude proposes each action, you confirm, then it executes. This matters when working with sensitive systems or unfamiliar pages.

Claude for Chrome is in beta and available to Pro, Max, Team, and Enterprise subscribers. Model access varies by plan: Pro users get Haiku 4.5, while Max, Team, and Enterprise users can choose between Opus 4.7, Sonnet 4.6, or Haiku 4.5. Team and Enterprise admins can restrict which sites Claude can access using allowlists and blocklists.

When should you use Chrome vs. connectors? Use connectors when they exist for your target service. They're faster, respect API-level permissions, and don't require a browser window. Use Chrome when no connector exists or when the task involves multi-step browser workflows across different sites.

Claude's integration system becomes most useful when you combine multiple connectors in a single conversation. Claude maintains context across all connected services, so each step in a workflow builds on what came before.

A practical example: ask Claude to find all emails about a project in Gmail, pull the latest project documents from Google Drive, then draft a status update for posting to Slack. Claude handles the context switching between services while you stay in one conversation.

Read vs. Write Capabilities at a Glance

The permission split across integrations shapes what workflows are possible:

• Full read-write: Google Calendar, Google Drive, Slack (with Interactive Apps)
• Read plus draft: Gmail (reads email, creates drafts you send manually)
• Read-only: Microsoft 365 (all five services)
• Interactive: Chrome (reads and acts on any website)

Any workflow that needs to write back to Microsoft 365 hits a boundary. Claude can analyze your Teams conversations and SharePoint documents, but output needs to land somewhere else. You can paste it manually, save it to Google Drive, or direct it to a persistent workspace.

Persistent Storage for AI Outputs

When Claude generates content from multiple integrations, those outputs don't persist across chat sessions unless you save them. Fast.io provides a workspace layer where AI-generated content gets stored, indexed, and shared with your team. Enable Intelligence Mode and every file Claude saves there becomes searchable by meaning, not just filename. Agents and humans work in the same workspace, so handoff is a permission change rather than a file transfer. The free plan includes 50GB of storage and 5,000 monthly credits with no credit card required.

For teams running Claude alongside other AI tools, Fast.io's MCP server provides a single endpoint for workspace operations. Any agent that speaks MCP can read, write, and query files in the same workspaces your team uses through the browser.