← Back to Skills Marketplace
7938
Downloads
5
Stars
0
Active Installs
15
Versions
Install in OpenClaw
/install quickbooks
Description
QuickBooks API integration with managed OAuth. Install only if you need QuickBooks accounting administration. Connect with a least-privileged QuickBooks account, verify the intended connection ID before each request, and revoke unused connections promptly. This integration can mutate accounting records — approve only specific write actions after checking the exact endpoint, account, resource ID, amounts, and consequence. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a QuickBooks connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a QuickBooks action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with QuickBooks examples; they add no QuickBooks capability - QuickBooks is not an event source, a trigger cannot read QuickBooks data, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe).
Usage Guidance
Install only if you need agent-assisted QuickBooks administration. Use a least-privileged QuickBooks connection, verify the Maton account and connection before each request, review every financial write or deletion carefully, and avoid persistent triggers or destinations unless you explicitly need ongoing automation and understand what data will flow.
Capability Assessment
Credentials
The skill uses network access, managed OAuth, optional SDKs, and a raw HTTP fallback with a Maton API key only when the CLI is unavailable; these are proportionate for an API integration but require careful credential handling.
Install Mechanism
Installation is limited to pinned Maton CLI/SDK package versions and no executable files are shipped in the artifact; the skill does not auto-install, auto-run, or fetch unreviewed remote payloads.
Instruction Scope
The instructions repeatedly default to read/list operations, require explicit user approval for writes, connection creation, destructive actions, hosted functions, triggers, and persistent destinations, and warn that external API content is untrusted data.
Persistence & Privilege
OAuth credentials, hosted functions, triggers, and destinations can persist across sessions, but the artifact discloses this and instructs agents to obtain approval, use DENY_ALL network policy for functions by default, scope triggers, and delete unused resources.
Purpose & Capability
The skill enables QuickBooks reads and writes for customers, vendors, invoices, payments, bills, accounts, reports, and batch requests; that is high-impact financial authority, but it directly matches the stated accounting-administration purpose.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install quickbooks - After installation, invoke the skill by name or use
/quickbooks - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.2.6
Simplify the login instructions to the code flow (maton login prints a link; finish with maton login --code <CODE>), drop the API Key subsection, and pin the Maton CLI install to 0.4.0.
v1.2.5
Switch the login instructions to the device flow (maton login prints a link and a user code; the --oauth flag is gone) and pin the Maton CLI install to 0.3.5.
v1.2.4
Pin the Maton CLI install to 0.3.4, the current release.
v1.2.3
Add this skill's own trigger policy to the shared Triggers section: the only destination it sets up is its own hosted function inside the platform, it does not forward events to third-party hosts, and it does not use event watch --exec; each trigger reference now also says this skill configures no trigger from that source on its own.
v1.2.2
Bring the skill to the current api-gateway baseline and tell the connection-to-function-to-trigger story: the shared Functions and Triggers sections open with an example for this app (a hosted function that performs one action for it through the Maton SDK, and the trigger that runs it - its own event source where it has one, otherwise a time schedule), the description says these constructs turn the connection into automation and add no capability of their own, the passthrough is described by its enforced boundary, CLI and SDK installs are pinned to 0.3.1, absolute API URLs are placeholders, and multipart uploads use mktemp.
v1.2.1
Judge writes by what the call does rather than its HTTP method: QuickBooks routes updates and deletes through POST with ?operation=, so the verb carries no intent. Also replace the generic high-impact category list with QuickBooks operations (money and ledger state, closed or reconciled periods, void versus delete, record merges, batch requests) and name QuickBooks' own fields as the untrusted-input sources
v1.2.0
CLI-first rewrite with the Maton SDK examples; clarify that the CLI and SDKs keep separate credential stores, and reword webhook egress warnings
v1.1.0
CLI-first rewrite: the maton CLI with OAuth login is the documented path, every example is a maton command, SDK examples added, and the raw HTTP fallback feeds the key on stdin instead of reading it from the environment
v1.0.6
- Added enhanced security and permission guidance: strong warnings to use least-privileged accounts, confirm connection IDs, and require explicit user approval before any write operation.
- Updated description to stress administrative risk and best practices for safe connection management.
- Clarified that only documented/supported API endpoints may be used, discouraging construction of arbitrary paths.
- Added requirement to always include the Maton-Connection header, especially for write operations, to avoid unintended access.
- Emphasized step-by-step resource verification and user confirmation processes for all accounting mutations.
v1.0.5
- Updated all service and API endpoints from gateway.maton.ai and ctrl.maton.ai to api.maton.ai for consistency.
- Clarified connection management URLs and instructions.
- Improved guidance for handling multiple QuickBooks connections, recommending always including the Maton-Connection header.
- Added a "Security & Permissions" section emphasizing user confirmation before any write operation.
- Removed LICENSE.txt file from the repository.
v1.0.4
- Added a new clawdbot metadata block specifying an emoji and required environment variable (MATON_API_KEY).
- No other functional or documentation changes detected.
v1.0.3
- No code or documentation changes detected in this release.
- Version number updated to 1.0.3.
v1.0.2
- Added a note to the skill description directing users to use the api-gateway skill for third party apps other than QuickBooks.
- Updated all shell command code examples to use Python scripts with urllib for greater compatibility and easier API key handling.
- Added important notes about using curl with `-g` to handle bracketed parameters and about possible shell issues with environment variable expansion in piped commands.
v1.0.1
- Added support for specifying a QuickBooks connection using the Maton-Connection header for environments with multiple connections.
- Updated base URL instructions for clarity on native API endpoint paths.
- Included new connection response fields: creation_time, last_updated_time, and metadata.
- Clarified API key instructions and updated authentication steps.
- Enhanced connection management documentation and header usage examples.
v1.0.0
Initial release of QuickBooks API skill with managed OAuth.
- Connect your QuickBooks account securely using managed OAuth flow.
- Query and manage customers, invoices, payments, and bills via QuickBooks API endpoints.
- Run financial reports, including Profit and Loss and Balance Sheet.
- Supports batch operations and SQL-like query language.
- Maton API key required for authentication; detailed setup and code examples included.
Metadata
Frequently Asked Questions
What is QuickBooks?
QuickBooks API integration with managed OAuth. Install only if you need QuickBooks accounting administration. Connect with a least-privileged QuickBooks account, verify the intended connection ID before each request, and revoke unused connections promptly. This integration can mutate accounting records — approve only specific write actions after checking the exact endpoint, account, resource ID, amounts, and consequence. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a QuickBooks connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a QuickBooks action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with QuickBooks examples; they add no QuickBooks capability - QuickBooks is not an event source, a trigger cannot read QuickBooks data, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe). It is an AI Agent Skill for Claude Code / OpenClaw, with 7938 downloads so far.
How do I install QuickBooks?
Run "/install quickbooks" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is QuickBooks free?
Yes, QuickBooks is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does QuickBooks support?
QuickBooks is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created QuickBooks?
It is built and maintained by byungkyu (@byungkyu); the current version is v1.2.6.
More Skills