QuickBooks
QuickBooks Online accounting events
QuickBooks Online connects to Tiny Command via Intuit OAuth, with three transactional triggers (Customer Created, Invoice Created, Payment Received) that match how an SMB or accountant tracks revenue lifecycle. Four actions cover the reads and writes: Create Invoice for outbound billing, List Customers for sync workflows, Get Company Info for connection sanity checks, and Query — a power-user escape hatch that takes raw QBO Query Language (e.g., `SELECT * FROM Invoice WHERE Balance > '0' AND DueDate < '2026-01-01'`). Payment Received is the high-value trigger: it fires when a payment is recorded against an invoice (manual entry or auto-matched bank feed), with the payment method, amount, customer reference, and the invoices it cleared. Create Invoice supports line items with item-ref or freeform descriptions, tax codes, currency override (multi-currency companies), and a custom transaction date. The sandbox versus production company distinction is set at connection time — most teams keep separate Tiny Command connections for each.
Workflows start when QuickBooks does.
3 real-time triggers, each backed by a webhook subscription. Events arrive within seconds and you don't have to set up polling.
Fires when a new customer is added to QuickBooks Online. For "auto-sync to CRM" or "send welcome email" customer-onboarding workflows.
Fires on invoice creation (draft or sent). Useful for "log to revenue forecast" or "post-invoice automation" workflows.
Fires when a payment is recorded — manually or auto-matched from bank feed. Payload includes amount, method, the cleared invoices. The revenue-event hook.
Do anything QuickBooks can do, from a workflow.
Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.
| Action | What it does |
|---|---|
| Create QuickBooks Invoice | Creates an invoice with line items, tax codes, due date. For "project complete → auto-invoice in QuickBooks" workflows. |
| QuickBooks Get Company Info | Returns the connected company's details — name, address, fiscal year. Useful for connection sanity checks and for adapting workflows to company-specific config. |
| QuickBooks List Customers | Paginated customers with filters. For sync workflows that mirror QuickBooks to CRM or for "all customers with overdue invoices" reporting. |
| QuickBooks Query (QBO QL) | Power-user escape hatch — full QBO Query Language against any entity. For complex reports that don't have a typed action (aging summaries, P&L line pulls, custom filtering). |
Pre-built QuickBooks workflows.
Clone any recipe and customize it in one click. Every recipe is fully editable.
Three things worth knowing.
Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.
Connect QuickBooks once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.
Every QuickBooks field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.
Questions about the QuickBooks integration.
If we missed yours, ping support. We usually reply within an hour.
How do I connect QuickBooks to Tiny Command?
What QuickBooks triggers does Tiny Command support?
What QuickBooks actions can I run from a workflow?
Is the QuickBooks integration real-time?
Do I need to write code to use QuickBooks with Tiny Command?
How much does the QuickBooks integration cost?
More finance & accounting apps people connect.
Same category as QuickBooks, ordered by how often teams pair them. Hover the carousel to pause.
Do more with QuickBooks.
Wire it to Slack, Notion, HubSpot, Stripe, or any of the other 438 apps in our catalog. Setup takes roughly two minutes. Free to try, no credit card.
