What an agent can do in QuickBooks
Read and record invoices, customers, payments and the books.
Jobs on Rush that use QuickBooks
- Explain Each User's Monthly Profit and Loss From Their Own QuickBooks
- Find Last Month's Uncategorized Expenses in QuickBooks Before the Close
- Follow Up on Overdue QuickBooks Invoices Every Week
- Which Supplier Bills Are Due This Week, and for Which Job? A Construction App Lists Each Contractor's QuickBooks Bills
- Chase Invoices More Than 30 Days Overdue by Phone and Log What Each Customer Said
How QuickBooks connects
QuickBooks is a built-in app: you sign in with your QuickBooks account on its own page, through Rush's own app, so you register no OAuth app. The sign-in asks only for the scopes listed below, and the run's token reaches quickbooks.api.intuit.com, the QuickBooks Online Accounting API.
Connect it once in the console under Settings → Connections, or from your server with POST /me/connections. The sign-in finishes in a browser signed in to the console as the same person, and a link not finished within 10 minutes expires.
After that, a run that names quickbooks in connections, or runs a saved agent that names it, gets it; your connections reach no run that does not name them.
Scopes the sign-in asks for:
com.intuit.quickbooks.accounting
POST https://api.phoenix.so/me/connections
{
"type": "app",
"name": "quickbooks"
}Whose QuickBooks account the agent uses
Your QuickBooks connection is personal: it belongs to the person who signed in. A run started in the console uses that person's QuickBooks, and a run started with an API key uses the QuickBooks of the member who created the key.
To act for your own app's users, make each user an agent from your template and show them, signed in to your app, the sign-in link POST /o/{org}/agents/{agent}/connections returns. They sign in to their own QuickBooks, and that agent's runs use their account and nothing else: never yours, never another user's.
More Finance integrations
Frequently asked questions
How do I connect QuickBooks to Rush?
Open Settings → Connections in the console and connect QuickBooks, or send POST /me/connections with {"type":"app","name":"quickbooks"} and open the authorize_url it returns while signed in to the console. The connection reads pending until the sign-in finishes, then connected.
Does every run get my QuickBooks account?
No. A run gets your QuickBooks connection only when it names it in connections ("connections": ["quickbooks"]), or runs a saved agent that names it. A saved agent names its connections once, and every run of it gets them.
What can an agent do in QuickBooks?
Read and record invoices, customers, payments and the books. 5 published jobs use it; this page lists them.
Can my app's users connect their own QuickBooks?
Yes. Make each user an agent from your template, and they sign in to their own QuickBooks through the link POST /o/{org}/agents/{agent}/connections returns. That agent's runs use their account alone.
Keep reading
- AI agents for finance teams: every job and app for them
- How connections work: sign in once, then every run that names a connection gets it
- Start your first run from the developer API quickstart
- Pricing: one price per member, hours shared by the team
- How Rush compares with other cloud agents
- Every app and MCP server Rush connects to