Search NetSuite Invoices: 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 customerId	string	Optional	501
Status status	options	Optional	—
From Date fromDate	string	Optional	—
Limit limit	number	Optional	—

Sample request

{
  "customerId": "501",
  "status": "{{trigger.status}}",
  "fromDate": "{{trigger.fromDate}}",
  "limit": "{{trigger.limit}}"
}

Returns

{
  "count": 1,
  "items": [
    {
      "id": "12001",
      "total": 198,
      "status": "Open",
      "tranid": "INV1042"
    }
  ],
  "hasMore": false
}

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

FAQ

Questions about Search NetSuite Invoices.

What does the Search NetSuite Invoices action do in NetSuite?

Filter invoices by customer, status, date range. For accounts-receivable reporting workflows.

What inputs does Search NetSuite Invoices require?

Search NetSuite Invoices has no required inputs. Sensible defaults are applied if you leave fields blank.

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 Search NetSuite Invoices support batch operations?

Yes. Run Search NetSuite Invoices 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