Claude for Small Business: 8 Connectors Explained (and Which to Wire First)

Every conversation I have with a small business owner looking at Claude lands on the same question within ten minutes: "Okay, but which of these should I actually connect first?" The Anthropic onboarding flow happily lets you wire all eight on day one. That's a mistake. Permissions inherit in ways you don't expect, you'll spend an hour debugging why Claude can't see a calendar it should see, and you'll lose the plot before you ever run your first workflow.

This is the post I wish existed before I'd set Cowork up for a dozen clients. What each connector does, what permissions to grant, the gotchas that bite once, and the order to wire them in.

The connector philosophy: why these 8

Anthropic didn't pick the 8 connectors at random. They mapped them to where small businesses actually do work. Two productivity stacks (Google Workspace and Microsoft 365). One comms layer (Slack). One CRM (HubSpot). One accounting tool (QuickBooks). One payments rail (PayPal). One design tool (Canva). One signature platform (DocuSign). Four functional zones — productivity, comms, revenue, money — covered by the smallest viable set of integrations. If your stack lives outside this list (say, Shopify-and-Zendesk), you'll have to work around it. We'll get to that.

1. Google Workspace

What it does. Reads and writes Gmail, Calendar, Docs, Sheets, and Drive. This is the connector that turns Claude from a blind assistant into one that can see what you're working on — read the thread before drafting the reply, read the calendar invite and attached docs before prepping for a meeting.

What permissions to grant. Read/write Gmail, read/write Calendar, read/write Docs and Sheets, read Drive. Skip Admin Console and domain-wide delegation scopes unless you specifically know you need them. You can always add scopes later.

Common use cases. Draft replies to inbound emails in your voice. Summarize long threads into a 3-line brief. Generate meeting prep notes from calendar invites plus CRM history. Turn discovery call notes into a follow-up email. Build a weekly status doc from your calendar and inbox activity.

Gotchas. If you have multiple Google accounts, Cowork connects to one. Pick the right one the first time — disconnecting and reconnecting under a different identity wipes workflow history tied to the first account. Only the paid Workspace tier supports the full feature set; individual Gmail accounts are limited.

2. Microsoft 365

What it does. The same surface area as Google Workspace, but for Outlook, Calendar, Word, Excel, OneDrive, and Teams. If your stack is Microsoft, this is your equivalent.

What permissions to grant. Mail.ReadWrite, Calendars.ReadWrite, Files.ReadWrite, and Sites.Read.All if you use SharePoint. Skip directory-level scopes unless you're an admin doing org-wide setup.

Common use cases. Same playbook as Google Workspace — draft Outlook replies, summarize threads, generate Word docs, pull data from Excel sheets, prep for Teams meetings.

Gotchas. Do not connect both Google Workspace and Microsoft 365 to the same Cowork instance. Cowork will let you, but you'll spend the rest of your life clarifying which calendar you mean. Also: if IT has conditional access policies, the OAuth handshake may fail silently — get IT involved before you start clicking.

3. Slack

What it does. Reads messages from channels you allow it into and posts to channels you specify. Cowork doesn't lurk by default — you whitelist which channels it can read and which it can post to.

What permissions to grant. Default OAuth scopes are fine. The decision that matters is which channels. Start with #general, your internal ops channel, and your leadership channel. Don't connect it to client-shared channels until you've watched how it behaves.

Common use cases. Post the weekly business pulse to your leadership channel. Drop a daily Monday morning brief. Alert the team when a high-value HubSpot lead lands. Summarize a long channel thread for someone catching up.

Gotchas. Slack rate limits apply — workflows that post dozens of messages in rapid succession get throttled. Cowork also can't currently respond in threads the way a human would; it posts top-level messages. Treat it as a broadcast tool, not a conversational one.

4. HubSpot

What it does. Reads contacts, deals, companies, and activity timelines. Updates contact properties and creates activities. This is the connector that turns Claude into something resembling an SDR or RevOps assistant.

What permissions to grant. CRM read/write at minimum. Skip marketing automation scopes unless you specifically want Cowork drafting marketing emails. Skip super admin.

Common use cases. Lead triage (score and route new inbound leads). Deal follow-up drafts based on last activity. Weekly pipeline health summary. Auto-enrich contact records from email signatures. Prep notes for a sales call by pulling the full deal history.

Gotchas. HubSpot's API rate limits are real and Cowork doesn't surface them cleanly. Batch large workflows or run them overnight. Free HubSpot accounts also have a more limited API surface — some paid-tier workflows silently underperform on free.

5. QuickBooks

What it does. Reads transactions, invoices, customers, vendors, and P&L data. Drafts invoices and reconciliation notes, but won't send invoices or move money without approval. This is the connector that finally lets a non-finance founder ask "where are we cash-wise?" and get a real answer.

What permissions to grant. Read access to all accounting data. Write access to invoices, bills, and reconciliations if you want drafts. Skip user management and company settings.

Common use cases. Daily or weekly cash flow snapshot. Invoice chasing drafts for anything 30+ days overdue. Month-end close prep checklist with reconciliation flags. Vendor payment timing analysis. Quarterly P&L narrative pulled from raw numbers.

Gotchas. This is the connector where permission inheritance matters most. Connect QuickBooks as the owner or admin, not as a restricted user. If your bookkeeper sets up the connection, Cowork inherits the bookkeeper's permissions — which usually means it can't see payroll, owner draws, or full P&L. Most owners don't realize this until they ask a question Cowork can't answer and assume the product is broken. It isn't. The permission scope is. Reconnect under the owner identity and you'll see everything.

6. PayPal

What it does. Reads payment history, payouts, transaction status, and customer records. Flags failed transactions, identifies duplicates, surfaces reconciliation gaps with QuickBooks.

What permissions to grant. Read transactions, read payouts, read disputes. Do not grant payment-initiation scopes unless you have a specific workflow that needs them. Less surface area is safer.

Common use cases. Daily reconciliation against QuickBooks. Failed payment alerts to Slack. Dispute summary briefs. Customer payment history lookup for a support inquiry.

Gotchas. PayPal's API only surfaces transactions tied to the connected account — sub-accounts don't roll up. Multiple PayPal accounts means multiple connections, treated as distinct sources. Webhook latency is also high; don't rely on Cowork for sub-minute payment alerts.

7. Canva

What it does. Reads your Canva brand kit and templates, generates new designs from text prompts using your brand assets. This is what keeps Cowork's visual output from looking generic.

What permissions to grant. Brand kit read, designs read/write, folders read. Skip team admin.

Common use cases. Auto-generate social posts in your brand colors and fonts. Produce on-brand quote graphics from blog posts. Generate ad creative variants for testing. Build out template instances for repeating use cases (event slides, monthly reports, etc.).

Gotchas. Canva Free accounts connect but lose brand kit and most templates — Cowork will produce generic output. Canva Pro at minimum if you want brand-consistent design. Design quality from text-only prompts is also uneven; expect to iterate 2-3 times.

8. DocuSign

What it does. Reads envelope status, sends documents for signature, tracks signature workflows, drafts follow-ups for envelopes sitting too long unsigned.

What permissions to grant. Envelope read/write, recipient read, template read. Skip account-level admin.

Common use cases. Daily summary of envelopes awaiting signature. Drafted follow-up emails for stalled contracts. New envelope creation from a template (with human approval before send). Signature completion alerts routed to Slack or HubSpot.

Gotchas. DocuSign uses separate sandbox and production environments, and Cowork has to be pointed at the right one. If your account was set up by a developer who tested in sandbox, OAuth may default there and you'll wonder why no real envelopes show up. Check the environment setting first.

Permission inheritance — the gotcha that catches everyone

This deserves its own section because it's the single biggest source of "Cowork is broken" tickets, and Cowork is almost never the thing that's broken.

Cowork inherits the exact permissions of whoever connected the tool. Not the user logged into Claude. Not the workspace admin. The specific account that clicked "Authorize" during OAuth.

If your bookkeeper connects QuickBooks, Cowork sees what your bookkeeper sees. If your sales manager connects HubSpot with rep-only permissions, Cowork can't see deals owned by other reps. If your designer connects Canva on a Free account, Cowork can't access your brand kit.

Plan connections by who has the right scope, not by who's at the keyboard during setup:

• QuickBooks: connect as the owner or accounting admin
• HubSpot: connect as a super admin or sales ops manager
• Google Workspace / Microsoft 365: connect as the account you want Cowork to read mail and calendar for (usually the owner)
• Slack: permissions matter less; any active user works
• Canva: connect from a Pro or Teams seat, not Free
• PayPal: connect from the master merchant account, not a sub-user
• DocuSign: connect from an account with template access

If you discover this three weeks in, disconnect, reconnect under the correct identity, and re-grant permissions. Cowork retains workflow history but rebuilds connector state.

What's NOT in the 8 (and what to do about it)

The 8 native connectors cover 70-80% of SMB stacks. The big gaps:

• Zendesk, Intercom, Freshdesk — forward tickets to a connected email address and let Cowork process them as threads.
• WooCommerce, Shopify — schedule daily order exports to Google Sheets; Cowork reads the sheet.
• Klaviyo, Omnisend, Mailchimp — weekly performance exports to Google Sheets.
• Stripe — Cowork's PayPal connector doesn't extend to Stripe. Bridge through Zapier → Google Sheet. Stripe is reportedly on the connector roadmap; no firm date.
• Industry-specific tools (Clio, Procore, etc.) — Zapier bridge pattern.

General workaround: get your tool's data into a Google Sheet or Excel file on a schedule, then point Cowork at that. Not as elegant as native, but it works.

The right first 3 to wire (by business type)

The default recommendation for most SMBs:

1. Google Workspace or Microsoft 365 (pick one — never both)
2. Slack for internal coordination
3. QuickBooks for finance visibility

This gives you draft-email-and-summarize-thread workflows on day one, internal broadcast on day two, and cash-flow visibility on day three. That's enough to justify the Team plan cost in week one.

Adjustments by business type:

• B2B services agency: swap QuickBooks for HubSpot as connector #3. Your sales pipeline is more valuable to surface than your books at this stage.
• DTC / e-commerce: swap Slack for PayPal (or Stripe via Zapier). Communications are less critical than transactional visibility.
• Professional services (lawyer, accountant, consultant): swap Slack for DocuSign. Contracts move your revenue more than internal coordination.
• Solo founder / pre-team: skip Slack entirely. Use Google + QuickBooks + HubSpot as your three.

Sequencing connectors 4 through 8

Over the first month, layer in the rest:

• Week 2: HubSpot (if not already), so lead triage workflows kick in
• Week 3: PayPal for reconciliation; Canva if you produce daily visual content
• Week 4: DocuSign as contracts come up

Each connector adds a new surface for things to break. Add one, run workflows for a week, learn its quirks, then add the next. You'll set up faster overall because you're not debugging four connectors at once.

How to disconnect and reconnect

Settings → Workspace → Connectors → click the tool → Disconnect. Then re-authorize from the right account. Plan on 5 minutes per tool, and warn your team — any in-flight workflows fail until reconnection completes. If you're disconnecting because a team member left, also revoke the OAuth grant from the source tool's admin panel. Cowork's disconnect doesn't automatically clean up the source-side grant.

FAQ

The bottom line

The 8 connectors aren't equally important and they're not all worth wiring on day one. Pick your productivity suite (Google or Microsoft, never both), add Slack, add QuickBooks, and you've got a working Cowork setup inside 90 minutes. Layer in HubSpot, PayPal, Canva, and DocuSign over the following month as your workflows pull on them.

The biggest mistake I see: connecting tools under the wrong identity and then assuming Cowork is broken when it can't see what you expect. Connect QuickBooks as the owner, HubSpot as an admin, Canva from a Pro seat — most of the "weird Cowork behavior" disappears.

For the long-form, screenshot-by-screenshot version, my Claude for Small Business setup guide walks through each connector. To skip DIY entirely, my done-for-you install handles all 8 connectors, the Business Brain, and your first set of workflows in 2 weeks. Details at /claude-for-small-business, or read up on what Cowork actually is if you're still deciding.