- Integrations
- /
- NetSuite
- /
- Actions
- /
- Upsert NetSuite Customer
NActionNetSuiteUpdated May 2026
How do I upsert a NetSuite customer?
Short answer: Drop the "NetSuite → Upsert NetSuite Customer" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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.
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 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 Upsert NetSuite Customer support batch operations?
Yes. Run Upsert 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
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.
ActionCreate 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.
ActionCreate 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.
ActionGet NetSuite Customer
Returns a customer by internal ID with all fields including custom fields. The standard lookup for enrichment or validation workflows.
ActionGet 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.
ActionList NetSuite Items
Returns the inventory items in NetSuite. For sync to e-commerce storefronts or for "audit which SKUs we have" inventory workflows.
Send upsert netsuite customer from your workflows.
Triggered by anything in the catalog. Free tier available. No credit card.