Claude Cowork works best when it's connected to the tools your team already uses. Out of the box, it can read and write files on your local machine. But once you plug in Slack, Notion, and Google Workspace, it stops being a chatbot and starts doing real work across your existing tools.

Anthropic's February 2026 update brought 13 plugin integrations to Cowork. That's a lot to configure, and most teams we work with aren't sure where to start. This guide walks through the three integrations that deliver the most value for most businesses: Slack, Notion, and Google Workspace. We'll cover what each integration actually does, how to set it up, and the workflows that make the setup worth the effort.

If you haven't used Claude Cowork before, start with our complete guide to Claude Cowork first. This article assumes you have an active Claude Team or Enterprise subscription.

What Integrations Are Available?

Before diving into the big three, here's a quick look at everything that's available. Claude Cowork currently supports:

Communication: Slack
Knowledge Management: Notion
Productivity Suite: Google Workspace (Docs, Sheets, Drive, Calendar, Gmail)
Project Management: Linear, Asana
Development: GitHub
Design: Canva, Figma
Finance: FactSet, S&P Global
Document Management: DocuSign, Box

Each integration uses Anthropic's MCP (Model Context Protocol) to create a secure, permissioned connection. You control exactly what Cowork can read, write, and modify in each tool.

The setup pattern is similar across all integrations: you authorize the connection through Claude Desktop's settings panel, configure permissions, and then reference the tool in your Cowork prompts. But the details vary, and getting those details right is the difference between a smooth experience and a frustrating one.

Slack Integration

Claude Cowork Slack integration setup

Slack is where most teams should start. It's the integration that pays off fastest because it connects Cowork to your team's conversations. Once connected, Cowork can read channel history, post messages, send DMs, and react to mentions.

What Cowork Can Do in Slack

Here's the full list of Slack capabilities once the integration is active:

Read channel history. Cowork can scan messages across any channel it has access to, including threads. This powers features like morning briefings and overnight summaries.
Post messages. Cowork can write to channels, either on demand or on a schedule. Useful for standup reminders, weekly summaries, or automated status updates.
Send and receive DMs. You can message Cowork directly in Slack. It responds using the same model (Claude Opus 4.6) that powers the desktop app.
Search workspace history. Cowork can search across your Slack workspace for specific topics, people, or timeframes. This makes it great for pulling context before meetings.
Respond to mentions. Tag Cowork in a channel and it will respond contextually, factoring in the conversation thread.
Create canvases. Cowork can create and write to Slack canvases, which is useful for shared reference documents that live inside Slack.

Setup Steps

Open Claude Desktop and go to Settings, then Integrations.
Click "Connect" next to Slack. This opens an OAuth authorization flow in your browser.
Sign in to your Slack workspace and approve the requested permissions. Cowork will ask for access to read messages, post messages, and search. You can modify these later.
Select which channels Cowork can access. By default, it can access public channels. For private channels, you need to invite @Claude to each one manually within Slack.
Test the connection by opening a Cowork session and typing: "Search Slack for the most recent messages in #general and summarize them."

The whole process takes under 5 minutes. If your Slack workspace uses SSO or has admin-approval requirements for third-party apps, you may need a workspace admin to approve the Claude app first.

Permission Best Practices

Don't give Cowork access to everything. Here's how we recommend scoping it:

Start narrow. Connect 3-5 channels that Cowork will actively use. Common starting points are #general, #team-updates, and one project-specific channel. You can always add more later.

Skip sensitive channels. If you have channels for HR conversations, compensation discussions, or confidential client work, leave them disconnected. Even though Cowork doesn't store or train on your data, limiting exposure is good practice.

Use read-only where possible. For channels where Cowork should only gather information (like a #leadership channel), grant read access only. Reserve write access for channels where Cowork will actively post.

Set up a dedicated Cowork channel. Many of our clients create a #cowork-updates channel where Cowork posts its automated outputs. This keeps AI-generated messages separate from human conversation and makes it easy to review what Cowork has been doing.

Example Workflows

Morning briefing in #general. Schedule a task to run at 7:30 AM. Cowork reads overnight activity across your key channels, checks your Google Calendar for the day's meetings, and posts a summary to your #cowork-updates channel or DMs you directly. Setup takes about 10 minutes, and it saves 30-40 minutes of morning catch-up every day.

Customer alert triage in #support. Connect your #support or #customer-success channel. Set Cowork to monitor for messages containing keywords like "urgent," "down," "broken," or "escalation." When it detects one, it pulls the customer's recent history from Notion (if your CRM data lives there) and posts a context brief to the support thread. Your team gets immediate context without digging through multiple systems.

Notion Integration

Claude Cowork Notion integration workflow

Notion is the second integration we recommend connecting. Slack handles your conversations. Notion holds your documentation. Connecting both to Cowork means information flows between them automatically.

What Cowork Does with Notion

Read pages and databases. Cowork can navigate your Notion workspace, read page content, and query databases. It understands Notion's page hierarchy, so it can find information across nested structures.
Create and edit pages. Cowork can write new Notion pages, add content to existing ones, and update database entries. This is how it automates documentation tasks.
Query database properties. If you use Notion databases for CRM data, project tracking, or content calendars, Cowork can filter and sort by properties just like you would in Notion's UI.
Cross-reference documents. Cowork can pull information from multiple Notion pages and synthesize it into a single output. This is powerful for reporting and analysis.
Auto-organize content. Cowork can move pages between databases, apply tags, and update statuses based on rules you define.

Setup Steps

In Claude Desktop, go to Settings, then Integrations, and click "Connect" next to Notion.
Authorize the connection through Notion's OAuth flow. You'll need to select which pages and databases Claude can access.
Choose your access scope. Notion lets you grant access at the page level. We recommend starting with one or two workspaces or top-level pages rather than your entire Notion account.
Verify the connection by asking Cowork to list the pages it can see: "Show me all the Notion pages you have access to."
Test a write operation. Ask Cowork to create a test page: "Create a new page in [your workspace] called 'Cowork Test Page' with a brief description." Confirm it appears in Notion, then delete it.

Structuring Notion for AI

The way your Notion workspace is organized has a big impact on how well Cowork works with it. A few structural decisions make things go much smoother.

Use descriptive page titles. "Q1 Marketing Plan" is much better than "Marketing Stuff" or "Untitled." Cowork uses titles to navigate, so clear names mean faster, more accurate results.

Keep databases clean. Every database should have a clear purpose and consistent properties. If your project tracker has 30 columns and half of them are empty, Cowork will struggle to understand what's relevant. Trim unused properties before connecting.

Create a Cowork-specific workspace. A top-level page called "Cowork Outputs" gives you a clean space where Cowork can create meeting notes, weekly summaries, research documents, and reports. This prevents AI-generated content from cluttering your human-managed workspace.

Use templates for recurring outputs. If Cowork will generate weekly reports, create a Notion template with the right structure. Then reference it in your prompts: "Create this week's report using the Weekly Summary template in the Cowork Outputs workspace."

Example Workflows

Meeting notes to Notion. After a meeting, share the transcript or your rough notes with Cowork. Prompt: "Extract action items, key decisions, and discussion topics from these meeting notes. Create a new page in the Meetings database with today's date and the attendee list as properties. Post a summary to #team-updates in Slack." This turns a pile of raw notes into a structured, searchable record in under a minute.

Weekly summary pages. Schedule a Friday afternoon task. Cowork reviews the week's Slack activity, completed Linear or Asana tasks, and any Notion pages modified during the week. It creates a "Week of [date]" summary page in Notion with sections for accomplishments, open items, and priorities for next week. Your Monday morning planning session starts with context instead of scrambling.

Google Workspace Integration

Google Workspace is the broadest integration because it covers four distinct products: Gmail, Google Calendar, Google Drive, and Google Docs/Sheets. Each one connects to Cowork independently, so you can enable just the pieces you need.

Gmail: Email Triage and Drafting

What it does: Cowork reads your inbox, categorizes messages by urgency, drafts replies, and saves them as Gmail drafts for your review. It never sends emails on its own.

Setup:

Go to Settings, Integrations, and connect Google Workspace.
Sign in with your Google account and grant Gmail permissions (read and compose).
Test with: "Check my inbox for unread emails from today and categorize them by priority."

Best workflows: Schedule an email triage every 2 hours. Cowork categorizes incoming mail as urgent, can-wait, delegate, or FYI. For urgent items, it drafts a reply. For delegate items, it suggests who should handle it. You review the drafts in Gmail, tweak if needed, and send. This saves 30-45 minutes per day for anyone processing more than 50 emails.

Google Calendar: Meeting Prep and Scheduling

What it does: Cowork reads your calendar events, checks for scheduling conflicts, generates pre-meeting briefs, and can help find available time slots. It doesn't create or modify events directly for security reasons.

Setup:

During the Google Workspace connection, grant Calendar read access.
Test with: "What meetings do I have tomorrow? Flag any that overlap or are back-to-back."

Best workflows: Set a pre-meeting trigger 15 minutes before each meeting. Cowork checks who's attending, searches Slack and Notion for recent interactions with those people, and creates a one-page brief. You walk into every meeting with full context without doing any prep work.

Google Drive: Document Search and Summarization

What it does: Cowork can search your Drive, read documents, and summarize content from files stored there. It works with Google Docs, Sheets, PDFs, and most common file formats.

Setup:

Grant Drive read access during the Google Workspace connection.
For write access (creating new documents), enable it separately in the permissions panel.
Test with: "Find the most recently modified document in my Drive that contains 'Q1 budget'."

Best workflows: Research tasks become much faster. Instead of manually searching Drive for the right document, ask Cowork: "Find all documents related to the Anderson project, summarize the key findings, and identify any open questions." Cowork searches, reads, and synthesizes across multiple documents in seconds.

Other Integrations Worth Knowing

Beyond the big three, Claude Cowork supports several other integrations that are valuable for specific teams.

Linear and Asana. Cowork can read tasks, update statuses, create new issues, and generate sprint reports. Development and product teams use these to automate standups and sprint retrospectives.

GitHub. Cowork can read repositories, review pull requests, search code, and generate summaries of recent changes. Useful for engineering leads who want a daily digest of what shipped.

Figma and Canva. Cowork can access design files and assets. Most practical for generating descriptions of design work or pulling assets into presentations.

DocuSign and Box. Document workflow integrations that help with contract management and file organization.

Each of these follows the same setup pattern: connect through Settings, authorize via OAuth, scope permissions, and test.

Combining Integrations: Multi-Tool Workflows

Claude Cowork multi-tool integration architecture

Claude Cowork's integration system gets more useful when you combine multiple tools in a single workflow. Cowork can chain actions across integrations within a single task, and it handles the data flow between tools automatically.

Here are three multi-tool workflows our clients use regularly:

Customer Escalation Pipeline

Trigger: A message in #support Slack channel contains "escalation" or "P1."

Cowork's actions:

Reads the Slack thread for full context.
Searches Notion's customer database for the account details.
Checks Google Calendar for the account manager's availability.
Creates a Notion page with the escalation summary, customer history, and suggested response.
Posts a brief to #escalations in Slack with a link to the Notion page and the account manager's next available slot.

Result: A 15-minute manual process compressed into about 30 seconds.

Weekly Business Review Automation

Trigger: Scheduled task, Fridays at 4 PM.

Cowork's actions:

Pulls completed tasks from Linear for the week.
Searches Slack for key announcements and decisions.
Reads relevant Google Docs for project updates.
Creates a full weekly review page in Notion.
Posts a summary with a link to the Notion page in #leadership on Slack.

Result: Your weekly review document writes itself. Leadership gets a consistent, thorough update every week without anyone spending an hour assembling it.

New Hire Onboarding Brief

Trigger: On demand, when a new team member starts.

Cowork's actions:

Searches Notion for the team handbook, org chart, and role-specific documentation.
Pulls the new hire's first week calendar from Google Calendar.
Identifies key Slack channels for their role.
Creates a personalized onboarding page in Notion with links, contacts, and a day-by-day plan.
Sends a welcome DM in Slack with a link to the onboarding page.

Result: Every new hire gets an onboarding page built around their role instead of a generic checklist.

Common Setup Issues and Troubleshooting

After deploying integrations across dozens of teams, here are the issues we see most often and how to fix them.

"Claude can't see my Slack channel." Private channels require an explicit invite. Go to the channel in Slack, type /invite @Claude, and try again. For shared channels between workspaces, the integration only covers your primary workspace.

"Notion pages aren't showing up." When you authorized the Notion connection, you selected specific pages. If you've created new pages since then, they won't be visible. Go to Settings, Integrations, Notion, and click "Update Access" to add new pages.

"Google Calendar shows no events." Check that you granted Calendar read access during setup. Some Google Workspace admin policies restrict third-party app access to calendar data. If you're on a managed Google account, your IT admin may need to allowlist the Claude app.

"Cowork posted to the wrong Slack channel." Be specific in your prompts. "Post to Slack" is ambiguous. "Post to #team-updates in Slack" is not. If Cowork keeps defaulting to the wrong channel, set a default in your scheduled task prompt.

"Integration disconnected after a few days." OAuth tokens expire. Claude Desktop should handle refresh tokens automatically, but if an integration drops, reconnect it from the Settings panel. This usually takes 30 seconds.

"Cowork is slow when reading large Notion databases." Databases with more than 1,000 entries can take a few seconds to query. Use filters in your prompts: "Search the customer database for entries where Status is Active and Region is Ontario" is much faster than "Read the entire customer database."

When to Get Professional Help

Most teams can set up the basic integrations on their own by following the steps above. But there are situations where working with someone who's done it before saves real time.

Complex permission structures. If your organization has strict data access policies, configuring the right permission scopes across multiple integrations requires careful planning. One wrong setting can either block Cowork from doing its job or give it access to data it shouldn't see.

Multi-tool workflow design. Building the individual connections is straightforward. Designing workflows that chain multiple integrations together, like the escalation pipeline above, requires understanding how data flows between tools and where handoffs can break.

Enterprise rollouts. Deploying Cowork integrations for a team of 5 is different from deploying for a team of 50. Larger teams need consistent configuration, training materials, and governance policies.

Custom use cases. If your workflow requires connecting Cowork to a tool that isn't in the standard integration list, MCP server configuration can extend its capabilities. This is technical work that requires familiarity with Anthropic's protocol.

We've deployed Claude Cowork integrations for businesses across Toronto and beyond. If you want help getting your setup right the first time, book a free 30-minute consultation and we'll map out the right integration architecture for your team.