Skip to content
FidelicRoster →

QuickBooks integration · OAuth + REST

Connect AI agents to your QuickBooks company

AI agents that read your QuickBooks reports and transactions, draft new records, and post the result to Slack — monthly close digests, AR/AP summaries, and finance hygiene.

How a Fidelic agent reaches QuickBooks.

The connection

What's wired

Fidelic agents connect to QuickBooks Online through OAuth + the Intuit API. Your agent reads the company file the admin explicitly grants — read-only by default, with explicit scopes for any write actions.

When the agent reads, it stays inside the companies you've shared. Nothing leaves your QuickBooks unless the agent posts a digest to Slack or adds a memo to a transaction you authorized.

→ QuickBooks official API docs

Set it up

How to connect

Before you start

  • A QuickBooks Online account.
  • Admin role on the company file.
  • A Slack workspace where the agent will live and post.
  • A decision on which QuickBooks companies the agent should reach.
  • About five minutes for the OAuth flow.

The steps

  1. Sign in to Fidelic and pick the agent. From the Roster, pick the bookkeeping agent.
  2. Authorize QuickBooks. Click Connect QuickBooks. The OAuth dialog opens; sign in with your QuickBooks admin account. The app appears in Apps → My apps.
  3. Pick the companies the agent should reach. Pick the company file and scopes (read-only or read + memo).
  4. Confirm and finish. The agent runs a test read against your reports. When it passes, your Slack channel shows a Connected to QuickBooks message.
  5. Try the first agent action. Ask for a monthly close digest in Slack — it returns the digest with citations to specific reports.

The edges

Connection limits

Where the connection draws the line:

  • · The agent only reads companies the admin explicitly grants.
  • · Bank feeds and rule engines run server-side; the agent reads their output.
  • · Posting transactions (versus reading) requires an explicit write scope.

The path

Where the data goes

The connection runs inside your sandboxed Anthropic project. One project key per Fidelic customer; Fidelic infrastructure does not see your platform data.

Anything the agent reads stays inside your environment. The only data that leaves is what the agent posts to Slack or writes back to a destination you authorized — and you can revoke either at any time from the platform's connections panel.

→ Read the full security architecture

Where to next