Create QuickBooks Invoice: QuickBooks action

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Company ID realmId	string	Required	Company ID
Customer ID customerId	string	Required	Customer ID
Line Item Description description	string	Required	Line Item Description
Amount amount	number	Required	Amount
Due Date dueDate	date	Optional	Due Date. (date/time)

Sample request

{
  "realmId": "{{trigger.realmId}}",
  "customerId": "{{trigger.customerId}}",
  "description": "{{trigger.description}}",
  "amount": "{{trigger.amount}}",
  "dueDate": "{{trigger.dueDate}}"
}

Returns

{
  "Invoice": {
    "Id": "123",
    "Balance": 100,
    "TotalAmt": 100,
    "DocNumber": "1001"
  }
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Create QuickBooks Invoice.

What does the Create QuickBooks Invoice action do in QuickBooks?

Creates an invoice with line items, tax codes, due date. For "project complete → auto-invoice in QuickBooks" workflows.

What inputs does Create QuickBooks Invoice require?

Required: Company ID, Customer ID, Line Item Description, Amount. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if QuickBooks returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Create QuickBooks Invoice support batch operations?

Yes. Run Create QuickBooks Invoice inside a Loop node to process arrays. Tiny Command handles QuickBooks's rate limits automatically so you don't have to throttle manually.

More actions