Appearance
QuickBooks Online
undefined
| Detail | Value |
|---|---|
| Category | Accounting |
| Base URL | https://quickbooks.api.intuit.com/v3/company/{realm_id} |
| Authentication | OAuth2 |
| Endpoints | 6 |
| Connector key | quickbooks |
Using QuickBooks Online in a workflow
- Go to Connections and click New Connection.
- Pick QuickBooks Online from the marketplace.
- Enter your credentials (see Authentication above for what's expected).
- In a workflow, drop an API Call node and select this connection.
- Pick the operation you need from the Operation dropdown — the full list is below.
Available endpoints
| Endpoint | Summary |
|---|---|
GET | Invoices |
GET | Customers |
GET | Payments |
GET | Bills |
GET | Accounts |
GET | Reports |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
GET
Invoices
| Detail | Value |
|---|---|
| Operation ID | invoices_0 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your QuickBooks Online connection from the Connection dropdown.
- In the Operation dropdown, select
invoices_0. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream QuickBooks Online API reference.
GET
Customers
| Detail | Value |
|---|---|
| Operation ID | customers_1 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your QuickBooks Online connection from the Connection dropdown.
- In the Operation dropdown, select
customers_1. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream QuickBooks Online API reference.
GET
Payments
| Detail | Value |
|---|---|
| Operation ID | payments_2 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your QuickBooks Online connection from the Connection dropdown.
- In the Operation dropdown, select
payments_2. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream QuickBooks Online API reference.
GET
Bills
| Detail | Value |
|---|---|
| Operation ID | bills_3 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your QuickBooks Online connection from the Connection dropdown.
- In the Operation dropdown, select
bills_3. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream QuickBooks Online API reference.
GET
Accounts
| Detail | Value |
|---|---|
| Operation ID | accounts_4 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your QuickBooks Online connection from the Connection dropdown.
- In the Operation dropdown, select
accounts_4. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream QuickBooks Online API reference.
GET
Reports
| Detail | Value |
|---|---|
| Operation ID | reports_5 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your QuickBooks Online connection from the Connection dropdown.
- In the Operation dropdown, select
reports_5. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream QuickBooks Online API reference.