Which Claude Connectors Should a Small Business Switch On?

Coding Liquids tutorial cover featuring Sagnik Bhattacharya for Which Claude Connectors Should a Small Business Switch On?
Coding Liquids tutorial cover featuring Sagnik Bhattacharya for Which Claude Connectors Should a Small Business Switch On?

For most small businesses, nine Claude connectors are worth switching on: Gmail, Google Calendar and Google Drive (or Microsoft 365), an accounts connector (Xero reads only; QuickBooks can also write), HubSpot, Stripe, Jobber, Granola and Docusign. Each sees only what your own login can see in that app, and every write tool can be set to Needs approval.

The Complete Excel Course with AI Integration

From formulas and pivot tables to Power Query, DAX, VBA and AI with Copilot, ChatGPT and Claude — hands-on from the first lesson.

By Sagnik Bhattacharya and Virginia Thorn, Primetime Emmy Award winner

Buy now

The privacy question is less "can Claude see my data?" than "what can it change, and where does what it reads end up?" For its Google Workspace connectors, Anthropic's help centre says retrieved data is stored with the chat it was used in, so deleting the chat deletes it, and that Anthropic doesn't train on Gmail, Drive or Calendar connector data. The connected app also processes requests under its own terms. Payroll and banking connectors exist too; leave them off until the nine below have run cleanly for a month.

How does Claude decide what a connector can see and change?

A Claude connector can reach only what your own login can reach in the connected app, and every write tool can be set to Needs approval. A connector links Claude to another app so it can find information there and take actions. Three rules from Anthropic's help centre decide what each one reaches:

  • Your permissions, not more. Claude inherits each person's permissions from the connected service. If you can't open a file, channel or record in the app, the connector can't reach it either. The exception is a custom connector set up with a shared credential, which reaches whatever that credential can access.
  • Tool-by-tool settings. In Customize, then Connectors, each connector lists its tools grouped by type (read-only tools, write and delete tools). Each can be set to Always allow, Needs approval or Blocked. On Team and Enterprise plans, owners can apply restrictions across the organisation, and members can't override them.
  • Approval by default for risky actions. For Gmail, Calendar and Drive, Claude asks for approval before actions such as sending, forwarding, sharing or deleting, unless you use Auto mode, where actions can run without asking unless an automated check flags them. Anthropic warns that the check can miss risky actions and says to use Manual if you want to approve them yourself.

Every connector in the directory also carries a label. A Verified connector has had its tools tested by Anthropic for quality and compatibility; a Community connector was screened but not reviewed in depth; a Custom connector is one you added yourself. Anthropic is explicit that verification isn't a security audit and that a developer can change its tools after review. All nine below showed as Anthropic verified on the claude.com marketplace in November 2026, and each is built by the company that runs the app itself, which matters because that company also runs the server your data passes through.

An electrical contractor's permission plan, in one table

To keep this concrete, picture an illustrative six-person electrical contractor: an owner, an office manager, three electricians and an apprentice. It runs on Google Workspace, Xero, HubSpot for commercial leads, Stripe for card payments, Jobber for scheduling and quotes, Granola for client meetings and Docusign for contracts.

The cost first. Claude Team is $25 per seat per month billed monthly or $20 billed annually, for 2 to 150 seats. Six seats come to $150 a month, or $120 on annual billing. Anthropic charges nothing extra for connectors, which are on every plan. Some apps have their own conditions, covered in each entry below.

ConnectorWho connectsRead toolsWrite toolsSend, share or delete
GmailEveryoneAlways allowDrafts: Always allowNeeds approval
Google CalendarEveryoneAlways allowNeeds approvalDelete: Blocked
Google DriveEveryoneAlways allowNeeds approvalShare and trash: Blocked
XeroOwner and office managerAlways allowNone (read-only)None
HubSpotOwner and office managerAlways allowNeeds approvalNo delete tools
StripeOwner onlyAlways allowBlockedBlocked
JobberOffice managerAlways allowNeeds approvalNeeds approval
GranolaWhoever holds client meetingsAlways allowNeeds approvalNone
DocusignOwnerAlways allowNeeds approvalNeeds approval

Copy the table, change the names and settings, and keep it in a shared document. It's the record of what you decided, and the first thing to check when something unexpected happens.

If you want help choosing and setting up connectors for how your business actually runs, I offer one-to-one AI consultations for small businesses.

The nine, by job

1. Gmail: the inbox, read freely, sent only with approval

Built by: Google. What it sees: your messages and whole threads, labels, drafts, and email metadata including attachment names, but not the attachment contents. What it can change: create drafts, send, reply, forward, apply labels and filters, mark spam and move messages to trash.

Example. "Find every email from the main contractor about the school rewire in the last 30 days and list the questions we haven't answered." An illustrative answer: three open questions (a revised containment route, a request for test certificates and a query about weekend access), each with a citation linking to the original email. The office manager answers the third herself and asks Claude to draft replies to the first two, which land in Drafts for her to send.

Watch-out. Emails are written by other people, and Anthropic warns users to stay alert to prompt injection, where text in content Claude reads tries to steer it. Keeping send and forward on Needs approval means a strange instruction buried in a supplier's email can't turn into an outgoing message without a person seeing it. If your business runs on Outlook, the Microsoft 365 connector covers email, calendar and files together; it's built by Anthropic, a work account needs a Microsoft admin to grant consent, and its write actions stay off until your administrators turn them on.

2. Google Calendar: free time and meeting prep

Built by: Google. What it sees: your events and calendars, including shared calendars you can already access, attendee lists and availability. What it can change: create, update and delete events, respond to invitations, set up recurring meetings and suggest times across attendees.

Example. "Find a two-hour slot next week when both senior electricians are free for the fire alarm handover, avoiding Friday afternoon." Claude reads the shared team calendar and proposes three slots. Creating the event waits for the owner's approval because write tools are set to Needs approval.

Watch-out. Shared calendars often hold more than you think: a medical appointment someone booked on the team calendar is visible to anyone who can see that calendar, and therefore to Claude in their chats. Ask staff to mark personal events private before the team connects.

3. Google Drive: price lists, logs and drawings

Built by: Google. What it sees: search across your Drive, recent files, a file's details and who it's shared with, and the contents of Docs, Sheets, Slides, PDFs, Word, Excel and PowerPoint files and images. Anthropic's help centre says Claude extracts text only from Drive files, so images embedded in documents aren't processed. What it can change: create and upload files, create folders, and share, move or trash files, with sharing and trashing asking for approval by default.

Example. "Read the 2026 rate card sheet and the variation log, and list any variation priced below the rate card." An illustrative answer: two variations (an extra circuit at $185 where the rate card says $210, and four floor boxes charged at last year's rate), with the rows quoted. That's a pricing check the owner used to do by hand once a quarter, if at all.

Watch-out. Because Claude can see who each file is shared with, a question like "which files are shared outside the company?" works, and is worth asking once. Block sharing and trashing for everyone except the owner. Drive files can only be added to a private Claude project, not a shared one.

4. Xero or QuickBooks: the accounts, read first

These two behave very differently, which is why the accounts slot needs a decision rather than a default.

Xero (built by Xero Limited) connects with read-only access, according to its directory listing. It can answer from profit and loss, cash position, aged receivables and payables, invoices, bills, contacts, bank account transactions and the chart of accounts. It can't change anything, which makes it the easiest finance connector to approve.

Intuit QuickBooks (built by Intuit) lists 74 tools. Beyond reports such as profit and loss, cash flow, balance sheet and ageing, it can create, update, send, duplicate and delete invoices and estimates, create payment links, add customers and products, and import transactions. Its listing also mentions read-only payroll answers and, when needed, adding an employee or setting base pay. Intuit's help page says deletions and payment reminders wait for your confirmation, advises checking new invoices in QuickBooks after Claude creates them, says a paid QuickBooks plan is needed for live data, and lists regional limits on availability. It also states that QuickBooks data isn't used to train Claude.

Example (Xero). "Which customers owe us more than $2,000 and are over 60 days late?" An illustrative answer: three customers totalling $11,340, the oldest a property manager at 94 days, with a link back to Xero for each. The owner phones that one first.

How to start with QuickBooks. Set every write tool to Needs approval and block delete tools for everyone but the owner. The companion tutorial on connecting Claude to QuickBooks read-only first, then adding approvals walks through it.

5. HubSpot: the sales pipeline

Built by: HubSpot. What it sees: according to HubSpot's help page, contacts, companies, deals, tickets and custom objects, the full engagement history on records (emails, calls, meetings, notes and tasks), marketing data and commerce data such as quotes, invoices and products. Custom properties marked as sensitive data aren't accessible. What it can change: create and update most CRM records, marketing emails and engagements, up to 10 records at a time in bulk. It can't delete anything.

Permissions. HubSpot says the connector respects each user's HubSpot permissions, that Super Admins choose which data permissions it can use and who can install it, and that connections and create or update actions appear in HubSpot's audit log. HubSpot's page says you need a paid Claude plan (Pro, Max, Team or Enterprise).

Example. "List commercial deals in Quote sent with no activity for 14 days, largest first." Six deals come back (illustrative), worth $48,600 together. The owner asks for a follow-up draft for the top three, and logs the calls in HubSpot after making them. More pipeline prompts are in Claude and HubSpot pipeline questions and call lists.

6. Stripe: payouts and refunds, read-only for most firms

Built by: Stripe. What it sees and changes: Stripe's documentation lists a read tool that can call any Stripe API method that reads data, and a write tool that can call any method that creates, updates or deletes, plus balance summaries and analytics. That write tool is broad, which is the reason to block it.

Permissions. When you connect, Stripe's own consent screen lets you grant access to live accounts or test sandboxes and set different permissions for each. Stripe administrators can switch MCP access on or off for the whole team, connected sessions can be revoked from Stripe's user settings, and Stripe can require a person to confirm certain actions, such as refunds, in its dashboard, separately from Claude's own approval setting.

Example. "How much was paid out last week, and were there any refunds or disputes?" A read-only question that used to mean logging in and filtering three reports. For a walkthrough, see checking Stripe payouts and refunds in plain English.

7. Jobber: jobs, quotes and the schedule

Built by: Jobber. What it sees: clients, properties, requests, quotes, jobs, visits, invoices and payments. What it can change: create and update clients, properties and requests, among other actions. Jobber's listing says you review and approve changes before they're made, and describes turning a customer email into a ready-to-review quote.

Example. Gmail and Jobber together: "Read the latest email from the café owner about the extra sockets and create a request in Jobber with the address and what they asked for." Claude drafts the request; the office manager approves it, then prices it in Jobber as usual. If you use a different job management app, check the directory for its own connector before assuming you need this one.

8. Granola: what was said in client meetings

Built by: Granola. What it sees: your Granola notes, AI summaries and full transcripts, and with Granola's Snapshots turned on, the slides and charts shared in meetings. Claude only sees notes you can already access in Granola, and transcripts and full meeting history need Granola's Business or Enterprise plan. What it can change: little; one tool creates a meeting note from a transcript.

Example. "What did we agree with the facilities manager about access times for the second-floor works?" Claude answers with the quote and the meeting it came from, which settles a disagreement in a minute rather than an hour of notebook searching. If you use Fathom instead, its connector covers summaries, transcripts and action items in a similar way.

9. Docusign: contracts out and signatures back

Built by: Docusign. What it sees: envelopes, templates, agreements and their details, such as renewal dates and key obligations. What it can change: create envelopes, update recipients and fields, send reminders and trigger Docusign workflows.

Example. "Which contracts sent this month are still unsigned, and when did each go out?" Two maintenance contracts (illustrative), one sent 12 days ago. The reminder Claude offers to send waits for the owner's approval. More on this pairing is in preparing and tracking contracts with Claude and Docusign.

Which Claude connectors should you leave off at first?

Payroll, banking and similar high-impact connectors should stay off until the nine above have run cleanly for a month. These are real, verified connectors. The issue isn't trust in the developer; it's how much they can do with one sentence typed by someone in a hurry.

  • Payroll (Gusto). Gusto's documentation says connecting needs full admin permissions, that access is limited to the data categories you grant, and that its tools cover employee details, home addresses, compensation history and payrolls. Eligible customers can run payroll from Claude. Gusto itself advises confirming every tool call and not enabling automatic execution.
  • Banking (Mercury). Its tools include requests to send and transfer money, which go into Mercury for approval. Useful later, but not in month one.
  • PayPal's write tools. The listing includes refunds, paying orders, accepting dispute claims and cancelling subscriptions. If you connect PayPal for reporting, block every write tool.
  • Square exposes a general request tool rather than separate named actions, so you can't approve reads and block payments tool by tool in the same way. Use it for reporting questions only, with that tool on Needs approval.
  • Community and custom connectors that touch money or client records. Screened is not reviewed. Anthropic's advice for any third-party connector: only connect developers you trust, review the permissions requested at sign-in, and watch for unexpected changes in behaviour. Free accounts can add only one custom connector anyway.

If an app you rely on has no connector at all, linking it to Claude through Zapier is the usual workaround.

How do you switch connectors on in a Team account without surprises?

In a Team account the owner adds each connector for the organisation, and adding one gives nobody access until each person signs in with their own account.

  1. Owner adds each connector for the organisation. In Organization settings, then Connectors, select Browse connectors, pick one and choose Add to your team. Adding it doesn't give anyone access; each person still signs in with their own account.
  2. Set organisation-wide restrictions before anyone connects. Use the permission table above. Restrictions apply to everyone and members can't override them.
  3. Decide on chat sharing. If your organisation turns off sharing of chats that use connectors, people can't share chats containing connector content. For a firm handling client contracts, that's a sensible default.
  4. Leave connector requests on. On Team plans, members can request a connector from its directory page and the owner approves or declines it. That's better than people adding things on personal accounts.
  5. Choose how connectors load. Anthropic's tool access setting has three modes: Auto, Always available and On demand. Its guidance: with fewer than 10 connectors you use constantly, Always available; with 10 or more, On demand keeps conversations from running out of room.
  6. Connect one person first. The office manager connects all nine, runs the examples in this tutorial and reports anything odd before the rest of the team joins.

Our tutorial on Claude Team admin settings covers the other switches worth checking while you're in there, and the Google trio has its own setup guide in setting up Claude's Gmail, Calendar and Drive connectors safely.

How much time can connectors save on a Monday cash check?

In the illustrative contractor's example, one read-only prompt across Xero, Stripe and Jobber cut a 40-minute Monday cash check to about ten minutes. Here's the before and after that convinced the owner the setup was worth an afternoon.

Before: every Monday, 40 minutes logging into Xero for overdue invoices, Stripe for last week's card payments and Jobber for completed jobs not yet invoiced, then a notebook list of calls to make.

After: one prompt with Xero, Stripe and Jobber turned on:

Using Xero, Stripe and Jobber only:
1. List invoices over 30 days overdue, largest first, with days late.
2. Total last week's Stripe payouts and list any refunds or disputes.
3. List Jobber jobs marked complete in the last 14 days with no invoice.
Finish with a call list: who to phone today and why, max 8 lines.
Don't create, send or change anything.

An illustrative result: four overdue invoices worth $9,870, $6,420 paid out through Stripe with no refunds, and two finished jobs never invoiced (a consumer unit swap and an EV charger install, $1,940 between them). Ten minutes including checking the two uninvoiced jobs in Jobber before raising invoices. The last line of the prompt matters: even with write tools on Needs approval, asking for no changes keeps a reporting chat a reporting chat.

If you want the weekly cash figures laid out in a spreadsheet that totals itself, try The Complete Excel Course with AI Integration on Coding Liquids.

What should you check after the first fortnight?

After the first fortnight, review approvals, move tools nobody needs to Blocked and disconnect any connector nobody used.

  • Review approvals. If people approve every request without reading, the setting has become a click. Move tools nobody needs to Blocked.
  • Disconnect what nobody used. Anthropic's advice is to disconnect services you no longer need. Fewer connectors also leave more room in each conversation.
  • Look at the app's own logs. HubSpot records connector actions in its audit log; Stripe lists connected sessions in user settings, where you can revoke them.
  • Re-read the directory listing. Developers can change a connector's tools after review. A connector that was read-only last month may not be next month, so check the tool list in Customize, then Connectors, once a quarter.
  • Ask the privacy question again. Anthropic notes that connected services process data on their own infrastructure under their own terms. If a client contract restricts where their data goes, check each provider's terms, not just Anthropic's.

Get these nine working with sensible permissions and Claude stops being a chat window and starts answering questions about your own business. Then add skills, so it does those jobs your way.

Claude connectors for small business: questions owners ask

Which Claude connectors should a small business switch on?

Nine are worth switching on for most small businesses: Gmail, Google Calendar and Google Drive (or Microsoft 365), an accounts connector (Xero reads only; QuickBooks can also write), HubSpot, Stripe, Jobber, Granola and Docusign. Each sees only what your own login can see, and every write tool can be set to Needs approval.

What can a Claude connector see?

Only what your own login can see in that app. Claude inherits each person's permissions from the connected service, so if you cannot open a file, channel or record, the connector cannot reach it either. The exception is a custom connector set up with a shared credential, which reaches whatever that credential can access.

Do Claude connectors cost extra?

Not from Anthropic. Its pricing page lists connectors on every plan, including Free, and Team seats cost $20 per person per month billed annually or $25 monthly. Some providers set their own conditions: HubSpot's help page asks for a paid Claude plan, Intuit needs a paid QuickBooks plan for live data, and Granola transcripts need its Business or Enterprise plan.

Does Anthropic train Claude on data pulled in through connectors?

Anthropic says it doesn't train its models on Gmail, Drive or Calendar connector data. On consumer plans (Free, Pro, Max and Ultra) with model training switched on, content you copy and paste from those connectors, or Claude responses containing it, may be used. Business plans such as Team don't train on business content by default.

Can I stop Claude sending emails or deleting files?

Yes. In Customize, then Connectors, each connector lists its tools grouped as read-only or write and delete, and each can be set to Always allow, Needs approval or Blocked. On Team and Enterprise plans, owners can set these restrictions for the whole organisation and members can't override them.

What's the difference between a Verified and a Community connector?

Anthropic tests a Verified connector's tools for quality and compatibility; a Community connector is screened before listing but not reviewed in depth. Anthropic says verification isn't a security audit, and that a connector's developer can change its tools after review, so the label is a starting point, not a guarantee.

Further reads

Sources: Claude help centre articles on connectors, Google Workspace connectors and tool access; Claude docs on the connectors directory, connector verification and the Microsoft 365 connector; claude.com marketplace listings for each connector; claude.com pricing; HubSpot, Intuit QuickBooks, Stripe and Gusto documentation for their Claude connectors (all checked 17 November 2026).

Ready to put AI on the jobs that eat your week?

No data team or big budget needed. In a 1:1 consultation I show small and medium-sized businesses and self-employed people which AI tools they can use, one workflow at a time.

Book a 1:1 call with me