How to Use Claude's Small Business Plugin Pack: Setup, Skills, and Connectors

What Small Businesses Actually Get From Claude Automation

Running a small business means wearing too many hats. You’re handling payroll one hour, chasing invoices the next, and trying to onboard a new hire before the end of the week. Claude can help with all of this — but only if it’s connected to the right tools with the right capabilities configured.

That’s the premise behind what people are calling the Claude small business plugin pack: a curated collection of skills and app connectors that turns Claude from a general-purpose assistant into something that can actually run your back office. This guide covers what the pack includes, how to install and configure it, which connectors to prioritize, and where things typically go wrong.

---

What the Small Business Plugin Pack Actually Is

The “plugin pack” isn’t a single download from Anthropic. It’s a structured set of tool integrations — typically 20 to 35 discrete capabilities — that extend Claude beyond text generation into real system actions.

These capabilities are made possible through Claude’s tool use API, which allows external functions to be registered as callable tools. When Claude processes a request, it can decide to call one of these tools, pass the right parameters, and act on the result.

The 31-skill small business variant typically groups these tools into five categories:

• Payroll and compensation — run payroll cycles, check pay stubs, calculate overtime, flag anomalies
• Invoicing and accounts receivable — generate invoices, send payment reminders, reconcile payments, create statements
• HR and onboarding — create employee records, trigger onboarding sequences, track PTO, send policy documents
• Scheduling and calendar — book appointments, manage team availability, reschedule on conflict
• Customer communication — draft and send emails, log interactions to CRM, pull contact history

Each skill maps to at least one connector — a live integration with a business tool like QuickBooks, Gusto, HubSpot, or Google Workspace. Without the connectors, the skills are just prompts. With them, Claude can actually do things.

---

Before You Start: Prerequisites

Getting this stack running requires a few things in place before you touch any configuration.

Claude API Access

You’ll need access to Claude through Anthropic’s API, not just through Claude.ai’s chat interface. The chat interface doesn’t support custom tool definitions in the same structured way.

Sign up for API access at Anthropic’s developer console. You’ll get an API key that you’ll use to authenticate all requests. Start with claude-3-5-sonnet for most small business workflows — it balances capability and cost well.

A Platform or Runtime Environment

Claude’s API doesn’t install skills on its own. You need something to:

• Define the tools and their schemas
• Route requests to the right integrations
• Handle authentication with external apps
• Manage conversation context across sessions

You can build this yourself with Node.js or Python, or use a no-code automation platform that handles the infrastructure. Both approaches work — the tradeoff is setup time versus flexibility.

Accounts With the Apps You’re Connecting

For each connector you want to activate, you need an existing account with that service and API credentials (usually an API key or OAuth token). Have these ready before you start configuring integrations.

---

Installing the Core Skills

Defining Tools in the Claude API

Each skill in the pack is defined as a JSON schema object that tells Claude what the tool does, what parameters it accepts, and what it returns. Here’s a simplified example for an invoice creation tool:

{
  "name": "create_invoice",
  "description": "Creates a new invoice for a customer in the billing system",
  "input_schema": {
    "type": "object",
    "properties": {
      "customer_id": { "type": "string" },
      "line_items": { "type": "array" },
      "due_date": { "type": "string" }
    },
    "required": ["customer_id", "line_items"]
  }
}

You pass an array of these tool definitions with every Claude API request. Claude reads the descriptions and decides which tool to call based on the user’s intent.

The quality of the description field matters more than most people realize. A vague description like “handles invoices” will produce unpredictable behavior. A specific one like “creates a new draft invoice in QuickBooks for a specified customer with line items and optional due date” gives Claude the context it needs to use the tool correctly.

Registering All 31 Skills

For a full small business plugin pack, you’re registering tools across all five categories. This typically means:

• 6–8 payroll skills (run payroll, check employee pay history, update withholding, etc.)
• 6–8 invoicing skills (create, send, update, void, reconcile)
• 7–9 HR skills (create record, update status, log performance note, query PTO balance, etc.)
• 4–5 scheduling skills
• 4–5 communication skills

All 31 get passed in the tools parameter on each API call. Claude only calls the relevant ones — having all 31 defined doesn’t slow things down or increase hallucination risk if descriptions are clear.

---

Configuring the Connectors

Payroll: Gusto and ADP

For Gusto, you’ll authenticate via OAuth 2.0. Generate an access token through Gusto’s developer portal and store it securely — never hard-code it in your tool handler. The most useful payroll skills to connect first are:

• get_employee_list — pulls current headcount and IDs
• run_payroll — initiates a payroll run for a specified period
• get_pay_stub — retrieves compensation details for an employee

ADP uses a similar OAuth flow but has a more complex API surface. If you’re starting out, Gusto is easier to connect and better documented for small business use cases.

Invoicing: QuickBooks and FreshBooks

QuickBooks Online is the most common connector here. Connect via OAuth 2.0 through Intuit’s developer portal. Priority skills:

• create_invoice — creates and saves a draft
• send_invoice — delivers via email directly from QuickBooks
• get_outstanding_invoices — returns all unpaid invoices with aging data
• apply_payment — marks an invoice paid and logs the payment method

FreshBooks works similarly and is often preferred by freelancers and very small teams. The API is simpler to navigate than QuickBooks for basic invoicing operations.

HR: BambooHR and Rippling

BambooHR provides a REST API with API key authentication. Useful skills to connect:

• create_employee — adds a new hire to the system
• get_employee — pulls a full employee record
• update_pto_balance — adjusts time-off balances
• trigger_onboarding — starts an automated onboarding workflow

Rippling covers HR, IT, and payroll in one platform and has a more complex integration surface. Start with just the HR endpoints if you’re connecting Rippling — the IT and device management endpoints add scope you may not need yet.

CRM: HubSpot and Salesforce

For customer communication skills, HubSpot is the most accessible connector for small businesses. Authenticate with a private app token. Core skills:

• get_contact — retrieves contact history and properties
• log_interaction — creates a note or activity on a contact record
• send_email — sends a tracked email through HubSpot’s email system
• create_deal — opens a new deal in the pipeline

Salesforce works for larger small businesses already on that platform. The REST API is well-documented, but the authentication setup (OAuth 2.0 with a connected app) takes longer to configure than HubSpot’s token-based approach.

Calendar: Google Calendar and Calendly

Google Calendar uses OAuth 2.0 via Google’s developer console. The most valuable skills here:

• create_event — books a meeting with specified attendees
• check_availability — returns open slots for one or more calendars
• reschedule_event — moves an existing event

Calendly is useful if your business takes external bookings. Connect via Calendly’s API key and use it primarily for get_scheduled_events and cancel_event skills.

---

Building Workflows With the Skills

Individual skills are useful. Chained together, they become workflows that handle multi-step processes without human involvement.

Example: Invoice-to-Payment Workflow

1. User says: “Send the outstanding invoice to Acme Corp and follow up in 7 days if unpaid.”
2. Claude calls get_outstanding_invoices with a filter for Acme Corp.
3. Finds two unpaid invoices, confirms with user.
4. Calls send_invoice for both.
5. Schedules a follow-up task via create_event seven days out.
6. Logs the activity to HubSpot via log_interaction.

This used to require opening four different apps. With the connectors live, it’s one conversation turn.

Example: New Hire Onboarding

1. Manager says: “Onboard Sarah Chen, starting Monday as a marketing coordinator.”
2. Claude calls create_employee in BambooHR with the details.
3. Calls trigger_onboarding to start the document flow.
4. Creates a kickoff meeting in Google Calendar for Monday morning.
5. Sends a welcome email via HubSpot.

Example: Payroll Exception Report

1. Finance lead asks: “Were there any overtime hours flagged in last week’s payroll?”
2. Claude calls run_payroll in review mode (not execute) or get_payroll_summary for the period.
3. Filters for overtime flags, presents a summary.
4. Offers to send the summary to the relevant manager via email.

---

Where MindStudio Fits

If you want to deploy all of this without writing and maintaining the API integration code yourself, MindStudio is worth looking at.

MindStudio’s no-code builder lets you define Claude-powered agents with tools, connectors, and logic visually. The platform has 1,000+ pre-built integrations — including QuickBooks, Gusto, HubSpot, BambooHR, Google Workspace, and Calendly — so you’re not building each connector from scratch.

You pick Claude (or any other model) as the reasoning engine, configure which integrations to attach, define your agent’s behavior with plain-language instructions, and deploy. The whole thing typically takes under an hour. MindStudio handles authentication, rate limiting, retries, and session management, so you’re focused on what the agent should do rather than how the infrastructure works.

For small businesses that want a full 31-skill pack without a developer on staff, this is the practical path. Agents can run on a schedule, trigger from email, or respond to chat inputs — depending on how you want to interact with them.

You can try MindStudio free at mindstudio.ai.

For teams that do have developers, MindStudio also offers the Agent Skills Plugin — an npm SDK (@mindstudio-ai/agent) that exposes 120+ typed capabilities to any AI agent, including Claude Code. Methods like agent.sendEmail(), agent.searchGoogle(), and agent.runWorkflow() let you call business functions as clean method calls without managing the API plumbing yourself.

---

Common Setup Problems and Fixes

Tool descriptions are too vague. Claude makes poor tool-selection decisions when descriptions are generic. Rewrite descriptions to be specific about what the tool does, what inputs it expects, and under what circumstances Claude should use it.

OAuth tokens expiring mid-session. Most connectors issue tokens with expiration times. Build token refresh logic into your handler, or use a platform that manages this automatically.

Conflicting tool names. If you have both a QuickBooks get_customer and a HubSpot get_contact that both sound like “look up a customer,” Claude may call the wrong one. Name tools with the system prefix: quickbooks_get_customer and hubspot_get_contact.

Claude not calling tools when expected. Check that the tool is included in the tools array for that request. Also check the model — older Claude versions have more limited tool use. Use claude-3-5-sonnet or later for reliable multi-tool workflows.

Missing required fields. If a tool call fails because Claude didn’t pass a required parameter, your description probably didn’t make that field’s necessity clear. Update the description and add an enum or example to the schema where possible.

---

Frequently Asked Questions

Does Claude’s small business plugin pack require coding to set up?

It depends on how you approach it. Building directly on the Claude API requires writing code to define tool schemas, handle tool calls, and manage connector authentication. Using a no-code platform like MindStudio removes that requirement — you configure connectors through a visual interface and the platform handles the integration layer. Either path works; the tradeoff is control versus setup speed.

Which Claude model works best for small business automation?

For most small business workflows — invoicing, HR, payroll queries — claude-3-5-sonnet is the right choice. It handles multi-step tool use reliably and at a cost that scales reasonably for small business usage volumes. claude-3-opus is more capable but more expensive; use it only if your workflows involve complex reasoning or analysis. claude-3-haiku is fast and cheap, but less reliable for multi-tool coordination.

How many tools can Claude use in a single conversation?

Technically, you can pass up to 128 tool definitions to Claude at once. Practically, performance stays consistent up to about 50 tools. For a 31-skill pack, this is well within limits. Claude only calls tools when relevant — having 31 defined doesn’t mean it calls all 31 on every request.

Can Claude handle payroll processing end-to-end without human review?

Not recommended for fully automated execution. Payroll errors are hard to reverse and carry legal and financial consequences. The better workflow pattern is: Claude prepares the payroll run, flags any anomalies, and presents a summary for human approval before executing. This is how most teams using AI-assisted payroll structure it — Claude handles the legwork, a human approves the final action.

What’s the difference between a skill and a connector in this context?

A skill is the capability definition — what Claude knows it can do (e.g., “create an invoice”). A connector is the live integration with an external system that actually executes the action (e.g., the QuickBooks API connection that creates the invoice in QuickBooks). You need both: the skill tells Claude what’s available, the connector makes it real.

Is this setup GDPR and SOC 2 compliant?

Compliance depends on your specific connector implementations and data handling practices, not just Claude itself. Anthropic offers a Business Associate Agreement (BAA) for healthcare use cases and has enterprise compliance options. For the connectors (QuickBooks, Gusto, HubSpot, etc.), each platform has its own compliance certifications. Review your data residency requirements before routing sensitive employee or financial data through AI workflows, and use enterprise-tier API plans where compliance documentation is available.

---

Key Takeaways

• The Claude small business plugin pack is a structured collection of ~31 tool integrations across payroll, invoicing, HR, scheduling, and customer communication
• Each skill requires a corresponding connector — a live API integration with tools like QuickBooks, Gusto, BambooHR, or HubSpot
• Tool descriptions are critical: vague descriptions produce unreliable tool-calling behavior
• Chaining skills into multi-step workflows (invoice → follow-up → CRM log) is where the real time savings come from
• For teams without developers, MindStudio’s no-code platform handles connector setup, authentication, and agent deployment with Claude built in
• Never fully automate payroll execution — keep a human approval step before running

If you want to get a small business automation stack running without managing API infrastructure, MindStudio is a practical starting point. You can build a Claude-powered agent connected to your existing tools and have it handling routine business tasks in a single session. Start free, and add connectors as your needs grow.