Start free
ActionNetSuiteUpdated June 2026

How do I fetch a NetSuite customer?

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

Get NetSuite Customer in NetSuite — start free All 9 NetSuite actions
Get NetSuite Customer 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.

FieldTypeRequiredDescription
Customer Internal ID
customerId
stringRequired501
Expand Sub-Resources
expandSubResources
booleanOptionalInclude addressBook, contactRoles, subscriptions etc. in the response.
Sample request
{
  "customerId": "501",
  "expandSubResources": "{{trigger.expandSubResources}}"
}
Returns
{
  "id": "501",
  "email": "jane@acme.com",
  "entityId": "Acme Inc",
  "companyName": "Acme Inc"
}

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

Triggered by

Apps that pair well as the trigger for Get NetSuite Customer.

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

Gmail → NetSuite
1 Gmail triggers
Slack → NetSuite
13 Slack triggers
Google Sheets → NetSuite
2 Google Sheets triggers
HubSpot → NetSuite
18 HubSpot triggers
FAQ

Questions about Get NetSuite Customer.

What does the Get NetSuite Customer action do in NetSuite?
Returns a customer by internal ID with all fields including custom fields. The standard lookup for enrichment or validation workflows.
What inputs does Get NetSuite Customer require?
Required: Customer Internal ID. 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 Get NetSuite Customer support batch operations?
Yes. Run Get NetSuite Customer inside a Loop node to process arrays. TinyCommand handles NetSuite's rate limits automatically so you don't have to throttle manually.
More actions

Other NetSuite actions.

Action
Create NetSuite Customer
Creates a customer record in NetSuite ERP with name, addresses, payment terms. For "new account in CRM → provision in ERP for invoicing" workflows.
Action
Create NetSuite Invoice
Creates an invoice tied to a customer with line items, terms, due date. For "external billing system → push to NetSuite for financial consolidation" workflows.
Action
Create NetSuite Sales Order
Creates a sales order with customer, items, ship-to address. The standard hook for "e-commerce order → push to NetSuite for fulfilment and finance" workflows.
Action
Get NetSuite Invoice
Returns an invoice by internal ID with line items, totals, payment status. For revenue-reporting workflows or for sync to other accounting systems.
Action
List NetSuite Items
Returns the inventory items in NetSuite. For sync to e-commerce storefronts or for "audit which SKUs we have" inventory workflows.
Action
Search NetSuite Customers
Lookup by email, name, or custom field. The standard "find before update" pattern for upsert workflows.
Get NetSuite Customer in NetSuite — start free