Create NetSuite Invoice: NetSuite 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
Customer Internal ID entity	string	Required	501
Invoice Date tranDate	string	Optional	—
Due Date dueDate	string	Optional	—
Memo memo	string	Optional	—
Line Items items	array	Required	Array of {item, quantity, rate} objects.

Sample request

{
  "entity": "501",
  "tranDate": "{{trigger.tranDate}}",
  "dueDate": "{{trigger.dueDate}}",
  "memo": "{{trigger.memo}}",
  "items": "{{trigger.items}}"
}

Returns

{
  "id": "12001",
  "total": 198,
  "status": "Open",
  "tranId": "INV1042",
  "dueDate": "2026-02-15"
}

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

FAQ

Questions about Create NetSuite Invoice.

What does the Create NetSuite Invoice action do in NetSuite?

Creates an invoice tied to a customer with line items, terms, due date. For "external billing system → push to NetSuite for financial consolidation" workflows.

What inputs does Create NetSuite Invoice require?

Required: Customer Internal ID, Line Items. 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 NetSuite 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 NetSuite Invoice support batch operations?

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

More actions