Get NetSuite Customer: 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	Required	501
Expand Sub-Resources expandSubResources	boolean	Optional	Include 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.

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. Tiny Command handles NetSuite's rate limits automatically so you don't have to throttle manually.

More actions