ActionNetSuiteUpdated September 2026

How do I search NetSuite customers?

Short answer: You can search netsuite customers in NetSuite by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the NetSuite Search NetSuite Customers action to a workflow, map its 3 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Search NetSuite Customers in NetSuite — start free All 9 NetSuite actions

Search NetSuite Customers in NetSuite — start free

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
Email Contains email	string	Optional	jane@acme.com
Company Name Contains companyName	string	Optional	Acme
Limit limit	number	Optional	Max records returned (1–1000).

Sample request

{
  "email": "jane@acme.com",
  "companyName": "Acme",
  "limit": "{{trigger.limit}}"
}

Returns

{
  "count": 1,
  "items": [
    {
      "id": "501",
      "email": "jane@acme.com",
      "entityid": "Acme Inc",
      "companyname": "Acme Inc"
    }
  ],
  "hasMore": false
}

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

Triggered by

Apps that pair well as the trigger for Search NetSuite Customers.

Any of these apps can fire this action as part of a workflow.

Google Sheets → NetSuite

2 Google Sheets triggers

HubSpot → NetSuite

18 HubSpot triggers

FAQ

Questions about Search NetSuite Customers.

What does the Search NetSuite Customers action do in NetSuite?

Lookup by email, name, or custom field. The standard "find before update" pattern for upsert workflows.

What inputs does Search NetSuite Customers require?

Search NetSuite Customers 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 run history shows the failed step with its input and the error message NetSuite returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does Search NetSuite Customers support batch operations?

Run Search NetSuite Customers inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within NetSuite's rate limits.

More actions