ActionNetSuiteUpdated September 2026
How do I create a NetSuite sales order?
Short answer: You can create netsuite sales order in NetSuite by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the NetSuite Create NetSuite Sales Order action to a workflow, map its 5 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
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 entity | string | Required | 501 |
Transaction Date tranDate | string | Optional | 2026-01-15 |
Memo memo | string | Optional | – |
Line Items items | array | Required | Array of {item: <internal_id>, quantity, rate}. e.g. [{"item": "42", "quantity": 2, "rate": 99.00}] |
Subsidiary Internal ID subsidiary | string | Optional | Required on OneWorld accounts. |
Sample request
{"entity": "501","tranDate": "2026-01-15","memo": "{{trigger.memo}}","items": "{{trigger.items}}","subsidiary": "{{trigger.subsidiary}}"}
Returns
{"id": "9001","total": 198,"status": "Pending Approval","tranId": "SO1042"}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for Create NetSuite Sales Order.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Create NetSuite Sales Order.
What does the Create NetSuite Sales Order action do in NetSuite?
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.
What inputs does Create NetSuite Sales Order require?
Required: Customer Internal ID, Line Items. 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 Create NetSuite Sales Order support batch operations?
Run Create NetSuite Sales Order 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
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.
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.
ActionSearch NetSuite Customers
Lookup by email, name, or custom field. The standard "find before update" pattern for upsert workflows.