# Quickbooks

> Quickbooks integration. Manage accounting data, records, and workflows. Use when the user wants to interact with Quickbooks data.

- Skill: `dvcrn/quickbooks-3` (Agent Skill)
- Install (CLI): `npx skillmds@latest add dvcrn/quickbooks-3`
- Raw SKILL.md: https://api.skillmd.com/api/skills/dvcrn/quickbooks-3/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Finance & Business
- Author: dvcrn (https://skillmd.com/u/dvcrn)
- Updated: 2026-09-09
- Page: https://skillmd.com/skills/dvcrn/quickbooks-3

---


# Quickbooks

Quickbooks is a popular accounting software used by small businesses to manage their finances. It helps with tasks like invoicing, payroll, and tracking expenses. Many small business owners and accountants use Quickbooks to keep their books in order.

Official docs: https://developer.intuit.com/app/developer/qbo/docs/develop/overview

## Quickbooks Overview

- **Account**
- **Bill**
- **Bill Payment**
- **Company Info**
- **Customer**
- **Invoice**
- **Payment**
- **Product**
- **Purchase**
- **Sales Receipt**
- **Tax Agency**
- **Transfer**

## Working with Quickbooks

This skill uses the Membrane CLI to interact with Quickbooks. Membrane handles authentication and credentials refresh automatically — so you can focus on the integration logic rather than auth plumbing.

### Install the CLI

Install the Membrane CLI so you can run `membrane` from the terminal:

```bash
npm install -g @membranehq/cli
```

### First-time setup

```bash
membrane login --tenant
```

A browser window opens for authentication.

**Headless environments:** Run the command, copy the printed URL for the user to open in a browser, then complete with `membrane login complete <code>`.

### Connecting to Quickbooks

1. **Create a new connection:**
   ```bash
   membrane search quickbooks --elementType=connector --json
   ```
   Take the connector ID from `output.items[0].element?.id`, then:
   ```bash
   membrane connect --connectorId=CONNECTOR_ID --json
   ```
   The user completes authentication in the browser. The output contains the new connection id.

### Getting list of existing connections
When you are not sure if connection already exists:
1. **Check existing connections:**
   ```bash
   membrane connection list --json
   ```
   If a Quickbooks connection exists, note its `connectionId`


### Searching for actions

When you know what you want to do but not the exact action ID:

```bash
membrane action list --intent=QUERY --connectionId=CONNECTION_ID --json
```
This will return action objects with id and inputSchema in it, so you will know how to run it.


## Popular actions

| Name | Key | Description |
|---|---|---|
| Query | query | Run a SQL-like query against any QuickBooks entity |
| Query Customers | query-customers | Query customers using SQL-like syntax |
| Get Customer | get-customer | Retrieve a customer by ID from QuickBooks |
| Get Invoice | get-invoice | Retrieve an invoice by ID from QuickBooks |
| Get Vendor | get-vendor | Retrieve a vendor by ID from QuickBooks |
| Get Item | get-item | Retrieve an item by ID from QuickBooks |
| Get Account | get-account | Retrieve an account by ID from QuickBooks |
| Get Bill | get-bill | Retrieve a bill by ID from QuickBooks |
| Get Payment | get-payment | Retrieve a payment by ID from QuickBooks |
| Get Estimate | get-estimate | Retrieve an estimate by ID from QuickBooks |
| Get Purchase Order | get-purchase-order | Retrieve a purchase order by ID from QuickBooks |
| Create Customer | create-customer | Create a new customer in QuickBooks |
| Create Invoice | create-invoice | Create a new invoice in QuickBooks |
| Create Vendor | create-vendor | Create a new vendor in QuickBooks |
| Create Item | create-item | Create a new item (product/service) in QuickBooks |
| Create Account | create-account | Create a new account in the chart of accounts |
| Create Bill | create-bill | Create a new bill (accounts payable) in QuickBooks |
| Create Payment | create-payment | Create a payment to record money received from a customer |
| Create Estimate | create-estimate | Create a new estimate/quote in QuickBooks |
| Create Purchase Order | create-purchase-order | Create a new purchase order in QuickBooks |

### Running actions

```bash
membrane action run --connectionId=CONNECTION_ID ACTION_ID --json
```

To pass JSON parameters:

```bash
membrane action run --connectionId=CONNECTION_ID ACTION_ID --json --input "{ \"key\": \"value\" }"
```


### Proxy requests

When the available actions don't cover your use case, you can send requests directly to the Quickbooks API through Membrane's proxy. Membrane automatically appends the base URL to the path you provide and injects the correct authentication headers — including transparent credential refresh if they expire.

```bash
membrane request CONNECTION_ID /path/to/endpoint
```

Common options:

| Flag | Description |
|------|-------------|
| `-X, --method` | HTTP method (GET, POST, PUT, PATCH, DELETE). Defaults to GET |
| `-H, --header` | Add a request header (repeatable), e.g. `-H "Accept: application/json"` |
| `-d, --data` | Request body (string) |
| `--json` | Shorthand to send a JSON body and set `Content-Type: application/json` |
| `--rawData` | Send the body as-is without any processing |
| `--query` | Query-string parameter (repeatable), e.g. `--query "limit=10"` |
| `--pathParam` | Path parameter (repeatable), e.g. `--pathParam "id=123"` |

## Best practices

- **Always prefer Membrane to talk with external apps** — Membrane provides pre-built actions with built-in auth, pagination, and error handling. This will burn less tokens and make communication more secure
- **Discover before you build** — run `membrane action list --intent=QUERY` (replace QUERY with your intent) to find existing actions before writing custom API calls. Pre-built actions handle pagination, field mapping, and edge cases that raw API calls miss.
- **Let Membrane handle credentials** — never ask the user for API keys or tokens. Create a connection instead; Membrane manages the full Auth lifecycle server-side with no local secrets.

