⚡ AI Analyst
Lovable QuickBooks integration is documented but missing from the connector catalogue we searched on 9 October 2026. Here is what works today.
Money Flock
Recommended Contents
Comments
MoneyFlock may earn a commission if you subscribe to a Lovable Business plan through links in this article, at no extra cost to you. TJ Alam is a certified Lovable Expert.
A Lovable QuickBooks integration is documented: a connector that reads customers, vendors, items, accounts, invoices, bills, payments, purchases and sales receipts from one QuickBooks Online company through Intuit's Accounting API, and writes records back through workflows. On 9 October 2026 that connector did not appear in the workspace connector catalogue we searched, so check yours before planning around it.
That gap is the whole story of this article. Lovable publishes a full page for the connector at docs.lovable.dev/integrations/quickbooks. The page loads, it is detailed, and it reads like any other shipped feature. But it is missing from the changelog, missing from the documentation index, and missing from the connector list inside the product. It is a key cut for a door that has not been hung yet.
Meanwhile the page ranking first for this search tells you flatly that QuickBooks has no native Lovable connector and walks you through an OAuth proxy you build yourself. That advice is out of date in one direction and still useful in another, which is an awkward place for a reader to land.
So this piece does three things. It sets out exactly what the documented connector covers and what it refuses to do. It shows what we found when we searched the live catalogue, with dates, so you can repeat the check in your own workspace in about thirty seconds. And it builds the thing most people actually want from company books, a receivables aging dashboard, including the arithmetic worked by hand and the Intuit limits that decide how often it can refresh.
Searched on 9 October 2026 in a live Lovable workspace. Xero returns a connector card. QuickBooks returns nothing.
Start with the documented scope, because it is narrower than the marketing-shaped summaries floating around. The connector works with QuickBooks Online only. It does not connect to QuickBooks Desktop. It reaches your books through Intuit's Accounting API using an OAuth connection to a single QuickBooks Online company.
Here is the read and write surface as the documentation describes it.
What the connector can and cannot do
| Capability | What the docs say |
|---|---|
| Query | Customers, vendors, items, accounts and company information |
| Read | Invoices, bills, payments, purchases and sales receipts |
| Write | Create or update QuickBooks records through workflows |
| Scope | One QuickBooks Online company per connection, shared across every project linked to it |
| Not supported | QuickBooks Desktop, webhooks or real-time event notifications, per-end-user QuickBooks login |
| Quotas | Intuit's own quotas, rate limits and account restrictions still apply and cannot be bypassed |
Two of those lines decide your architecture before you write a prompt. No webhooks means nothing pushes you an update when an invoice is paid, so the dashboard has to pull on a schedule. No per-end-user login means every viewer sees the same company's books through one shared connection, so the app itself has to decide who may see what.
There is also a role gate worth knowing before you promise a finance team a demo on Friday. Only workspace owners and admins can create the QuickBooks connection. A new connection is private to the person who made it until they choose to share it with named members or invite the whole workspace. Everyone else can only ask Lovable, in a project chat, to link their project to a connection that already exists.
One detail the queued brief had slightly wrong, and the live page corrects: you can create several QuickBooks connections using different Intuit accounts or companies. That is how you keep a sandbox company and a production company side by side, which matters more than it sounds.
On 9 October 2026 we opened the Connectors panel in a live Lovable workspace and searched it twice, with nothing else changed between the two searches.
142 connectors in the catalogue. QuickBooks is not one of them.
Searching xero returned a Xero card reading "Connect accounting data from Xero". Searching quickbooks returned No connectors found. Same workspace, same panel, same minute. The screenshot above is that pair, uncropped except for the project sidebar.
Three more checks point the same way:
What that does not prove is that the connector is unavailable everywhere. A single workspace is a single data point, and staged rollouts are ordinary. What it does prove is that you should not quote a delivery date to anyone on the strength of a documentation page. Open your own Connectors panel, type the vendor name, and believe the answer you get there.
It is worth saying plainly what the better third-party pages get wrong. The community-run Lovable Feature Atlas lists this connector as generally available since July 2026. We could find no Lovable source that dates it, and the changelog, which dated Xero to the day, says nothing. Treat that July date as unsourced.
This is the part that decides your bill, so it comes before the build. Lovable's publishing rules are tied to plan, and company books are the clearest case in the whole product for why that matters.
Where a published app can be seen, by plan
| Plan | Who can visit the published app |
|---|---|
| Free | Anyone with the link. Access cannot be restricted |
| Pro, $25 a month | Anyone with the link. Access cannot be restricted |
| Business, $50 a month | Public, or workspace members only, or a custom audience you compose |
| Enterprise | The same, plus admin control over who is allowed to publish externally |
Read the first two rows again. On Free and Pro, publishing is always external to the web, and there is no setting that keeps strangers out. A dashboard showing your receivables, your overdue customers and your cash position is not something to put behind an unguessable URL and hope. Workspace-only publishing starts on Business.
There is a trap on the way back down, too. If you restrict access on Business and later downgrade, the live app keeps requiring a login, but you cannot publish changes to it. Lovable shows "Publish to workspace requires a Business plan" and the old version stays up until you either make the app public or upgrade again.
On Business you can also invite named people outside your workspace as viewers, which is how an external accountant or a fractional CFO sees the dashboard without joining your team. Those invitations do not expire, and removing someone revokes access the next time you publish. If your workspace restricts invitations to verified domains, addresses outside them simply cannot be added.
If you are weighing the step up, our plan-by-plan breakdown of Lovable pricing covers the credit ladders, and you can start a Business plan on Lovable when the audience control is the thing you actually need. If you would rather have someone set the workspace up with you, TJ's certified Lovable Expert profile is the place to start.
The connector documentation says it in one line: billing, quota and API limits are handled by Intuit. So the ceiling on your dashboard is Intuit's, and those numbers are published.
Read on developer.intuit.com on 9 October 2026. These limits apply whichever route you use.
QuickBooks Online REST API limits, read 9 October 2026
| Limit | Value |
|---|---|
| Requests per minute | 500 per realm ID |
| Requests per second | 10 per realm ID and app |
| Combined limit with non-QuickBooks endpoints | 800 per minute per realm ID and app |
| Batch payloads | 30 recommended per request |
| Batch throttle | 40 per minute per realm and app, 120 per minute per realm |
| Query response size | 1,000 entities maximum, paginate beyond that |
| Request timeout | 120 seconds |
| On throttle | HTTP 429, wait 60 seconds before retrying |
500 requests per minute per realm ID. That is Intuit's ceiling, and it is generous for a dashboard and tight for a sync.
Two numbers deserve a second look. The 1,000 entity cap on a query response is the one that quietly breaks a dashboard six months after launch, when the invoice table finally crosses it and a page that always worked starts showing a number that is wrong rather than an error that is obvious. Paginate from day one, even when the test company has forty invoices.
The second is the one nobody writes about. Apps in the Builder tier of the Intuit App Partner Program carry an included limit of 500,000 CorePlus API calls per workspace per month, and calls past it are throttled with a 429. An internal dashboard that pulls once an hour will not come close. A per-customer portal that refreshes on every page view can, and the failure arrives as a rate-limit error rather than a bill.
Note also that the Intuit App Partner Program is open to partners based in a short list of countries. Check Intuit's own page for whether yours is included before you design around the Builder tier.
The example below is a receivables aging view: how much is current, how much is 30, 60 and 90 or more days past due, cash in against cash out by month, and the customers holding up the most money. It is the request that comes up more than any other when a finance team asks for a view of the books.
Intuit gives developers sandbox companies, and the connector's setup explicitly offers Sandbox as an environment alongside Production. Build against the sandbox. Real books are exactly the wrong place to discover that a filter was inverted, and sandbox servers carry the same throttles, so your pagination and retry logic get a fair test.
A workspace owner or admin creates the connection, names it something like QuickBooks Prod, picks the environment, and authorizes through Intuit's consent screen. The connection is private to its creator until shared, so decide early whether the whole workspace gets it or a named few do. If you are a solo builder this takes a minute. If you are in a company, it is a conversation with whoever administers the books.
Once a connection exists, anyone building in a project can ask Lovable in the project chat to link that project to it. From there you describe the dashboard in plain language rather than wiring endpoints. The pattern is the same one that makes Lovable's connectors genuinely useful across a finance stack: the credentials live in the connector gateway, not in your project's code.
Five object types cover the whole dashboard: invoices, payments, customers, bills and accounts. Resist pulling the full chart of accounts on every load. Cache the customer list, which barely changes, and refresh only the transaction objects.
With no webhooks, the dashboard is only as current as its last pull. Pick a cadence that matches how the number is used. Hourly is plenty for a view someone checks with coffee. A collections team working a list wants fifteen minutes. Whatever you pick, put the timestamp on the page, because a stale number with no timestamp is worse than no number.
Last step, and the one people skip. Open the publish dialog, change the audience from the default to your workspace, and publish. If the option is not there, you are on Free or Pro, and the app you just built is about to be readable by anyone who gets the link.
Dashboards hide arithmetic, and hidden arithmetic is how two people end up quoting different overdue totals in the same meeting. So here is one bucket, done by hand, with a reporting date of 9 October 2026 and terms of net 30.
Take four open invoices for one customer: $18,400 issued 2 September, $7,250 issued 1 August, $12,000 issued 5 July and $4,900 issued 20 September.
Due dates are issue plus 30: 2 October, 31 August, 4 August and 20 October. Days past due on 9 October are 7, 39, 66 and not yet due. So the $4,900 sits in current, the $18,400 lands in the 1 to 30 bucket, the $7,250 in 31 to 60, and the $12,000 in 61 to 90. Total outstanding is $42,550, of which $37,650 is past due and $19,250 is more than thirty days past due.
Two decisions inside that calculation will be argued about, so make them explicit in the interface rather than burying them. The first is whether you age from the invoice date or the due date. Ageing from the due date, as above, is the normal convention and the one a collections team expects. The second is what you do with partial payments: a $18,400 invoice with $10,000 received is usually shown as $8,400 in its original bucket, not moved forward. Put the rule in the field label, not in a footnote.
For cash in against cash out, sum payments received by month on one side and bills plus purchases by month on the other, and plot both. The gap is the number people look at. If you want that same picture built from a sheet rather than from the books, we covered the route in turning a finance spreadsheet into an app.
Lovable pricing read logged out on 9 October 2026. Internal publish appears first on the Business card.
Two meters run at once, and they are easy to confuse.
Lovable charges credits. Business starts at $50 a month for 100 credits and runs up a ladder to 10,000 credits at $4,300 a month, verified logged out on 9 October 2026. Pro runs from $25 for 100 credits to $2,250 for 10,000. Business is roughly twice Pro per credit through most of the ladder, and what the extra buys is the team workspace, role-based access, internal publish, SSO and the security centre rather than more capacity.
Intuit charges nothing for ordinary Accounting API access, but the Builder tier's 500,000 CorePlus calls per workspace per month is the number that governs a high-traffic app. Between the two, a normal internal dashboard is a credit question, not an API question.
If QuickBooks turns out not to be available in your workspace, the alternatives are worth pricing honestly. Lovable's catalogue carries Xero today. The documentation also describes connectors for Wave, Zoho Books and Sevdesk. And for anything with a public API, a custom connector or a direct integration is available on all plans, with the custom connector route keeping the credentials in the gateway rather than in your project. Creating one needs the admin or owner role.
The whole reason this article exists. A page that loads is not a feature that shipped. Check the changelog for a date, then check the product itself.
On Free and Pro there is no audience control. If your dashboard is live and you did not deliberately choose an audience, it is public. This is the single most expensive mistake in the list, and it costs $50 a month to avoid.
No webhooks means no push. If a collections call is made on a figure that was pulled four hours ago, the timestamp matters more than the figure.
Queries return at most 1,000 entities. A dashboard built without pagination works perfectly until it silently stops being right. Build the paging in before you need it.
One connection equals one company. There is no per-end-user QuickBooks login, so a customer-facing portal must enforce its own access rules on top of the shared connection. Our guide to keeping financial data safe in apps built with Lovable covers the row-level pattern that does the work.
This connector reads books that already exist. If what you want is to raise invoices from scratch, that is a different build, and we covered it in building an invoice app without code.
Yes, through more than one route. Lovable documents a native QuickBooks Online connector, and where that is unavailable you can create a custom connector or a direct integration against Intuit's Accounting API on any plan. Both routes hit the same Intuit limits.
No. The documentation is explicit that the connector supports QuickBooks Online through Intuit's Accounting API and cannot connect to QuickBooks Desktop.
Nothing is replacing it, but it is no longer the only option in the catalogue. Xero is available as a Lovable connector today, and the documentation also describes Wave, Zoho Books and Sevdesk. Which one fits depends on where your books already live, not on which has the better API.
Workspace owners and admins. A new connection is private to its creator until shared with named members or the whole workspace. Other members can only ask Lovable to link an existing connection to their project.
You need it to keep the dashboard private. Free and Pro publish to anyone with the link with no way to restrict access, and workspace-only publishing starts on Business at $50 a month.
No. The connector receives no QuickBooks webhooks or event notifications, so the app has to pull on a schedule. Show the last-refreshed timestamp on the page.
A key cut for a door that has not been hung yet is still a useful thing to have in your pocket, as long as you do not promise anyone you can open the door. Verify in the product, build on the sandbox, publish to the workspace, and let the documentation catch up on its own schedule. If an outside view would help, TJ's Lovable Expert directory listing is open, and you can compare the plans on Lovable before you commit.
If you want the whole series in one place, our 2026 review of Lovable for founders links every article in this cluster, including the Excel connector as a finance backend, the expense approval build and turning a published app into a connector for ChatGPT and Claude.
TJ Alam is a certified Lovable Expert (Website Builder track), founder of Digi Flock Enterprises, and built tjalam.com and cyberdance.in on Lovable. MoneyFlock may earn a commission if you subscribe to a Lovable Business plan through links in this article, at no extra cost to you. TJ Alam is a certified Lovable Expert.