ActionNetSuiteUpdated September 2026

How do I upsert a NetSuite customer?

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

Upsert NetSuite Customer in NetSuite — start free All 9 NetSuite actions

Upsert 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.

Field	Type	Required	Description
External ID externalId	string	Required	External identifier used to find an existing record; created if not found.
Company Name companyName	string	Optional	Acme Inc
First Name firstName	string	Optional	–
Last Name lastName	string	Optional	–
Email email	string	Optional	–
Phone phone	string	Optional	–
Subsidiary Internal ID subsidiary	string	Optional	Required on OneWorld accounts.

Sample request

{
  "externalId": "crm-customer-501",
  "companyName": "Acme Inc",
  "firstName": "{{trigger.firstName}}",
  "lastName": "{{trigger.lastName}}",
  "email": "{{trigger.email}}"
}

Returns

{
  "id": "501",
  "externalId": "crm-customer-501"
}

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

Triggered by

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

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 Upsert NetSuite Customer.

What does the Upsert NetSuite Customer action do in NetSuite?

Creates or updates a customer based on external ID. For sync workflows that maintain NetSuite as the financial-master record with CRM as the originating source.

What inputs does Upsert NetSuite Customer require?

Required: External 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 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 Upsert NetSuite Customer support batch operations?

Run Upsert NetSuite Customer 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