Bolt.new AI and QuickBooks integration: Step-by-Step Guide 2025

To integrate Bolt.new with QuickBooks, you don’t connect “Bolt to QuickBooks” directly — instead, you build a normal web backend inside Bolt.new (Node/Express, Python/FastAPI, etc.), and that backend talks to QuickBooks using Intuit’s official REST APIs through OAuth 2.0. Inside Bolt, you store your QuickBooks keys in environment variables, implement the QuickBooks OAuth flow, then call their accounting endpoints like customers, invoices, and payments. Bolt is simply the workspace where you scaffold, run, and test this integration in a sandboxed environment.

 

What Integrating Bolt.new with QuickBooks Really Means

 

Bolt.new does not provide a built‑in QuickBooks connector. You integrate with QuickBooks using:

• Intuit Developer App (this gives you Client ID, Client Secret, Redirect URI)
• OAuth 2.0 Authorization Code Flow (required by QuickBooks Online APIs)
• QuickBooks Accounting API (standard JSON REST API)
• Environment variables inside Bolt.new to store secrets securely

All communication happens from the backend service you build and run inside Bolt.new.

 

Step-by-step: How to integrate Bolt.new with QuickBooks

 

This is a clean, real-world way to do it.

• Create a QuickBooks Developer app at https://developer.intuit.com. In the dashboard you’ll get:
  • Client ID
  • Client Secret
  • Development Redirect URI
• Create a backend project inside Bolt.new (Node.js recommended for QuickBooks ecosystem compatibility).
• Add your secrets to Bolt.new environment variables:
  • QB_CLIENT_ID
  • QB_CLIENT_SECRET
  • QB_REDIRECT_URI
  • QB\_ENV=development
• Implement QuickBooks OAuth flow using official endpoints:
  • Authorize URL: https://appcenter.intuit.com/connect/oauth2
  • Token URL: https://oauth.platform.intuit.com/oauth2/v1/tokens/bearer
• Store the access token + refresh token (Bolt.new can store them in a local JSON file or use a DB if you added one).
• Call QuickBooks Accounting API endpoints using the access token and their required “realmId” (company ID).

 

Real Example: Working Node.js Express Code (OAuth + Fetch Customers)

 

import express from "express"
import fetch from "node-fetch"
import dotenv from "dotenv"

dotenv.config()

const app = express()

// Step 1 — Redirect user to QuickBooks authorization screen
app.get("/auth/quickbooks", (req, res) => {
  const url =
    "https://appcenter.intuit.com/connect/oauth2" +
    "?client_id=" + process.env.QB_CLIENT_ID +
    "&response_type=code" +
    "&scope=com.intuit.quickbooks.accounting" +
    "&redirect_uri=" + encodeURIComponent(process.env.QB_REDIRECT_URI)
  res.redirect(url)
})

// Step 2 — QuickBooks redirects back with ?code=&realmId=
app.get("/auth/callback", async (req, res) => {
  const { code, realmId } = req.query

  const tokenRes = await fetch(
    "https://oauth.platform.intuit.com/oauth2/v1/tokens/bearer",
    {
      method: "POST",
      headers: {
        Authorization:
          "Basic " +
          Buffer.from(
            process.env.QB_CLIENT_ID + ":" + process.env.QB_CLIENT_SECRET
          ).toString("base64"),
        "Content-Type": "application/x-www-form-urlencoded"
      },
      body:
        "grant_type=authorization_code" +
        "&code=" + code +
        "&redirect_uri=" + encodeURIComponent(process.env.QB_REDIRECT_URI)
    }
  )

  const tokenData = await tokenRes.json()

  // Save tokenData.access_token and tokenData.refresh_token somewhere safe
  global.accessToken = tokenData.access_token
  global.realmId = realmId

  res.send("QuickBooks connected! Tokens stored.")
})

// Example API call — Fetch QuickBooks customers
app.get("/quickbooks/customers", async (req, res) => {
  const url = `https://sandbox-quickbooks.api.intuit.com/v3/company/${global.realmId}/query?query=select * from Customer`

  const qbRes = await fetch(url, {
    headers: {
      Authorization: "Bearer " + global.accessToken,
      Accept: "application/json"
    }
  })

  const data = await qbRes.json()
  res.json(data)
})

app.listen(3000, () => {
  console.log("Server running on port 3000")
})

 

Important Notes

 

• QuickBooks access tokens expire quickly. You must refresh them using refresh tokens.
• Bolt.new does not persist tokens across rebuilds unless you store them in a DB or file storage you added.
• Use the sandbox QuickBooks company while testing. Production keys require Intuit review.
• The redirect URI must match exactly between your Bolt app and Intuit app dashboard.

 

What You Can Build from Here

 

• Automatic invoice creation when events happen in your app
• Sync QuickBooks customers into your internal CRM
• Push payment records or fetch outstanding balances
• Webhook listener for QuickBooks event notifications

This is the real, correct way to integrate Bolt.new with QuickBooks: build a backend in Bolt, store secrets as env vars, run the OAuth flow, call official QuickBooks REST endpoints, and test it end‑to‑end inside the Bolt sandbox.