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.
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. |
{"externalId": "crm-customer-501","companyName": "Acme Inc","firstName": "{{trigger.firstName}}","lastName": "{{trigger.lastName}}","email": "{{trigger.email}}"}
{"id": "501","externalId": "crm-customer-501"}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.