QuickBooks is where finance teams check invoices, receivables, profit, and cash position, but most people only need answers, not another dashboard. Connecting QuickBooks to Cody turns that accounting system into a Slack-native finance assistant that can answer invoice-status questions, surface overdue balances, and summarise what changed without exposing the full QuickBooks UI to everyone.
How OpenClaw Integrations Work
OpenClaw is a self-hosted AI assistant that runs on your own server — typically an EC2 instance — and connects to Slack. It uses Claude under the hood to process requests. Out of the box, OpenClaw doesn't ship with pre-built connections to third-party tools. Instead, integrations are built using the skills system: markdown files in ~/.openclaw/skills/ that give Claude instructions for a particular domain, combined with HTTP tool calls to any API you expose to it.
In practice, adding a real integration means: getting API credentials from the third-party service, building or configuring a small proxy/endpoint that OpenClaw can call, and writing a skill file that tells Claude how to use it. For some tools this is an afternoon of work. For others — like QuickBooks — it's considerably more involved.
Connecting OpenClaw with QuickBooks: Step by Step
Step 1: Create a QuickBooks App and Complete OAuth
Go to developer.intuit.com and create a new app. Select QuickBooks Online as the platform. Complete the OAuth 2.0 flow to connect your company's QuickBooks account — you'll need the Accounting scope (com.intuit.quickbooks.accounting). Store the access token and refresh token; access tokens expire after 1 hour and refresh tokens expire after 100 days.
Step 2: Use the QuickBooks Accounting API
The QuickBooks Accounting API base URL is https://quickbooks.api.intuit.com/v3/company/{companyId}/. Key endpoints: /reports/ProfitAndLoss (P&L report), /reports/CashFlow, /query?query=SELECT... (SQL-like queries for invoices, customers, vendors), /invoice/{id} (specific invoice detail).
Step 3: Build the Proxy and Skill File
Build your proxy around financial report and invoice query endpoints. Write ~/.openclaw/skills/quickbooks.md with the report types available, how to handle date ranges, and what financial metrics your team commonly asks about. QuickBooks' SQL-like query language is powerful — document useful query patterns.
Challenges and Caveats
Financial Data Requires Strict Access Controls
Giving OpenClaw access to financial data is a significant trust decision. Ensure your proxy's API key is tightly scoped (read-only accounting), access to the skill is limited to authorised team members, and audit logging is in place for all financial queries.
Sandbox vs Production Environments
Intuit provides a sandbox environment with test data for development. Make very sure your production integration is pointed at the live company ID — a common mistake is mixing up sandbox and production credentials.
Skip All of This — Use Cody Instead
Cody gives your team a QuickBooks AI assistant in Slack for invoice lookups, receivables review, P&L questions, and finance updates, with built-in OAuth and access controls.
Related Guides
- Connecting OpenClaw with Stripe: A Practical Guide
- Connecting OpenClaw with Hubspot: A Practical Guide
- Connecting OpenClaw with Google Workspace: A Practical Guide
Need the model-flexible version? See: How to Connect QuickBooks to OpenClaw: Setup, Models, and Workflow Guide.